Build a clear LP or board impact report with reviewed findings, visible limitations, source references and decisions your team can follow through.
By Sopact · Updated September 12, 2026
Produce an LP or board impact report by turning reviewed portfolio evidence into a clear account of progress, limitations and decisions. Start with the reporting period and audience, show results against expectations, disclose missing coverage and explain material changes. Link each important claim to its source. Finish with the action requested, its owner and the next review date. A collection of charts becomes a useful report when readers know what to do with it.
This lesson is for investment, impact and program teams reporting to limited partners (LPs), boards or funding committees. Bring the reviewed dashboard and exception register from the previous lesson. You will produce a short decision brief supported by an evidence appendix. The structure below is a suggested working format, not a prescribed investor disclosure standard.
Include the portfolio’s intended outcomes, what was observed during the period, how that compares with expectations and what needs attention. Add the boundary, data coverage and methods needed to interpret those findings. The reader should not need to open every source file to understand the report, but a reviewer should be able to trace a material claim.
| Part | What to include | Reader’s question |
|---|---|---|
| Purpose and scope | Audience, period, included entities and decision | What does this report cover? |
| Progress | Results, agreed targets and comparable prior periods | What changed? |
| Coverage and limits | Missing records, exclusions, uncertainty and definition changes | How much confidence should I place in it? |
| Interpretation | Evidence-based explanations and unresolved questions | Why might this matter? |
| Action | Decision requested, options, owner and follow-up date | What happens next? |
| Evidence appendix | Definitions, calculations, sources and review history | Can someone check the claim? |
The Operating Principles for Impact Management’s monitoring guidance connects performance against expectations with an appropriate response. That supports a report focused on action as well as disclosure. It does not imply that this suggested format satisfies every fund agreement or reporting obligation.
Keep the underlying evidence consistent, but tailor the decision context. LPs may need progress against the fund’s stated impact objectives, the scope of the analysis and important risks or changes. A board may need to consider a management response, resource allocation or oversight issue. Confirm the actual reporting agreement and agenda instead of assuming all recipients want the same packet.
Write the purpose before drafting: “This report asks [audience] to review or decide [question] using evidence from [period and entities].” If there is no decision request, make the oversight purpose explicit, such as noting a material reporting gap and the plan to address it.
Separate impact performance from financial performance. Both may belong in the packet, but participant outcomes, assessed social value and financial returns are different measures. Do not imply one proves the other.
Select findings because they affect the stated objectives, risk or decision. Include positive results, underperformance and important unknowns. A small negative result can be material if it concerns serious harm; a large activity count may tell little about whether an intended outcome occurred.
Record why each finding was selected. Check whether a headline describes the whole portfolio, only responding investees or a selected case. If a result applies to a subset, put that boundary beside the claim rather than only in a footnote.
Use a reporting-coverage measure that matches the question. “Eight of ten partners submitted” is different from “those partners represent 90% of invested capital” or “60% of participants.” State which denominator you use. A large coverage percentage on one basis can conceal an important gap on another.
Illustrative continuation of the dashboard exercise: Partners A and B report 90 completions among 150 enrolled people. Partner C, with 40 enrolled people, has not submitted its result. Definitions and periods match for the two received reports, and the exercise assumes no overlapping participants.
| Brief component | Draft for the committee |
|---|---|
| Finding | Reporting partners recorded a 60% completion rate: 90 of 150 enrolled people. |
| Coverage | Results cover 2 of 3 partners and 150 of 190 enrolled people, or 78.9%. |
| Limitation | The final portfolio rate is unknown because Partner C’s result is missing. |
| Interpretation | The received reports are usable for their stated scope; they do not establish that the whole portfolio met its target. |
| Proposed action | Ask the portfolio lead to obtain or explain Partner C’s missing result and return with a revised assessment. |
| Follow-up | Record the agreed owner, response date and evidence needed to close the issue. |
A weak headline would say “The portfolio achieved 60% completion.” A better one says “Reporting partners achieved 60%; one partner’s result remains outstanding.” The second is less sweeping and more useful because the committee sees both the evidence and the unresolved question.
Suppose Partner A’s narrative describes transport difficulties. Include this as a reported explanation, then state whether the team has checked it. Do not convert the narrative into a proven cause or recommend changing funding solely because AI summarized it as a risk. Gather the evidence needed for that decision.
Attach enough information to reproduce the important claims without overwhelming the main report. Use a claim register that links the headline to its definition, data cut and review. Maintain access controls when source material includes personal or commercially sensitive information.
| Field | Example entry or instruction |
|---|---|
| Claim ID | Completion result Q3, version 1 |
| Population and period | Partners A and B, agreed quarterly cohort |
| Calculation | 90 completions / 150 enrolled people |
| Source | Submission IDs, relevant fields and supporting documents |
| Exclusions | Partner C result not received |
| Review | Named reviewer, date and outstanding qualifications |
| Change history | Later revisions preserve the earlier released values |
A source link establishes traceability, not independent assurance. Describe a review accurately: internally checked, partner-reported, externally verified within a stated scope, or not yet reviewed. Do not call the whole report “audited” because it links to documents or includes an audited financial statement.
A participant or investee story can explain the practical meaning of a finding. Choose it because it illuminates the topic, not because it supplies a dramatic headline. Confirm permission, quotation accuracy and the context in which the account was collected.
State what the story can and cannot show. One person’s account can describe their experience; it cannot establish how common that experience is across the portfolio. Pair it with the relevant quantitative scope and acknowledge experiences that differ. If you do not have a verified, suitable story, use the evidence you have rather than invent one.
Give the assistant the reviewed record, report purpose and claim limits. Ask for gaps and source references along with prose. Check every material number and interpretation before circulation.
Draft an LP or board impact brief for [audience and purpose] covering [period and portfolio boundary]. Use only the attached reviewed data, claim register and narrative sources. Show progress against the supplied expectations, reporting coverage, material exceptions and proposed follow-up. Label estimates, partner explanations and unresolved questions. Cite a source ID for each material claim. Do not infer causation, invent missing results, hide exclusions, or describe the report as audited. Return a short brief, an evidence appendix and a list of decisions or facts a reviewer must confirm.
Keep sensitive material out of a draft unless the recipient is authorized to see it. Review the rendered report and exported file, not only the source document. A hidden column in a working file may still be available in a downloaded dataset.
Release a dated snapshot for the meeting or reporting period. A live dashboard can support follow-up, but it should not silently replace the evidence on which an earlier decision was made. State the data cutoff, version and responsible reviewer.
After the meeting, record the decision, action owner, due date and closure evidence. Carry unresolved actions into the next reporting cycle. If a correction changes a material finding, explain the change and notify the appropriate recipients through your agreed process.
Watch the portfolio reporting demonstration · 2 minutes 16 seconds
A Sopact demonstration of connected portfolio records and reporting. This demonstration introduces connected portfolio reporting. The demonstration introduces connected portfolio reporting. Watch the portfolio reporting demonstration, then test whether a report claim can be traced to its source. The lesson’s figures are illustrative, not customer results.
Test whether the workflow preserves the path from a partner’s submission to a reviewed finding and then to the report. Use one numerical claim, one narrative explanation and one missing result. Ask how the team can retrieve their sources, revise a value and retain the report version already shared.
The portfolio solution is the place to evaluate collection, analysis and reporting together. Confirm the configured permissions and export behavior. People still decide what to claim, what action to recommend and when the report is ready to share.
Use the length needed for the audience’s decision. Keep the main brief focused and put detailed definitions, calculations and sources in an appendix. There is no universal page count that makes a report useful.
Yes. Show missing coverage and explain how it affects the findings. Do not imply that a reporting subset represents the full portfolio without justification.
Source links help review, but do not establish that an audit’s requirements have been met. Describe the actual preparation and assurance performed, including its scope.
It can illustrate an experience, but cannot establish the prevalence or cause of outcomes across a portfolio. Keep its role and limits explicit.
A current dashboard can be useful between meetings. Preserve a dated released version as well so readers can understand what supported each decision.
Track decisions and agreed actions, resolve open questions and carry material changes into the next review. Reporting should support a continuing management process.
Use How to Write an Impact Report for writing guidance and browse the report examples for presentation ideas. Next, connect the portfolio’s existing systems while preserving sources, ownership and reporting history.
Bring a portfolio report, its source records and the decision it needs to support. Work through the reporting workflow with Sopact.
Explore Impact & ESG Portfolio →