
Date:
Author:
A2.Ai
001
Give missing information a clear status
A form arrives without an attachment. A report appears after a draft is prepared. Two documents contain different details. These cases belong in the workflow design.
Create a checklist for one type of job. Separate information that is always required from information needed only in certain circumstances. Use useful statuses: not received, unreadable, needs clarification and ready for review.
Keep extracted information linked to its source so a reviewer can check or correct it.

002
Separate extraction from acceptance
Extracting a name or date does not establish that a document is suitable or sufficient. Check required fields, known identifiers and unexpected formats. Leave uncertain information unresolved rather than inserting a plausible guess.
Where personal information is involved, assess the AI product’s suitability, accuracy and data handling. The OAIC’s guidance on commercial AI products is a useful starting point, alongside the needs and obligations of the specific workflow.

003
Give every exception a next action
Each exception needs a reason, an owner and an allowed next step. A useful message might say that a statement for the requested period is missing and assign the request to the client-services team.
Let staff correct an input, ask for clarification or stop the job. Reminders need limits and should recognise when someone has already replied. Measure the effort spent resolving exceptions as part of the workflow.
Missing file: request it or record why it is not required.
Conflicting details: send the source material for review.
Duplicate submission: identify the existing job before creating another.
Late report: decide whether it changes the draft or requires another review.
004
Test the difficult cases
In our recent work, reports collected after an operator started the relevant searches helped prepare a draft and supporting pack. Late material, corrections and human review remained part of the process.
Test missing files, unreadable scans, conflicting identifiers, duplicates and late reports. Check both incorrect passes and unnecessary escalations. Once a document has progressed to signing, do not silently replace it with a new version.
A first release can improve collection and status tracking while leaving document acceptance with the existing reviewer.
Build clear ownership and recovery into the wider system
Book a free 30-minute discovery call to discuss your paperwork bottleneck.



