When a new site opens, the agenda is always the same: lease, fit-out, equipment, hiring. Attendance at the new branch usually sits at the bottom of that list - which is exactly why it causes trouble in the opening week.
This piece covers the real sources of delay and the sequence that brings connection down to one day.
Where the delay comes from
In a device-based model three stages create sequential waiting, and they cannot run in parallel.
First, ordering and delivery. If the device is not in stock, the timeline depends on the supplier.
Second, cabling and mounting. This has to overlap with the fit-out; if it does not, the wall gets opened a second time.
Third, configuration, testing and acceptance. Usually the shortest stage, but it cannot start before the first two are done.
In practice these three take a week or two, and the opening date ends up depending on their schedule. The result is a familiar picture: the store is trading while the record is still kept on paper.
The price of one week on paper
"Let's keep it on paper for a week" looks harmless but produces three consequences.
That week's records have to be transferred into the system by hand later. New employees form their first impression on paper - so moving to the system means learning it a second time. And third, the opening week is usually the most chaotic: schedules shift, people cover for each other, overtime is high. Those are precisely the records that cause the most disputes at month end.
How one-day connection becomes possible
In a model with no hardware purchase, two of the stages simply do not exist - ordering and mounting. What remains looks like this:
- Structure. The new branch is created as a unit and attached to the existing company tree.
- Recording point. The point attaches to the branch; the code is printed and placed in plain sight at the entrance.
- Work schedule. One of the existing templates is selected, or a new one is written.
- Employees. The list is added and each person connects from their own phone.
These four steps fit into one working day. The long part is not technical - it is settling the branch's rules. More on this: multi-branch attendance system.
Three things to prepare before opening
The work schedule. If the new branch's schedule differs from existing templates, it should be written in advance. Store and warehouse schedules usually differ.
The lateness threshold. It must match the central rule. If the new branch decides "we count fifteen minutes here", cross-branch comparison is broken from the first month.
The location of the point. In the entrance area, visible and well lit. A practical detail: the point must sit on the path people actually take - a point off to one side is forgotten in the first week.
Seasonal and temporary staff
At a new site opening this is the most common case: a temporary crew is brought in for the launch.
Keeping them in a separate file is the most common mistake - a second source appears at month end and the reconciliation work comes back.
The practical approach: temporary staff are added to the same structure and deactivated when the work ends. Their records stay in the archive, so the next opening has real numbers to plan with - how many people, how many days, how many hours.
What to check in the first week
- Are records landing in the correct branch? (This is the most common setup error.)
- Does the lateness threshold match the central rule?
- Is coverage adequate at the point?
- Can the branch manager see their own cut?
- Do notifications arrive scoped to this branch only?
Run these five checks in the first week and there is almost nothing left to correct at month end.
A worked example: two store openings
A retail company opened two stores in the same quarter. The first with the terminal model, the second already on a mobile setup.
At the first store the device order took three weeks, the mounting did not line up with the fit-out and the wall was opened a second time. After the store started trading, nine days of records were kept on paper. Those nine days were transferred by hand later and produced four disputed rows at month end.
At the second store the setup was finished two days before opening: a row was added to the structure, the code was printed and placed at the entrance, employees connected from their own phones. Day one started with records.
The company summed the result up in one sentence: the difference was not in the system itself but in whether the opening date depended on somebody else's schedule.
Three typical questions in a new branch's first month
"Records land in the wrong branch." This is the most common setup error and the cause is usually the same: the point was created but not attached to the branch. Checking a few records on day one exposes it immediately.
"The lateness count is far too high." At a new branch this is usually not real lateness - the work schedule was set up wrongly. In the opening week especially, schedules are volatile and the template does not reflect the current situation.
"Far too many notifications are arriving." The cause is that every event was switched on for the new branch. The practical fix: in the opening month only one event stays - a shift that has not opened - with the rest added a month later.
Knowing these three in advance makes the opening week considerably calmer.
The next step
Keeping the opening date independent of an installation schedule is one of the most appreciated advantages in practice - particularly for companies opening two or three sites a year.
See what QRGate does, or calculate the price for the number of branches you are planning.
