Chasing documents
Why a missing document is not a review point, how the chase list is built, and what to send the client.
Source reviewed Product documentation
A build produces two kinds of output that people constantly merge, and should not.
| Review point | Chase | |
|---|---|---|
| What it is | A judgement the AI made | A document that is absent |
| Where it shows | Against the workpaper line | The Awaiting panel |
| What you do | Reply to it, or ignore it | Ask the client through Email or Message |
| Who resolves it | You | Them |
"This looks like a private-use apportionment" is a review point. "There is no June bank statement" is a chase. Putting the second in your review queue means sitting on a task you cannot complete.
The Awaiting panel is the whole list, and it keeps what has already arrived struck through rather than deleting it — so "have we asked for this yet" has an answer after the fact.
How the chase list is built
Not by counting files. A chase line has an identity — what kind of document, which period, which instance — so twelve monthly BAS is not "BAS: 12 uploaded" but a period with gaps in it. A missing quarter is a gap in a range, and that is how it is reported.
Sending it
Choose Chase to open a draft under Email, or switch to Message for the portal conversation. Check the selected documents and edit the wording before you use Mail app or Copy. See Request missing documents.
Chases do not block a build
You can build a workpaper with documents outstanding, and often should — the result tells you what the gaps actually cost. What you cannot do is treat that build as final.