Use this workflow when documents have been requested but clients have not sent everything needed for bookkeeping, tax preparation, cleanup, or month-end close. CollectCue is a focused, lightweight client document request workflow for small bookkeeping firms that supports the request, reminder, tracking, and review stages described here.
Browse the resources hubStop rebuilding each follow-up from the original request. Start with the current items that still need client action, send one focused reminder for those items, and move uploaded files into staff review instead of chasing the client again.
A clarification request asks for missing context. A replacement request asks for a corrected file after review. Neither action determines the final accounting treatment.
Decision point
Trigger
Clarification request
The transaction or uploaded document exists, but staff still needs factual context or a specific answer.
Replacement file request
Staff reviewed the submitted file and identified a file-specific problem such as a wrong period, missing pages, unreadable content, or the wrong document.
Decision point
Client action
Clarification request
Answer the specific factual question and provide supporting context if requested.
Replacement file request
Upload the requested replacement for the original item.
Decision point
Workflow status / next action
Clarification request
Do not invent a new Clarification status. Keep the actual request or item status and make the remaining client action clear.
Replacement file request
After staff review identifies the problem, use Needs reupload and keep the replacement tied to the original requested item.
Decision point
Reminder behavior
Clarification request
Only remind while a client action is genuinely outstanding.
Replacement file request
Remind for the replacement only after staff has requested reupload.
Decision point
Common failure
Clarification request
Asking for a new file when only a factual answer is missing.
Replacement file request
Creating a loose new request and losing the original item, period, and review context.
Move every request through the same sequence so reminders are specific, timely, and tied to real blockers.
Use the workflow as the operating rhythm for every missing-document queue.
Use these answers to standardize follow-up rules across the team.
A practical cadence is original request, reminder after the due date, second reminder when the item blocks work, and escalation only when the document affects a deadline or deliverable.
Only generate reminders from items in Waiting on client or Needs reupload. Items in Uploaded / Pending review are staff-owned, and items that are Received or Not applicable are resolved, so none should appear in client reminders.
Each request should have an internal owner and each missing item should have a client owner. This prevents broad reminders that no one can act on.
Escalate when an item blocks reconciliation, tax preparation, month-end review, filing work, or a client deliverable.
Use these pages when follow-up needs better templates, checklists, or operating rules.
Use the core checklist when the firm needs a full missing-document request by client and period.
Open resourceUse the tax-season checklist when W-2s, 1099s, prior-year returns, and tax support are still outstanding.
Open resourceUse status-based wording for each reminder and escalation level.
Open resourceSee how client, period, requested items, reminders, uploads, and review status stay connected in one request.
Open resourceTurn the follow-up cadence into a documented firm procedure.
Open resourceUse tax-specific request language when follow-up happens during filing season.
Open resourceTurn follow-up steps into request status, reminder scheduling, client owner tracking, and close-ready review queues.
