Ask for the evidence you need, reuse what is current and resolve gaps with focused clarification rather than repeated applications.
Reduce applicant burden by asking only for information that supports a decision, reusing current evidence where permitted, and sending focused clarification requests instead of asking for a complete resubmission. When information is missing or contradictory, identify the exact issue, explain what response is needed and apply a clear deadline and review policy. AI can help prepare the request; a person should check that it is necessary, fair and accurate before sending it.
By Sopact Academy · Updated September 11, 2026. This lesson combines cited public guidance with practical workflow recommendations. Figures and teaching scenarios are illustrative unless explicitly identified as a published case.
Grant Intelligence · Chapter 8 · Collect
Bring: the incomplete or conflicting test submission from chapter 7.
Leave with: a focused clarification request, an owner and deadline, and a record of how the response changes the review. The message below is a fictional teaching example, not an instruction to contact an applicant.
A faster request for unnecessary information is still unnecessary work. Review your questions and attachments before building reminders. For each item, name who uses it, what decision it informs and whether you already hold a current version.
The Trust-Based Philanthropy Project’s paperwork guidance recommends options such as accepting existing proposals, using a short initial screening stage and learning through conversations. These are practices to consider in context, not a reason to ignore the specific requirements of a competitive grant round.
Keep the applicant’s effort proportional to the stage. A brief expression of interest may establish fit before a full budget is necessary. If you accept an existing document, tell the applicant which additional details you need instead of requiring a new format for the same facts.
In a 2018 account by the Robert Sterling Clark Foundation, Lisa Pilar Cowan described accepting proposals prepared for other funders and using follow-up research and conversations to learn more. The foundation also developed an oral reporting process with questions shared ahead of the conversation.
This is a published example of a funder changing its process. It is not a Sopact customer story, an AI implementation or a quantified claim about time saved. Its useful lesson here is that clearer learning needs can reduce repeated paperwork.
Clarification resolves an ambiguity or a missing item within the rules of the round. A substantive revision changes the proposal. Decide which is permitted before asking an applicant to respond.
| Issue | Possible clarification | What needs separate policy judgment |
|---|---|---|
| Two budget totals disagree | Confirm which total is correct and identify the supporting calculation | A materially revised budget or new funding request |
| Attachment cannot be opened | Provide a readable copy of the same document, if permitted | A new document created after the deadline |
| Participant count lacks a period | State the period used for the submitted count | Changing the target to improve the proposal |
| Partner role is unclear | Explain the commitment evidenced in the submission | Adding a new partner after the deadline |
A reviewer should not quietly coach one applicant into a stronger proposal while others receive no equivalent opportunity. Record the policy basis, the permitted response and the reason for any exception. A correction that seems small to the reviewer may affect the competitive outcome.
Group related questions so the applicant can respond once. Include the application identifier, the exact source of the issue, the requested action, the response channel and the deadline. State what does not need to be resubmitted.
Illustrative message · review before use
For application A-104, the form lists a total project cost of $120,000, while the uploaded budget shows $125,000. The grant request is $75,000 in both places.
Please confirm the intended total project cost and identify the line or calculation that explains the difference. If the round’s correction policy permits a revised file, attach it as a new version and describe the change. You do not need to resend the rest of the application.
Please respond through [approved channel] by [date, time and time zone]. If the request is unclear or you need an accommodation, contact [program contact]. This request does not indicate an award decision.
The placeholders are deliberate. A real request needs the actual policy, contact, channel and deadline. Do not send a draft that leaves those choices to the applicant or implies that every budget revision will be accepted.
In a configured Sopact workflow, AI can flag a possible inconsistency and draft a focused request from the linked application evidence. The program owner should verify both source values and the extraction before approving the message.
For a $120,000 versus $125,000 discrepancy, first check whether one figure includes indirect costs, uses a different period or belongs to an earlier file version. The difference may already be explained. A careful reviewer can avoid sending an unnecessary question by reading the related evidence.
Do not let a draft introduce new requirements, promise eligibility or imply that the applicant is at fault. A request should identify what is unclear and why the information is needed. Keep the authorized person responsible for the communication and final assessment.
Watch the method · 4 minutes 43 seconds
This Sopact demonstration covers the review stage. Use it alongside the broader application-to-report method in this chapter; people still verify evidence and make decisions.
Watch on YouTube if playback is unavailable · Browse the video library
Store the request, approval, send date, response and source versions with the application. Mark the issue as resolved only after a reviewer checks the answer. “Response received” and “sufficient evidence” are different states.
If the response does not resolve the issue, decide whether another request is permitted and useful. Do not repeat messages indefinitely until the applicant produces the desired answer. Preserve an unresolved outcome when that is what the evidence supports.
Use plain language, accessible formats and a named contact. Let applicants know when they can reply with a short explanation rather than an entirely new document. Where a conversation is appropriate, share the questions in advance and record an agreed summary.
Check what information a reviewer can already access legitimately. Asking again for an unchanged document may add no value, but an old financial statement or a different program’s budget may not be suitable. Reuse requires a currency and relevance check, not blind copying.
Keep accommodations distinct from merit. An applicant’s need for an accessible format or an approved extension should not silently reduce their score. Follow the published process and applicable organizational requirements.
Track a small set of operational measures for comparable rounds: the share of applications needing clarification, number of requests per application, time from response to review, and the issues that recur. Ask applicants which requests were unclear or duplicative.
Interpret these measures together. Fewer requests could mean clearer intake, but it could also mean reviewers stopped checking. Faster completion may reflect a simpler round or a different applicant mix. Review sample records and feedback before attributing improvement to a tool or a policy.
If the same question keeps causing confusion, fix the original field, instructions or evidence requirement. The durable improvement happens upstream, not through an ever-larger reminder queue.
Pass condition: another team member can understand the issue, the applicant’s response and the review conclusion without searching a separate inbox. The record shows what changed and what remains uncertain.
Remove unnecessary questions, reuse current evidence where permitted, explain requirements clearly and use focused clarification instead of complete resubmission. Check whether the information supports an actual decision.
Include the application identifier, exact issue and source, requested action, response channel, deadline and contact. Explain what need not be resubmitted and verify that the request follows the round’s policy.
That depends on the published rules. Clarifying existing evidence and materially improving a proposal are different actions. Use a consistent policy and record approvals or exceptions.
Use AI to prepare drafts where configured, with an authorized person checking the source, necessity and policy before sending. Do not let a generated message invent a requirement or imply an award decision.
When a reviewer has assessed the response and recorded the conclusion. A reply arriving does not necessarily mean the evidence is sufficient.
Set a proportionate reminder and escalation policy for the round. There is no universal number. Avoid repeated messages without a clear purpose, and preserve unresolved status when appropriate.
Compare similar rounds using clarification volume, repeated requests, review delay and applicant feedback. Check evidence quality too; fewer requests alone do not establish improvement.
After an award, unclear report fields create the same cycle of repeated requests. Carry forward the approved definitions and ask only for information that serves a reporting or learning purpose. Keep the application promise, amendment and reported result distinguishable.
Previous: collect applications with usable evidence →
View the Grant Intelligence course →
Bring a recurring application issue and your clarification policy. Explore a workflow that keeps requests, responses and review decisions connected.
Explore Applications & Grants →
