ACCESS CONTROL

Testing RFID wristbands before the doors open

Testing RFID wristbands before the doors open

Testing RFID wristbands before the doors open

21 JULY 2026

Abstract 3D illustration of an off-white arch on a deep violet base, with a pale lilac sphere passing through it and small spheres floating around, on a plain coral background.

The first hour after the doors open is when an access system is under the most pressure. Thousands of people arrive at once, staff are still finding their rhythm, and any problem with the wristbands or the readers turns into a queue within minutes. Most of those problems can be found and fixed the day before, with a simple test plan that takes a few hours and involves the people who will actually run the gates.

This guide sets out a practical test plan for RFID wristbands, from the moment the boxes arrive to the last check before opening. It covers checking the delivery, reading samples from every batch, rehearsing at the gates with the real hardware, training staff, and deciding in advance what happens when a band does not read. It assumes the chip and encoding were confirmed with a sample before production, as they should be.

Check the delivery

Start when the boxes arrive. Count them against the packing list, open a few from each version and check that the contents match the labels: access level, colour, number range and quantity. A box of VIP bands packed as general admission is easy to fix in the office and very hard to fix at a busy gate.

Start when the boxes arrive. Count them against the packing list, open a few from each version and check that the contents match the labels: access level, colour, number range and quantity. A box of VIP bands packed as general admission is easy to fix in the office and very hard to fix at a busy gate. Store the boxes by version in a locked room, so nothing is opened or moved before the distribution plan says so.

Check the print on a few bands from each version. Look at the design, the colours, the numbering and any codes, and compare them with the approved proof. Small differences in colour are normal between materials, but a wrong date, a missing logo or an unreadable code should be raised immediately, while there is still time to act.

Check the print on a few bands from each version. Look at the design, the colours, the numbering and any codes, and compare them with the approved proof. Small differences in colour are normal between materials, but a wrong date, a missing logo or an unreadable code should be raised immediately, while there is still time to act. Photograph anything that looks wrong next to the label of its box, so the issue is easy to describe and trace.

Keep the UID file that came with the order, and make sure your access provider has imported it. The file links each band's number to its chip, and the system needs it to recognise the bands. Ask the provider to confirm that the number of records matches the number of bands delivered, version by version.

Keep the UID file that came with the order, and make sure your access provider has imported it. The file links each band's number to its chip, and the system needs it to recognise the bands. Ask the provider to confirm that the number of records matches the number of bands delivered, version by version. Save a copy of the file in a second place, because it is the reference for every replacement during the event.

Read samples from every batch

Take a few bands from each version and read them with the provider's hardware: a handheld reader, a gate reader or whatever will be used on the day. Check that each band reads, that the system recognises it and that it shows the right access level. A version that reads in the office but shows the wrong level in the system points to a data problem, not a band problem.

Take a few bands from each version and read them with the provider's hardware: a handheld reader, a gate reader or whatever will be used on the day. Check that each band reads, that the system recognises it and that it shows the right access level. A version that reads in the office but shows the wrong level in the system points to a data problem, not a band problem. Note the result for each version in a short checklist, so you can show later exactly what was tested and when.

  • Include the first and last numbers of each range in the test. If the UID file is incomplete or offset by one row, the first or last bands are often where it shows. A quick check at both ends of each range catches errors that a random sample might miss.

  • Include the first and last numbers of each range in the test. If the UID file is incomplete or offset by one row, the first or last bands are often where it shows. A quick check at both ends of each range catches errors that a random sample might miss. If a range does not read as expected, stop and check the file with your provider before testing further.

Test the spares too. The bands that will be used for replacements need to be in the system and work like the others. Finding out at the help desk, on the first afternoon, that the spare stock was never imported is a common and avoidable problem.

Test the spares too. The bands that will be used for replacements need to be in the system and work like the others. Finding out at the help desk, on the first afternoon, that the spare stock was never imported is a common and avoidable problem. Keep a few tested spares aside as a reference, so the help desk can compare a faulty band with one that is known to work.

Rehearse at the gates

Once the samples read correctly, rehearse at the actual gates with the hardware installed. Readers mounted on turnstiles or posts behave differently from handheld readers, and the way people present their wrist matters. Ask a few colleagues to walk through each gate as attendees would, with bands on their wrists, at a normal walking pace.

Once the samples read correctly, rehearse at the actual gates with the hardware installed. Readers mounted on turnstiles or posts behave differently from handheld readers, and the way people present their wrist matters. Ask a few colleagues to walk through each gate as attendees would, with bands on their wrists, at a normal walking pace. Include the accessible entrances and any gates that will only open at peak times, because they are the easiest to forget.

