Define what counts as incomplete
An incomplete document is one that cannot move to its next step as intended. A form may lack a required field, an attachment may be missing, or a scan may cut off part of a page. The problem is not always obvious: a file can open correctly and still be unusable because its purpose or owner is unclear.
Set a short checklist for each common document type. For an incoming form, that might include all expected pages, readable text, the necessary contact details, and any required attachments. Keep the checklist focused on what the next person needs to do their job. A consistent check at intake is easier than discovering a gap after several people have handled the file.
Give the document a visible holding status
When a document fails the check, do not leave it in an ordinary inbox or move it into a completed folder. Give it a clear status such as “Waiting for information” or “Needs a clearer scan.” A shared tracker, task board, or designated holding folder can work; the important feature is that someone can see which items are paused and why.
Record the document’s identifier, the specific issue, who is responsible for the next action, and when to check again. Use the minimum identifying detail needed in a tracker that others may see. If the document contains sensitive information, keep it in its approved storage location rather than copying its contents into a note or chat message.
Avoid vague entries such as “Please fix.” “Page two is missing from the submitted form” tells the next person what to request and gives them a way to confirm that the problem has been resolved.
Ask for one clear correction
A useful follow-up request identifies the document, describes the gap, and explains what would let work continue. For example: “We received the application, but the second page was not included. Please send that page so we can continue processing it.” If several details are missing, put them in one concise request rather than sending a series of messages as each gap is noticed.
Choose a communication channel that fits the document and the people involved. A routine clarification may be easy to handle by email; a sensitive attachment may require an approved file-sharing method. Avoid asking someone to resend an entire document when a single missing page or a clearer image would suffice, unless replacing the whole file is necessary to keep the record coherent.
Decide who sends the request and who watches for the reply. Without that ownership, two people may contact the sender while each assumes the other will pick up the corrected document. If a reply does not arrive, the assigned person can follow up according to the team’s usual schedule rather than relying on memory.
Return the corrected item to the normal path
When new information arrives, check that it actually resolves the recorded issue before changing the status. Match a replacement page or attachment to the right document, and make sure the combined record is readable and complete. If the correction creates another question, update the same holding entry so the next action remains visible.
Once the check passes, move the item to its normal next step and notify the person responsible for that step if needed. Note that the issue was resolved, then close the holding entry. This prevents an old reminder from prompting another request and makes it easier to distinguish active exceptions from finished work.
Periodically review the holding list for items with no owner or no recent action. Patterns can point to a fix at intake: if scans are often cropped, adjust the scanning check; if a form regularly arrives without an attachment, make the requirement clearer before submission. The aim is not to build a complicated exception system. It is to ensure that every paused document has a known problem, a next action, and a way back into the workflow.
