Why acceptance has its own list
A pilot usually ends with the impression that everything works, because it worked for a dozen or so people in one department. Acceptance is meant to check whether the same works for other shifts, other supervisors and other ways of entering. The employer keeps a working time record, which is the basis for pay and other benefits (Labour Code (Kodeks pracy), art. 149 § 1), so a scale error means an error in pay for many people.
The time module is disabled by default and the administrator turns it on. Earlier, visibility can be limited to a list of testers, where an empty list means everyone. This is the basic mechanism of a controlled start: scope grows by adding people, and the final step is emptying the list.
Points to tick and comments
Each point on the checklist below has one owner and one piece of evidence. Without evidence the point is not ticked.
Scope and visibility
Check who is on the tester list and decide whether the list will be emptied when starting on all halls, because an empty list means everyone. Remember that an employee sees themselves, HR sees employees of its company, a supervisor sees their subtree and the administrator sees everything, so before extending check the structure of supervisors' subtrees.
Quality of the record
From the pilot period collect the numbers: how many missing exits there were, how many changed exits, how many declared times, and how long supervisors took to approve them. Check the default thresholds: an uncertain exit after 89 minutes, a reminder call after 34 minutes and a classification tolerance of 13 minutes. If the exception queue has grown, change the thresholds before covering everyone.
Rules and roles
A supervisor cannot approve or correct their own record, so during acceptance establish who approves the records of supervisors. The period is closed and reopened only by the HR or administrator role, so test this on a real pilot period, not on demo data.
Product boundaries and expectations
The module was piloted on one installation. Do not write in acceptance documents that it is widely deployed or that it calculates pay. The schedule screens, the HR tab and the ERP export are at the preview stage with demo data, so in the protocol describe them as development options with a separate date.
Default thresholds to review at acceptance
Evidence and documents for the acceptance protocol
Attach three pieces of evidence to the protocol: screenshots of the exception queues from the last week of the pilot, the PDF timesheet for a sample employee from each shift, and the record of closing and reopening the period. Such a set shows the auditor that acceptance was not a formality and that the time record after the pilot works on real data.
How to organise acceptance in practice
It is best to hold one acceptance meeting with the project manager, HR and two supervisors from different shifts. Each point on the list is walked through on screen, on live data, and entered into the protocol. Open points get an owner and a date, and extending to all halls is conditional: only after the critical points are closed, namely the record, the roles and the period closing.
Checklist
Video
Frequently asked questions
After the pilot, is the module already deployed across the whole plant?
No. The module was piloted on one installation, and extending it to the halls requires acceptance and emptying the tester list.
What does an empty tester list mean?
The module is visible to everyone. That is why emptying the list should be the last step of acceptance.
Who should sign the acceptance?
The project manager and HR, with the participation of at least two supervisors from different shifts.
Sources
Let's plan acceptance after your pilot
We will prepare an acceptance protocol with the points from this list and lead the meeting with HR and supervisors. Book a conversation with the InnerWeb team.
Let's talk