Design a shared reporting core, accept useful existing documents and ask only for the clarification needed. A practical worksheet for portfolio teams.
By Sopact · Updated September 12, 2026
Reduce investee reporting burden by collecting a small shared core, adding only the questions relevant to each organization, and reusing existing evidence where it fits. Keep definitions, reporting periods and source references consistent. Review each submission for missing or conflicting information, then ask for the specific clarification needed rather than another complete report.
This lesson is for portfolio and impact teams collecting quarterly or other recurring updates from investees or grantees. Bring the reporting agreement and diligence handoff. Leave with a tested reporting request, a review checklist and a short clarification message.
Build and test the request in six steps:
Before adding a question, name its purpose. Will someone use the answer to review an agreed target, investigate a concern, meet a reporting commitment or decide what support is needed? Remove requests with no clear use, or keep them optional and explain why.
A quarterly update should not repeat the application. Stable information can be confirmed or corrected rather than retyped. Collect observations at a frequency that fits the measure: a financial update, an annual outcome follow-up and a social audit do not necessarily belong on the same schedule.
| Information | How to request it | What to avoid |
|---|---|---|
| Stable organization details | Confirm the existing record and flag changes | Re-entering the same address, contacts and description every cycle |
| Shared portfolio measures | Use the agreed definition, unit and reporting window | Similar labels with different denominators |
| Partner-specific outcomes | Show the relevant questions from that partner’s agreement | Making unrelated organizations complete identical indicator lists |
| Supporting documents | Accept the existing file when it covers the required evidence | Reformatting a useful report only to match a preferred layout |
| Exceptions and learning | Ask what changed, why and what needs attention | Collecting a narrative that no reviewer reads |
Principle 6 of the Operating Principles for Impact Management connects ongoing monitoring with the expectations established before investment and the response when performance differs. The reporting package below is a practical exercise for that review cycle, not an official reporting template or a claim of compliance.
Each submission needs an organization identifier, reporting period and responsible contact. Attach the metric, explanation and supporting file to that same reporting record. A filename alone is not a reliable identifier.
The following package is illustrative. Include financial documents or audits only when the agreement and purpose require them.
| Part | Example input | Context to retain |
|---|---|---|
| Measure | People who started paid work this quarter | Definition version, period, count and relevant denominator |
| Explanation | What helped or limited placements? | Question asked, respondent and observation date |
| Document | Existing financial report or employment verification summary | Document date, coverage, source and review status |
| Conversation | Relevant partner check-in notes or an authorized transcript | Meeting date, participants, consent and access requirements |
| Review | Accepted figure or a question needing clarification | Reviewer, decision, reason and correction history |
Where files come from Google Drive, Dropbox, Box or SharePoint, agree how access and imports work before relying on them. A supported connection or an upload route must be configured and tested. Do not assume that a shared link guarantees continuing access.
Fictional example. Partner A submits 40 job starts, an explanation that says 35 people began work, and a spreadsheet containing 40 rows. Five rows are accepted offers with start dates next quarter. The organization also uploads its existing financial report.
Do not choose the number that best matches the target. Compare the source records with the agreed definition. The discrepancy may come from counting offers as starts. Ask the partner to confirm the five records and correct the submission if necessary.
A useful clarification is: “Your update lists 40 job starts, while the narrative says 35 and five rows show future start dates. Our agreed measure counts people who began work during this quarter. Can you confirm the quarter’s count and update those records?” The partner can answer this without recreating the whole report.
Some checks are mechanical: a required period is blank, a rate exceeds its permitted range or a document belongs to another organization. Other findings require interpretation: a result differs from a target, a narrative contradicts a metric or a source does not establish the claim.
| Check | Action | Who decides? |
|---|---|---|
| Missing field needed for interpretation | Request the specific missing context | Submitter supplies it; reviewer checks it |
| Apparent contradiction | Show both sources and ask for clarification | Reviewer resolves it with the partner |
| Changed definition | Record the version and assess comparability | Designated definition owner |
| Unexpected outcome | Read the explanation and relevant evidence | Portfolio team and partner interpret it |
| Unanswered request | Follow the agreed reminder and escalation process | Responsible relationship owner |
AI can help extract candidate values, compare statements and apply a configured review rubric as submissions arrive. Test that workflow on representative files first. Keep uncertain readings visible and require review of consequential flags. A document that has been processed is not automatically a document whose claims have been verified.
Avoid sending separate emails from several reviewers about the same submission. Consolidate questions, identify the source of each question and distinguish required corrections from optional context. Tell the partner what has already been accepted.
Use clear statuses such as received, under review, clarification requested and accepted for this reporting purpose. These are workflow states, not a claim that an organization’s impact has been independently assured. Give each open question an owner and a realistic response date.
Do not silently overwrite earlier submissions. A corrected value should retain the original observation and the reason for the change so subsequent reports can explain a restatement.
Before scaling, ask a partner with an established reporting process and one with limited capacity to try the request. Observe the work rather than asking only whether the form was easy.
Measure reporting effort before and after the change using the same method. Do not claim a time saving without observing it. Review the questions each cycle; a field that was useful during onboarding may no longer need to be requested.
Watch the portfolio reporting demonstration · 2 minutes 16 seconds
A Sopact demonstration of connected portfolio records and reporting. Use the sample reporting package in this lesson to test collection and review against your own requirements.
Use the package from this lesson: one organization, one metric, an explanation and a supporting file. Check that the original evidence stays linked to the reporting period; new material can be reviewed against your definitions; and a later question can use the accumulated record. Confirm permissions, import arrangements and any reminder workflow during setup.
The practical benefit to test is less repeated assembly of the same evidence, with more time to understand the result. It depends on the collection design and review process as well as the software.
Use shared definitions for common measures, with questions appropriate to each organization’s agreement. A common structure does not require identical questions for every partner.
Yes, when it provides the required evidence and context in a usable form. Ask only for the missing details, such as a period, denominator or definition, rather than duplicating the entire report.
No. Set the frequency to match the measure, reporting commitment and practical burden. Some outcomes need longer follow-up, while a specific concern may need an earlier check-in.
No. It can prepare extracted information and review findings. People should resolve uncertainty and approve consequential interpretations or corrections.
Test the request, agree who reviews it and define the follow-up process for missing information. Keep accepted evidence and open questions in the same reporting record.
Next: follow up on missing investee data. Use the question list and ownership rules you have just defined.
Bring one reporting request, its definitions and a sample submission. Work through collection, clarification and review with Sopact.
Explore Impact & ESG Portfolio →
