How long does it take to write a batch of tags?
The write itself takes about a second. Everything around it dominates: picking up the tag, positioning the phone, waiting for confirmation, moving it to the other pile. Quote a job on handling time rather than on write time, because handling is nearly all of it.
The write is the fast part
Committing a short message to a tag takes about a second, and a longer message somewhat more. Verification adds roughly the same again.
That figure is stable and uninteresting, and it is the one people ask about. It is not what determines how long a batch takes.
Handling is the job
Pick up a tag. Position it. Bring the phone over it and hold still. Wait for the confirmation. Move it to the written pile. Pick up the next one.
Every one of those steps costs more than the write, and together they account for the overwhelming majority of a run. A batch of five hundred is an exercise in repetitive handling with a brief electronic pause in the middle.
Which means the technical questions people worry about, chip speed, message length, tag type, barely matter to the schedule. The physical arrangement of the table matters enormously.
Quoting a run
Estimate from handling, then add the passes you actually need: writing, verification, application, and a final walk if the tags are installed somewhere.
Add a rejection allowance based on your own recorded yield rather than an assumption, and order spare tags accordingly. Running out of tags at the end of a job costs a second delivery and a second visit.
And be honest about fatigue. A run that takes a full day does not proceed at the pace of its first hour, and pretending otherwise is how deadlines slip.
What actually makes it faster
Removing the phone case, which reduces retries on every single tag.
Laying tags out in a grid rather than a pile, so picking one up is a single motion and no two are ever in contact.
A repeat mode that does not require returning to a setup screen between tags.
And two people, one presenting tags and one operating the phone, which is more than twice as fast as one person doing both because it removes the constant switch between hands.
What does not make it faster is rushing. Moving the phone before the confirmation produces partial writes, and every one of those costs a rework cycle worth many times the second it saved.
Frequently asked questions
Does a longer URL take noticeably longer to write?
Marginally, and not enough to change a schedule. The handling around each tag dominates so completely that content length is a rounding error.
Is a dedicated encoder much faster per tag?
Per tag the difference is modest. Its advantage is removing the human from the loop for large runs and driving unique content from a list, not raw speed.
How many tags can one person do in an hour?
It depends on the tags, the layout and the operator, so the useful figure is your own measured rate. Time a hundred and extrapolate rather than trusting a published number.
Should verification be a separate pass?
Doing it immediately after each write is simpler and catches problems at the moment they occur. A separate pass is only worth it when the two are done by different people.