Watch the read rate and the time per person. A gate that needs people to stop, turn their wrist and wait for a second beep will move far more slowly than one that reads as people walk past. If reads are slow or inconsistent, involve the provider: the position of the reader, the angle of approach or the settings may need adjusting.

Watch the read rate and the time per person. A gate that needs people to stop, turn their wrist and wait for a second beep will move far more slowly than one that reads as people walk past. If reads are slow or inconsistent, involve the provider: the position of the reader, the angle of approach or the settings may need adjusting. Time a few walk-throughs with a stopwatch, because impressions of speed are unreliable when everyone is busy.

For UHF systems, test with several people at once, because the read zone and the number of tags in range affect performance. For HF and LF systems, test with people of different heights and with bands on either wrist. The goal is to find the conditions in which reads fail before the crowd finds them for you.

For UHF systems, test with several people at once, because the read zone and the number of tags in range affect performance. For HF and LF systems, test with people of different heights and with bands on either wrist. The goal is to find the conditions in which reads fail before the crowd finds them for you. Repeat the test once the gate structures, barriers and signage are fully installed, because metal and layout can change the results.

Train the people at the gates

Gate staff need to know three things: how a correct read looks and sounds, what to do when a band does not read, and how to recognise each access level by sight. A short briefing at the start of each shift, with real bands to hold and look at, works better than a written document that nobody reads.

Gate staff need to know three things: how a correct read looks and sounds, what to do when a band does not read, and how to recognise each access level by sight. A short briefing at the start of each shift, with real bands to hold and look at, works better than a written document that nobody reads. Pair new volunteers with someone experienced for the first hour, so questions are answered without stopping the line.

Show staff the closure on each band type and what tampering looks like. Our article on wristband closures explains what to check. Staff who know what a normal closure looks like will spot a damaged one quickly, and they will be more confident in refusing a band that has clearly been opened and closed again.

Show staff the closure on each band type and what tampering looks like. Our article on wristband closures explains what to check. Staff who know what a normal closure looks like will spot a damaged one quickly, and they will be more confident in refusing a band that has clearly been opened and closed again. Keep a few correctly closed and deliberately opened examples at each gate for reference during the first shifts.

Give staff a simple rule for problems. A band that does not read after two attempts goes to the help point, not back into the queue. The person is not refused, but the gate keeps moving. A clear rule prevents long discussions at the reader, which hold up everyone behind.

Give staff a simple rule for problems. A band that does not read after two attempts goes to the help point, not back into the queue. The person is not refused, but the gate keeps moving. A clear rule prevents long discussions at the reader, which hold up everyone behind. Make sure the help point is close enough to the gates that sending someone there does not feel like a punishment.

Plan for failures

Some bands will fail on the day. A chip damaged during fitting, a band cut by mistake or a record missing from the system all lead to the same result: a person at the gate whose band does not read. The help point should be able to check the band, find the record by its printed number, and issue a replacement or fix the record within minutes.

Some bands will fail on the day. A chip damaged during fitting, a band cut by mistake or a record missing from the system all lead to the same result: a person at the gate whose band does not read. The help point should be able to check the band, find the record by its printed number, and issue a replacement or fix the record within minutes. Rehearse that process at least once with a test record, so the help point team has done it before the first real case.

Decide in advance what happens if a reader or the network fails. Some systems keep working offline and sync later; others need a constant connection. Ask your provider which applies, and agree a fallback: a handheld reader, a visual check of the band and its number, or a temporary manual process. Write it down, so staff do not have to improvise under pressure.

Decide in advance what happens if a reader or the network fails. Some systems keep working offline and sync later; others need a constant connection. Ask your provider which applies, and agree a fallback: a handheld reader, a visual check of the band and its number, or a temporary manual process. Write it down, so staff do not have to improvise under pressure. Test the fallback during the rehearsal by switching off a reader for a few minutes, so everyone sees how it works.

Keep a log during the first hours. Record each failed read, its cause if known and the action taken. Patterns appear quickly: a batch with more failures, a gate with slow reads, a type of band that is often fitted badly. The sooner you see them, the sooner you can fix them, while the event is still running.

Keep a log during the first hours. Record each failed read, its cause if known and the action taken. Patterns appear quickly: a batch with more failures, a gate with slow reads, a type of band that is often fitted badly. The sooner you see them, the sooner you can fix them, while the event is still running. A shared sheet that the help point and the provider can both see makes it easier to act on what the log shows.

Test cashless and internal points too

If the bands are also used for cashless payments, test the payment devices at bars and stalls as well as the gates. Top up a band, make a payment, check the balance. Do it with bands from the delivered order, not the sample, so the test covers the real data. Our article on cashless wristbands covers what to check in more detail.

