When they ask for documents from three years ago

The problem it solves

The request lands on an ordinary Tuesday and asks for paperwork from several closings back, on a deadline that leaves no room to rebuild anything. The company then finds that the information exists but is scattered: some in the old system, some in the mailbox of someone who has left, some in a drawer nobody has opened since the move.

What follows is two or three weeks of work nobody planned for. The administrative team stops doing its own job to hunt for paper. The outside accountant is asked for documents he was never the custodian of. Explanations get improvised for whatever cannot be found, and each explanation opens a fresh question.

The cost is not only the diverted time. A company rebuilding under pressure hands over too much, hands over too little, and answers questions nobody asked. The signal it sends is the one it can least afford: if the basic paperwork cannot be produced, it is reasonable to assume there is more worth looking at. Leaving it until the day it happens is a decision, even when nobody says it out loud.

What it covers

The day rests on a simple idea that is rarely practised: being ready is not having the paperwork, it is being able to hand it over. The gap between those two shows up in the inventory. In the first part, each area of the company, sales, purchasing, payroll, banking, lists which document supports each figure it reports, where that document sits today, and who holds it. The list is usually uncomfortable, and that is what makes it useful.

A sample evidence file is then assembled. Participants pick a period already closed and rebuild, from what the company actually has, the set of documents standing behind one specific figure. The exercise surfaces two things quickly: what is genuinely missing, and how long it takes to find what does exist. From those findings the group defines a file format the company can assemble in advance, closing after closing, instead of against the clock.

The afternoon turns to the response itself. In a simulation, one group receives a request for information while another plays the party that sent it. Participants practise handing over exactly what was asked for, with the document and without commentary, and they practise what to say when a document does not exist, which is the most delicate case and the one that improvises worst. By the end, it is clear who receives a request, who answers, who follows up and what gets recorded about each handover.

The close sets the rhythm that keeps readiness alive when nobody is asking for anything, and draws the line between what the company is responsible for and what its external adviser is. ALUD does not audit, does not certify and does not opine on any organisation's documentation: the programme is educational and does not replace specific tax, legal or accounting advice.

What participants learn

• Identify, area by area, which document supports each figure the company reports.
• Develop an evidence file format that can be assembled in advance, closing after closing.
• Design the response path: who receives a request, who answers it and who follows up.
• Apply the discipline of handing over exactly what was asked for, with the document and without improvised commentary.
• Evaluate what to do when a document does not exist or cannot be found, and how that is recorded.

Agenda

1. 01What being ready means, and what it does not
2. 02The evidence inventory, area by area
3. 03From a reported figure to the document behind it
4. 04One voice: who answers and who does not
5. 05Handing over what was asked for, and nothing more
6. 06When the document does not exist: what to say and what to do
7. 07A record of what was handed over, to whom, and when
8. 08Holding readiness as a permanent state
9. 09Where the company ends and its external adviser begins

What the organisation leaves with

• An evidence inventory by area, with each document's current location and custodian.
• An evidence file format, tested against a period that is already closed.
• A one-page response protocol: who receives, who answers, what gets recorded.
• A handover log showing what was produced, for whom, and on what date.