Additional course links
How do you follow up on missing grantee data?
By Sopact Academy · Reviewed September 12, 2026. This lesson combines cited public guidance with practical workflow recommendations. Figures and teaching scenarios are illustrative unless explicitly identified as a published case.
Resolve one gap without chasing the whole report
Bring: the sample reporting request and test submission from How to Collect Grantee Reports with Less Burden.
Leave with: a small issue register, a focused follow-up message and a rule for resolving, pausing or escalating the issue. The examples are fictional and do not prescribe a universal grant policy.
Find out what is actually missing
“Incomplete report” is too broad to guide a useful response. A report may be absent, a file may be inaccessible, a count may lack a definition or an outcome may not yet be measurable. Each problem needs a different action.
| What you see | What it may mean | First action |
|---|---|---|
| No report received | Submission is late, sent elsewhere or assigned to an outdated contact | Check the agreed deadline, destination and contact before reminding |
| Required value blank | Omitted, unknown, not applicable or not yet due | Ask for the value or the reason it is unavailable |
| File link will not open | Access permission or an expired link | Request appropriate access or an accepted alternative |
| Number lacks a period or denominator | The value cannot yet be interpreted reliably | Request the definition rather than a new full report |
| Two sources disagree | Different scopes, versions, timing or a genuine error | Read the source context and identify the exact difference |
Missing and contradictory are not the same. “We do not have the number” differs from “we have two numbers that describe different things.” Preserve that distinction in the follow-up record so the grantee receives the right question.
Check your own records before contacting the grantee
Look at the agreement, approved amendments, earlier submissions and recent correspondence available to the authorized reviewer. The grantee may already have explained that the outcome will be measured after the cohort finishes, or a colleague may have granted an extension.
Confirm that the requirement applies to this grant and reporting period. A portfolio-wide field should not trigger a request when it is irrelevant to the funded work. If the agreed requirement is unclear, resolve that internally before presenting it as the grantee’s mistake.
For a failed extraction, inspect the original document. A scanned table, a footnote or a changed column heading may account for the apparent gap. If the information is present, correct the internal record and document the source instead of asking the grantee to submit it again.
Keep a small issue register
One row per issue is usually clearer than a single “late” label on the organization. A grantee can have a reviewed narrative and an outstanding financial clarification at the same time.
- Identity: grant, report, period and issue identifier.
- Gap: field or file, source reference and why it matters.
- Responsibility: internal owner and appropriate grantee contact.
- Timing: agreed due date, request date and next review date.
- Status: not requested, awaiting response, received for review, resolved or escalated.
- Evidence: request, response, new source version and reviewer’s conclusion.
Record an approved extension separately from the original due date. Otherwise an extended report may appear overdue and generate the wrong reminder. Avoid putting sensitive details into subject lines or broad notification lists.
Write a request that can be answered once
State what you already received, what remains unclear and the smallest action that will resolve it. Link to the relevant report or field through the approved access route. Provide a person to contact if the requested information is unavailable or the instructions are unclear.
The W3C’s guidance on form notifications recommends clear, concise feedback that identifies the relevant control and explains how to correct an error. Apply the same clarity to the collection form. This guidance supports accessible messages; it does not establish a grant reminder schedule.
Illustrative request · adapt to the agreement
Please clarify the employment follow-up count
Thank you for the quarterly report for grant G-104. We have received the narrative and financial attachment.
The outcome table lists 60 people employed, but it does not state how many people had a known employment status. Please confirm that count and the follow-up period. If the information is not available, tell us that rather than entering zero.
You can update the outcome field or provide the explanation through [approved response channel] by [agreed date and time zone]. There is no need to resend the narrative or financial file. Contact [named owner] if you need help or a revised date.
Replace every placeholder before sending. Check that the request uses the current agreement and does not introduce a new requirement after the fact. If several colleagues need information, combine their questions into one coherent request where possible.
Set reminders around status, not just the calendar
Agree a proportionate cadence with the program team. There is no universal rule that every grantee needs three reminders or a message every week. A request that blocks an imminent review may need earlier attention than information that is not yet expected to exist.
- Before sending: verify the issue, owner, recipient and due date.
- Before reminding: check for a response, extension, contact change or internal review in progress.
- When a response arrives: pause the pending reminder and assign the response for review.
- After review: close the issue, ask a narrower follow-up or escalate to the authorized owner.
- When the issue cannot be resolved: preserve the limitation and record the decision about its use.
In a configured Sopact workflow, linked report records and analysis can help surface gaps and prepare follow-up. Notification delivery, reminders and assignment depend on the workflow and connected channels that have actually been set up. Check those behaviors in a test round; do not assume that an AI summary sends messages or closes issues by itself.
Keep people responsible for exceptions and consequential decisions. An overdue field alone should not silently trigger a funding decision, a poor-performance label or an accusation of noncompliance.
Watch the explainer · 6 minutes 7 seconds
Help readers understand the evidence in a report
This Sopact video explains why sources, definitions and audience context matter even when the numbers are clean. Apply that lesson when deciding which missing evidence matters and explaining what a report can support.
▶ Play video: why clean reporting data still gets ignored
Watch on YouTube if playback is unavailable · Browse the video library
Worked example: the reply changes what you can say
Use this fictional cohort: 150 starters and 60 people reported as employed. The denominator for known employment status is missing from the submitted outcome field.
| Grantee response | Review result | What can be reported |
|---|---|---|
| Employment status is known for 100 of 150 starters; 50 remain unknown | Check the period and source, then resolve the missing denominator | 60% employed among 100 with known status; 66.7% follow-up coverage |
| The count 100 is from another cohort | Still unresolved; the denominator does not match the result | Do not calculate a rate using unrelated groups |
| We cannot recover the number with known status | Record the limitation and the owner’s decision | 60 reported employed, with rate and coverage unavailable |
The third answer can close the communication task without making the data complete. Keep those outcomes separate. A reviewer may decide the available count can be used with a limitation, while a rate must be withheld. Do not invent the denominator just to fill a dashboard.
Escalate the obstacle, not the person
When a grantee does not respond, examine the reason before sending more messages. The contact may have left, the request may be ambiguous or the organization may not have the capacity or records to produce the answer. Ask the program owner whether an alternative source, conversation or revised timing is appropriate.
Record the actual decision and who authorized it. If an issue affects a contractual or regulatory requirement, use the organization’s applicable process; this lesson does not replace it. Do not portray an internal reminder status as a legal conclusion.
If the same gap appears across many grantees, examine the collection design. A confusing denominator question is a funder process problem worth fixing. Repeatedly chasing it does not make the original question clearer.
Measure useful resolution
Track unresolved issues by type, time awaiting grantee response, time awaiting internal review and the share reopened after an inadequate answer. Also ask grantees whether requests were clear and duplicated information they had already supplied.
Keep the measures balanced. A high closure rate can hide issues closed without evidence. A fast reply does not prove the response is usable. Inspect a small sample of resolved records and check whether another reviewer can follow the conclusion.
Exercise: test the stop rules
Use one fictional report. Create three issues: a missing denominator, an inaccessible attachment and a result not yet due. Write the action for each, including one case where no message should be sent.
Then test a response arriving just before a reminder is due. Confirm that the record changes to received for review and the reminder pauses. Test an approved extension, an incorrect recipient and a reply that does not answer the question. Keep the results of these tests with the workflow setup.
Pass condition: another team member can see who owns the issue, why a message will or will not be sent, and what evidence is needed to resolve it. No blank is converted into a zero simply to complete the report.
Frequently asked questions
How do you follow up on a missing grantee report?
Check the deadline, contact and submission destination, then send a specific request through the agreed channel. Assign an owner and a next review date, and check for a response or extension before reminding.
Should missing data be entered as zero?
No. Zero is a known value. Missing, unknown, not applicable and not yet due have different meanings and should remain distinguishable.
How many reminders should a funder send?
Use a proportionate schedule based on the agreement, urgency and context. There is no universal number. Check the current status before every reminder and stop when the issue moves to review or an approved alternative.
When is a missing-data issue resolved?
After a reviewer checks the response and records the conclusion. A communication can end with an acknowledged limitation even when the requested data cannot be recovered.
Can AI automatically chase grantee data?
AI can help identify possible gaps and draft requests within a configured workflow. Actual delivery, reminder rules and escalation require an implemented setup and responsible owners; they do not eliminate review work.
What if the grantee cannot provide the information?
Record why it is unavailable, consider an appropriate alternative and have the authorized owner decide how the limitation affects reporting. Do not manufacture a value or keep sending the same request indefinitely.
What should a missing-data tracker contain?
Record the grant and period, precise gap, source, owner, contact, due date, status and the response or resolution evidence. Keep extensions and review conclusions visible.
Move from collecting evidence to reviewing it
Your issue register should now distinguish a received reply, a verified answer and a documented limitation. Return to the course module on reviewing applications with consistent evidence and criteria. Apply the same review discipline to the stage of work you are managing, including grantee reports. Carry forward the same habits: keep the source, distinguish uncertainty and record the human decision.
Related collection practice: collect grantee reports with less burden →
When preparing the final output, use the impact report writing ebook and example reports to make evidence and limitations clear to readers.