If the bands are also used for cashless payments, test the payment devices at bars and stalls as well as the gates. Top up a band, make a payment, check the balance. Do it with bands from the delivered order, not the sample, so the test covers the real data. Our article on cashless wristbands covers what to check in more detail. Include a refund in the test, because it is the step most likely to be forgotten until the end of the event.

Test internal checkpoints such as VIP areas, backstage doors and staff entrances. Each one may have its own rules in the system, and a rule that is set up incorrectly will block the people it should let in. Walk through each checkpoint with a band from each access level and confirm the result is the expected one.

Test internal checkpoints such as VIP areas, backstage doors and staff entrances. Each one may have its own rules in the system, and a rule that is set up incorrectly will block the people it should let in. Walk through each checkpoint with a band from each access level and confirm the result is the expected one. Record which bands were used for these tests and remove them from circulation afterwards if your system requires it.

If bands are used across several days, test that the system handles the change of day correctly. A Saturday band should not open the gates on Sunday, and a weekend band should work on both. Testing the day change the evening before, with the provider, avoids a difficult start on the second morning.

If bands are used across several days, test that the system handles the change of day correctly. A Saturday band should not open the gates on Sunday, and a weekend band should work on both. Testing the day change the evening before, with the provider, avoids a difficult start on the second morning. If the system allows it, simulate the change of day earlier in the week rather than waiting for midnight.

Who should be involved

The test needs three groups: the access provider, who knows the hardware and the system; the operations team, who will run the gates and the help point; and someone who knows the order, its versions and its number ranges. When all three are present, problems can be diagnosed and fixed on the spot instead of passed from one team to another.

The test needs three groups: the access provider, who knows the hardware and the system; the operations team, who will run the gates and the help point; and someone who knows the order, its versions and its number ranges. When all three are present, problems can be diagnosed and fixed on the spot instead of passed from one team to another. Agree a time and a place for the test in advance, and send everyone the same checklist so nothing is left out.

Schedule the test early enough to fix what it finds. The day before the doors open is the latest sensible time, and earlier is better for large events. If the test shows that a batch has a problem, there may still be time to work around it, for example by issuing those bands only at a staffed desk where they can be checked manually.

Schedule the test early enough to fix what it finds. The day before the doors open is the latest sensible time, and earlier is better for large events. If the test shows that a batch has a problem, there may still be time to work around it, for example by issuing those bands only at a staffed desk where they can be checked manually. Keep a short list of who to call if the test reveals a problem, including your system provider and your wristband supplier.

Before production, we send a physical sample of the actual wristband within 24 hours of the chip being confirmed, so the provider can test the chip and encoding early. The on-site test then confirms that the whole system, from the delivered bands to the installed readers, works together under real conditions.

Before production, we send a physical sample of the actual wristband within 24 hours of the chip being confirmed, so the provider can test the chip and encoding early. The on-site test then confirms that the whole system, from the delivered bands to the installed readers, works together under real conditions. Both tests are needed, because each one answers a different question about the same bands.

A calm first hour

A few hours of testing the day before turn the first hour of the event from a gamble into a routine. Check the delivery, read samples from every batch, rehearse at the gates, train the staff and agree what to do when something fails. When the doors open, the system has already been through its first rush.

A few hours of testing the day before turn the first hour of the event from a gamble into a routine. Check the delivery, read samples from every batch, rehearse at the gates, train the staff and agree what to do when something fails. When the doors open, the system has already been through its first rush. After the event, keep the test checklist and the log, because they are the best starting point for the next edition.

You can see the wristband, badge and lanyard options in our catalogue.

If you want to plan the sample and delivery dates around your on-site rehearsal, tell us your event dates and the system you use. We reply in one hour on average and can help you build the timeline. Everything is produced white label and pre-encoded to the specification you approve.

If you want to plan the sample and delivery dates around your on-site rehearsal, tell us your event dates and the system you use. We reply in one hour on average and can help you build the timeline. Everything is produced white label and pre-encoded to the specification you approve. Allowing a few days between delivery and the rehearsal gives you room to act on anything the checks reveal.

Write to us at hello@accesioid.com, or book a call with Marco using the link at the bottom of this page.



YOU MAY ALSO LIKE

It starts here

One conversation,
no commitment.

Book a call

Pick a day and time. No back-and-forth emails.

Or leave us your email
and we'll get back to you.

© 2026 Accesio. All rights reserved.

Made with love by Relaja

It starts here

One conversation,
no commitment.

Book a call

Pick a day and time. No back-and-forth emails.

Or leave us your email
and we'll get back to you.

© 2026 Accesio. All rights reserved.

Made with love by Relaja

It starts here

One conversation,
no commitment.

Book a call

Pick a day and time. No back-and-forth emails.

Or leave us your email
and we'll get back to you.

© 2026 Accesio.
All rights reserved.

Made with love
by Relaja