Additional course links
By Sopact · Updated September 12, 2026
This lesson is for portfolio operations, impact and grant teams managing recurring partner reporting. Bring the reporting package from the related lesson. You will build a follow-up register, define when a reminder should stop, and practice reporting incomplete coverage honestly.
- Confirm what was agreed and when it is due.
- Classify the gap before contacting the partner.
- Assign one owner and consolidate the request.
- Use a reminder schedule with clear pause and stop rules.
- Review the response and retain the correction history.
- Disclose remaining gaps at the reporting cutoff.
What counts as missing investee data?
A gap exists when information required for an agreed reporting purpose is unavailable or cannot yet be used. An empty field does not tell you why. It might be overdue, not applicable, not yet measured, inaccessible or awaiting review. Those situations need different responses.
Use the partner’s reporting agreement and current data dictionary to decide what is expected. Do not classify an annual social audit as missing from a quarterly update if it is not due. Check whether a contact has already supplied the information in an accepted document or another approved channel before asking again.
| Situation | What it means | Next action |
|---|---|---|
| Not received | An agreed submission is due and no usable receipt is recorded | Confirm delivery and request the submission |
| Partially received | Some required components arrived; others did not | List only the outstanding components |
| Clarification needed | Evidence arrived but its period, definition or interpretation is unclear | Quote the specific discrepancy and ask one focused question |
| Access problem | A file was shared but the reviewer cannot open it | Resolve permissions or agree another secure route |
| Not yet due or not applicable | The agreement does not require this item now | Record the reason; do not send a missing-data reminder |
| Unavailable | The partner confirms that the observation does not exist | Record the limitation and agree the next measurement opportunity |
Principle 6 of the Operating Principles for Impact Management calls for an agreed process covering collection frequency, methods, sources and responsibilities. The register below is a practical way to organize that work. It is not an official template or evidence of compliance.
Build one register for requests and responses
Keep one row for each outstanding requirement, linked to the organization and reporting period. The row should identify the evidence needed and the next action, not simply label the partner “late.” One organization may have several requirements with different owners and dates.
| Field | What to record |
|---|---|
| Organization and period | Stable partner ID and reporting window |
| Requirement | Measure or document, dictionary version and reason it is needed |
| Original due date | The agreed date; retain it if an extension is approved |
| Current status | Not received, clarification needed, access problem or other defined state |
| Contact and internal owner | Authorized partner contact and one responsible relationship owner |
| Latest evidence and communication | Source link, response date and the question already sent |
| Next action and date | Reminder, review, call or accepted extension with its owner |
| Closure record | What resolved the request, who checked it and when |
A spreadsheet can support a small portfolio if everyone works from the same version and permissions are appropriate. The difficulty grows when files, survey answers and email replies update independently. Whatever tool you choose, verify that a response changes the status of the right organization, requirement and period.
Write a reminder that the partner can answer
A useful reminder names what is already received, what is missing, why it matters and how to respond. Do not ask the partner to resend a complete package when only one denominator or a document date is missing.
Reusable message template. Replace every bracketed field before using it:
Subject: [Organization] — [period] reporting clarification
Thank you for sending [items received]. We are reviewing the update for [reporting purpose]. We still need [specific item or clarification], using [definition and period].
Please [reply through the agreed channel or update the named record] by [agreed date]. You do not need to resend [accepted items]. If the information is unavailable or the date is not workable, please tell [owner] so we can agree the next step.
Reference: [request ID and authorized source link].
Use the channel agreed with the partner. Keep sensitive personal or financial material out of broadly copied messages; link to the authorized workspace instead. If a file link fails, resolve access before treating the report as absent.
When should reminders pause or stop?
Pause routine reminders when a response arrives, an extension is agreed, a contact problem is identified or the request enters review. Close the request after the reviewer confirms that the requirement is resolved, or records why it cannot be resolved for this period.
The following schedule is illustrative, not a universal service standard. Choose intervals with partners around the reporting agreement, local working days and urgency.
| Trigger | Action | Pause or stop condition |
|---|---|---|
| Before the agreed due date | Optional reminder of the specific upcoming requirement | Already received, exempted or extended |
| Due date passes with no receipt | Check other accepted channels, then send a focused reminder | Any relevant response moves the request to review |
| No response after the agreed interval | Relationship owner checks delivery, contact changes and capacity | Contact issue or agreed revised date |
| Response arrives | Acknowledge receipt and review the evidence | Stop the missing-submission sequence; use a clarification task if needed |
| Reporting cutoff arrives | Record unresolved coverage and its effect on conclusions | No indefinite automated chasing; owner agrees next action |
Do not run several reminder sequences for the same requirement. Test whether a reply, replacement upload or approved extension cancels a queued message. A system that receives a response but sends “we have not heard from you” the next morning undermines trust.
If follow-up is automated, specify the conditions, delivery channel, responsible owner and maximum escalation path before enabling it. Do not assume the software can detect every email response or file change. Test those routes with sample records and inspect the message log.
Practice: resolve three different gaps
Fictional exercise. Three organizations owe the same quarter’s agreed reporting package. Partner A has submitted its metric and narrative, but a financial document is missing. Partner B’s files are complete, but its reported job-start count includes five offers that start next quarter. Partner C has not responded; its main reporting contact has left.
- Partner A: mark the package partially received. Request only the required financial document and confirm the accepted metric and narrative.
- Partner B: stop missing-report reminders. Open a clarification about the definition and the five records, using the definition and source dates.
- Partner C: pause reminders to the departed contact. The relationship owner identifies an authorized replacement and agrees a workable response date.
After Partner A supplies the document, record receipt and review it. After Partner B confirms a corrected count, retain both the original and corrected value with the explanation. Partner C remains unresolved until a usable response or a documented limitation is recorded. These are different actions even though all three packages were initially incomplete.
How do you report when gaps remain?
Describe coverage for the specific measure, not just how many organizations uploaded a file. A package can be received while a key outcome remains unusable. Keep the denominator of expected responses visible and distinguish missing observations from measured zeroes.
Illustrative arithmetic. If eight of ten organizations supplied comparable, usable values for a measure, organization-level coverage is 8 ÷ 10 = 80%. If their observed total is 240, report “240 across eight reporting organizations; two remain unresolved,” rather than presenting 240 as the full portfolio result. This does not tell you the share of invested capital or people covered; calculate those separately if relevant and supported.
Do not fill gaps with zero or last quarter’s value without explicitly identifying the treatment. If an estimate is justified for a separate analysis, label it, explain the method and show which results are observed. Missingness may be uneven: partners with less capacity or more difficult results may respond differently. A high response rate alone does not establish an unbiased portfolio estimate.
For the reporting handoff, retain the cutoff date, unresolved requirements, attempted follow-up, affected measures and planned next action. Use the impact reporting guide and report examples to plan how limitations will be presented alongside results.
Improve the next reporting cycle
Review the reasons for repeated gaps before increasing reminder frequency. Unclear definitions, duplicate requests, an inaccessible upload route or a deadline before the evidence exists cannot be fixed by sending more messages.
- Count repeated clarification topics and revise the relevant question.
- Check whether one requirement creates disproportionate effort.
- Confirm contacts and backup coverage before the next cycle.
- Measure time from receipt to review as well as time from request to receipt.
- Check for reminders sent after a response or approved extension.
- Discuss persistent capacity constraints with the partner and agree support or a revised process.
Late reporting is a process signal to investigate. It is not, by itself, proof of poor impact performance or misconduct.
Watch the portfolio reporting demonstration · 2 minutes 16 seconds
A Sopact demonstration of connected portfolio records and reporting. This demonstration introduces the connected reporting record. Reminder support and stop rules must be checked separately against your requirements.
What should you test in Sopact?
Start with the three fictional situations above or an authorized sample from your own portfolio. Test whether a survey answer, upload and clarification stay linked to the same partner and period. Confirm that reviewers can see what was received, what remains uncertain and the source behind a corrected value.
Then check the follow-up workflow you intend to use: contact matching, permissions, status changes, reminder support and stop rules. Any notifications or integrations need to be confirmed and configured. AI may help identify candidate gaps or contradictions; the relationship owner should resolve ambiguous evidence and consequential escalations.
The result to seek is one clear history of the request and response, with less repeated assembly. Measure that improvement in a pilot rather than assuming that automation removes all work.
Frequently asked questions
How often should we remind an investee?
Agree an interval appropriate to the reporting commitment and partner’s working context. Check delivery and ownership before repeating reminders. Pause when a response, extension or contact issue changes the next action.
Is an uploaded report a complete submission?
Not necessarily. Confirm that required measures, periods and supporting evidence are usable. Treat an unclear value as a clarification task rather than pretending the report never arrived.
Can missing values be recorded as zero?
No. Zero means the measure was observed and its value was zero. Missing means the value is unknown or unavailable. Keep those states separate in calculations and reports.
What if an investee cannot provide the information?
Record why, identify the reporting limitation and agree what can be collected next. Consider capacity support or a better-timed request. Do not invent a replacement result.
Can follow-up be fully automated?
Routine reminders can use configured rules where the system supports them. Exceptions, inaccessible files, changed contacts and ambiguous responses still need review. Test stop rules before relying on automation.
What should we retain for the next reporting cycle?
Bring the accepted reporting package, unresolved questions, definitions and source links. Use those materials in the report-review reference when you need to read financial, quantitative and qualitative evidence together.
Bring the result back to your module
Related practice: read investee reports across financial, quantitative and qualitative evidence. Keep unresolved gaps visible as you interpret the results.