Onboarding: control and audit worksheet
This worksheet checks whether the setup of a new way of running daily operations was done properly, using the actual records instead of a general impression. It is used by the owner, the person leading the setup and, where possible, someone outside the setup team who looks with fresh eyes.
When to use it
Use it at the end of the first two weeks of a setup, again when the trial period closes, and whenever a new branch or department is added. Test the setup against the written records: if a control point has no record behind it, treat it as not done, however well people remember it. Keep the test short and factual: it should take no more than an hour, and everyone should know in advance which records will be opened.
The template
Part 1: control points.
| Control point | What to check | Evidence to look at | Reviewer | Result found |
|---|---|---|---|---|
| Business profile written | Products or services, locations, team size, busy season and ways of working are described | Business profile sheet | Setup lead | |
| Reporting channel chosen | One channel is agreed for daily updates and every team member has been added | Channel member list, first week's messages | Owner | |
| Problems ranked | Top operating problems are listed in order with a rupee estimate of the loss | Problem ranking sheet | Operations manager | |
| First processes confirmed | The processes to set up first are named, with start dates | Process list signed by the owner | Owner | |
| Roles named | Each process has an owner, a doer and an approver by name | Role list | Setup lead | |
| Trial run reviewed | A trial period ran with real work and the results were discussed | Trial notes, entries made | Operations manager | |
| Changes made after trial | Responsibilities were adjusted where the trial showed a problem | Dated changes in the role list | Setup lead |
Part 2: findings log.
| Control point | What was found | Effect in ₹ or hours | Fix | Owner | Due date |
|---|---|---|---|---|---|
How to fill it
- Result found: write what you saw, for example "complete", "two staff not added to the channel" or "no ranking sheet". Avoid plain ticks.
- Evidence to look at: note the date or file name opened, so another person can repeat the check.
- Effect in ₹ or hours: estimate the cost of the gap, such as weekly staff hours lost or a monthly loss in rupees. A rough number with a stated basis is enough.
- Fix and Owner: one named person per fix. A finding that touches payroll, tax or labour records is a statutory matter. Check the current rule on the official portal or with your CA before acting.
- Due date: a calendar date.
Example row
| Control point | What was found | Effect in ₹ or hours | Fix | Owner | Due date |
|---|---|---|---|---|---|
| Roles named | Dispatch has a doer and an owner but no approver; two challans in the first week went out unsigned | About 3 hours a week of rework | Name the stores manager as approver and tell the team in writing | Setup lead | 12 Nov 2026 |
Review and sign-off
- The reviewer signs each control point tested, and the owner signs the whole sheet with the date.
- Run it at the end of week two, at the end of the trial, and at three months.
- Escalate to the owner at once if a process has no named owner, or if staff are working outside the agreed channel.
Keeping it up to date
- Add a control point whenever the setup fails in a way not covered here.
- Keep completed worksheets for the period your CA or the law requires, or longer if the owner wants a record of how the setup grew.
- Compare each run with the last one: repeated gaps point to a weak role or an unclear instruction.