Onboarding: exception and recovery register
This register records what goes wrong while a business is being set up to run its work in a structured way, and what was done to recover. It is used by the setup lead, the owner and the department heads, so each snag is dealt with once and the same snag does not appear at the next branch.
When to use it
Use it whenever the setup does not follow the plan: staff cannot agree on how the business should be described, branches follow different rules, a key person is absent, or the setup is interrupted halfway. Look at open lines every week until the trial is closed. Anyone on the setup team may add a line, but only the setup lead or owner may close it. This stops a problem from being declared solved by the person who caused it.
The template
Part 1: common exceptions and the usual recovery.
| Exception | How it shows up | Usual recovery step | Who decides |
|---|---|---|---|
| Business type is unclear | The profile fits two trades, or the team disagrees on what the main activity is | Take the activity that brings most of the revenue as the base; note the rest as extras | Owner |
| Branches with different rules | One branch uses its own forms, credit terms or approval limits | Write each difference down; decide which become common and which stay local | Owner and branch heads |
| Interrupted setup | A session stopped halfway; entries partly made | Note the last completed step, restart from there, and fix a date | Setup lead |
| Key person absent | The named owner of a process is on leave or has left | Name a temporary owner in writing, with dates | Operations manager |
| Staff unwilling to report | Entries missing for several days from one team | Meet the team head, find the cause, and agree a simpler way to report | Owner |
| Records missing or inconsistent | Opening figures do not match the books | List the differences and take the source the CA accepts | Accounts lead |
Part 2: the register.
| Date found | Area or branch | Exception | Effect in ₹ or hours | Owner | Recovery step taken | Next check | Closed on |
|---|---|---|---|---|---|---|---|
How to fill it
- Exception: choose from Part 1 and add a line of detail, or add a new type.
- Effect in ₹ or hours: the cost of the delay: staff hours lost, an order held, or a cost already paid. Write 0 if none.
- Recovery step taken: what was actually done and on what date.
- Next check: a date when someone confirms the recovery has held.
- Closed on: fill only when evidence is on file, such as the revised role list or a note from the branch head.
- A mismatch in tax, payroll or statutory books is a statutory matter. Check the current rule on the official portal or with your CA before acting.
Example row
| Date found | Area or branch | Exception | Effect in ₹ or hours | Owner | Recovery step taken | Next check | Closed on |
|---|---|---|---|---|---|---|---|
| 29 Oct 2026 | Pune branch | Branch allows credit of 45 days; head office allows 30 | ₹92,000 over terms on 4 customers | Owner | Joint call 31 Oct; branch moves to head-office terms from 1 Dec 2026 | 15 Dec 2026 |
Review and sign-off
- The setup lead reviews the register weekly; the owner signs it off at the end of the trial.
- Group exceptions by type each month. A type that repeats means the plan needs changing, not just the case.
- Escalate to the owner at once for any exception that stops a process from starting or puts customer money or stock at risk.
Keeping it up to date
- Do not delete lines; mark them closed so the history remains.
- Keep the register for the period your CA or the law requires.
- Carry the lessons into the plan for the next branch or department.
- Once a quarter, read the closed lines together with the team heads and ask which of them could have been avoided by a clearer instruction at the start.