The minimum you need this quarter (not a manual that never gets read)
The goal is not a perfect knowledge base in a fortnight. It is a safe minimum so someone else can run payroll, quotes, dispatch, or month-end on day one without a panic. The same single point of failure shows up in operational technical debt and when a spreadsheet is the brain — not because Excel is wrong, but because nobody else can be the system of record without a runbook when it all lives in one person's head.
Book a free systems review if you are under time pressure. We work in Teesside and the North East and remotely when the fit is right.
The three artefacts that matter first
Access, admins, and MFA — Who can get into what, who is admin on the systems that matter, who holds the second factors, and the practical path when someone is off sick or locked out. No séance in the group chat; a named reset path and a second person who can approve.
"How I actually do it" (one page + one walkthrough) — Not a 40-page manual. One page of the real order of operations: where you click, what you check, what good looks like, plus a 10–15 minute walkthrough (Loom or a paired run in the live tool). The point is to catch the tacit stuff: the export you run after the import, the field everyone forgets, the do not touch row that is load-bearing for everyone else.
Where the truth lives — For each line of work, name the system of record: quotes, stock, job status, invoice, payroll. If truth is split between a system and a sheet, say that in plain language — the handover version of when a spreadsheet is the brain. Clear ownership for system work is the policy side; a handover is when key-person risk is visible in the room.
Ongoing system care helps keep these three pieces from going stale after go-live: small updates when the stack or the people change.
Pair before solo (no deep-end Friday)
The worst pattern is here are the logins on Friday and a full inbox on Monday. Better: shadow a full cycle, pair the next, then solo with the expert on standby. You are testing muscle memory, not a password. It is the same discipline as a calm go-live: see the first 30 days after a build when a new system lands; here the system is the same, but the person is not.
If you are also changing how work moves, not just who does it, our offers cover process audit, build and integration, and rescue and rebuild when the quarter is already a rescue not a greenfield.
Buses, and the minimum that still helps
You will not get a perfect pack in a week. A credible one is still: access and reset paths, one honest how I do it page with a walkthrough, and a named system of record. Book a free systems review and we will pressure-test the pack with you, and point at the thinnest next move from what we offer if you need more than documentation.