By Sopact · Updated September 12, 2026
Build dashboards and compliance reports from a reviewed reporting record, then apply the rules for each audience separately. Define the measures and reporting period, collect the evidence, reconcile exceptions and show coverage alongside results. A dashboard helps people monitor and decide; a filing must meet its own instructions. Reusing data can reduce repeated entry, but it does not make every output accurate or compliant automatically.
This lesson is for portfolio, program and finance teams turning partner reports into recurring management information. Bring the comparability decisions from the related lesson. You will produce a dashboard specification, an exception register and a release checklist. The method works for investment portfolios, grant programs and multi-location operations; the filing examples below are specific to US nonprofit reporting.
- Define the audience, decision and reporting boundary.
- Set the collection cadence and preserve each submission.
- Review definitions, calculations and unresolved evidence.
- Build a dashboard that separates results from reporting coverage.
- Map approved data to each report’s requirements.
- Review, release and retain a dated version.
What is the difference between a dashboard, an SROI analysis and a compliance report?
A dashboard summarizes selected information for monitoring. An SROI analysis estimates social value within a defined scope and set of assumptions. A compliance report answers requirements set by a regulator or other authority. They may share source records, but they do not share every calculation, boundary or approval rule.
| Output | Question it answers | What must accompany the numbers |
|---|---|---|
| Management dashboard | What changed, where and what needs attention? | Period, definitions, coverage, comparisons and action owners |
| Board or investor report | What decision or oversight discussion is needed? | Interpretation, material exceptions, options and limitations |
| SROI analysis | What social value is assessed relative to investment? | Valuation sources, adjustments, overlap, assumptions and sensitivity |
| Compliance report | Have the applicable reporting requirements been addressed? | Required categories, reconciliations, supporting records and authorized review |
A complete submission is not necessarily a strong outcome. Likewise, a favorable outcome does not establish compliance. Keep these judgements separate so a green status cannot stand for three different things.
Start with the decision before choosing charts
Write one sentence for each audience: “This view helps [role] decide [action] using [period and scope].” A program manager may need late submissions and unresolved questions. A portfolio lead may need comparable outcomes and concentration of risk. Finance may need a reconciliation to the ledger. The board needs a concise explanation of what matters and what action is proposed.
Choose a small set of measures that supports those decisions. For each, record its definition, numerator and denominator, unit, reporting window, source, owner and allowed breakdowns. Add the expected refresh date. Distinguish a financial actual from a commitment or forecast; do not label them all “spend.”
Include access rules in the specification. A board summary usually does not need participant names or sensitive case notes. Test the view as its intended reader, including downloads and shared links, rather than assuming the administrator’s view represents everyone’s access.
How should you collect recurring reports?
Use a reporting schedule agreed with the partner. Reuse the stable core of the request, while allowing partner-specific metrics and attachments. A request can combine structured measures, explanations of change, financial documents and supporting evidence. Version the request when definitions or requirements change instead of silently modifying an old series.
Record the partner ID, period, submission date, source files and version together. An uploaded financial statement remains a source document; extracted amounts should link back to it and retain their review status. Keep a corrected submission without erasing the earlier one.
If reminders, a portal or file imports are part of the setup, test them with a real partner before promising a frictionless process. Confirm that the recipient can open the request, save or submit the necessary material and receive a useful explanation of any missing fields. Automation does not solve unclear questions or unavailable records.
Review exceptions without assuming unflagged data is correct
An exception queue helps prioritize review. Define the checks first: missing required evidence, inconsistent units, duplicate records, dates outside the period, impossible values or a mismatch between the narrative and the metric. Keep a separate check for performance against a target.
| Review issue | Example | Next action |
|---|---|---|
| Missing evidence | Reported cost has no supporting schedule | Request the schedule; keep cost provisional |
| Definition mismatch | One partner reports enrollments; another reports completions | Separate the measures or obtain a justified reconciliation |
| Calculation issue | Reported percentage disagrees with its numerator and denominator | Recompute and ask the owner to confirm the correction |
| Performance exception | Verified result falls below its agreed target | Keep the result visible and discuss the explanation |
| Source conflict | Narrative says delivery stopped; activity table shows a full month | Resolve the period or version difference before release |
Assign an owner, due date and resolution for each issue. Review a sample of unflagged records as well: a rule or AI analysis can miss an error. If a repeated problem appears, investigate the request, the source system and the partner’s circumstances before assuming which one caused it.
Do not quietly remove incomplete partners from the dashboard. Show the reporting gap, label provisional values and explain which totals exclude them. Otherwise the dashboard may appear to improve simply because difficult cases disappeared.
Worked example: show results and coverage together
Illustrative exercise: three partners owe a quarterly completion report using the same definition and period. Partner A reports 60 completions from 100 enrolled people. Partner B reports 30 from 50. Partner C has 40 enrolled people but has not supplied a completion result. Assume no person appears in more than one partner’s enrollment count.
| Dashboard item | Calculation | Label the reader should see |
|---|---|---|
| Received reports | 2 of 3 partners | One partner report outstanding |
| Enrollment represented in received reports | 150 of 190, or 78.9% | Coverage by enrolled people; not completion performance |
| Completion rate for reporting partners | 90 / 150 = 60% | Received reports only; Partner C excluded |
| Confirmed completions against all enrolled people | 90 / 190 = 47.4% | Confirmed so far; the final portfolio result is unknown |
| Action | Partner C clarification request | Named owner and agreed response date |
Do not label 60% as the whole portfolio’s final rate. Do not treat Partner C’s missing result as zero completions. When C submits, create a new version and explain the change. If the submission uses a different period, keep it separate until the comparison is resolved.
Pair the numbers with a short explanation of what happened. If A reports a transport disruption, preserve that explanation and its source, but do not claim it caused the observed completion rate without supporting analysis. A useful dashboard makes both the result and the open question visible.
How do you map the same records to a compliance report?
Build a crosswalk from the applicable reporting instructions to the data you actually hold. For each required item, record the definition, period, source field or document, transformation, reconciliation and reviewer. Mark gaps explicitly. An outcome framework or Theory of Change can organize program evidence, but it is not a substitute for a filing’s rules.
For example, IRS Schedule H concerns hospital organizations meeting its filing conditions. Schedule I concerns grants and other assistance to organizations, governments and individuals in the United States. These are not interchangeable templates for every organization. Use the current instructions for the relevant filing year and have the responsible finance or tax reviewer confirm applicability and treatment.
State requirements also differ. Name the jurisdiction and reporting obligation before designing a mapping; a generic “State Attorney General report” is not enough. This lesson explains the preparation workflow, not an organization-specific filing determination.
Reconcile financial values to their authoritative records. Explain differences between program reporting periods and fiscal years, or between commitments and recognized expenditure. Preserve the transformation instead of copying an unexplained total into a new document.
Where does SROI fit?
SROI belongs in a separate, documented analytical view when it serves a real decision. Outcome observations can inform it, but valuations and adjustments require additional evidence and judgement. Do not turn a dashboard count into a monetary benefit merely by attaching a convenient proxy.
Carry forward the portfolio SROI lesson: align boundaries, document proxies and adjustments, check overlap and show sensitivity. Label an estimated social value separately from financial income or cash returned. A ratio does not certify the accuracy of the underlying report.
A usable prompt for specifying the report
Use this with an authorized dataset and the actual reporting instructions. Review the proposed specification before building the view.
Using the attached metric dictionary, submission register, reviewed values and reporting instructions, propose a dashboard and report specification for [audience, decision, period]. For each measure show its definition, numerator, denominator, source, review status and exclusions. Separate reporting coverage from performance. Identify incompatible periods, unresolved records and duplicate-counting risks. For each filing requirement, cite the instruction and the source field or mark a gap. Do not invent values, assume filing applicability, or classify the output as compliant. Return the specification, open questions and named review roles for a person to confirm.
Watch the portfolio reporting demonstration · 2 minutes 16 seconds
A Sopact demonstration of connected portfolio records and reporting. Watch the portfolio reporting demonstration, then test source traceability and reporting coverage in your own setup. This video is not statutory filing guidance.
What should you test in Sopact?
Test a small workflow from collection to the final view: one partner submits metrics, a narrative and an attachment; the team checks the proposed extraction or analysis; a reviewer resolves an exception; and the approved result appears with its period and source. Ask how corrections affect the dashboard and an already exported report.
The value to evaluate is continuity between the incoming evidence and the answer someone uses. Confirm which reminders, imports, analysis rules, permissions and exports are configured for your implementation. Do not assume every connector or statutory filing is supplied automatically.
Use the portfolio solution to discuss that workflow. The team remains responsible for interpretations, publication and any required professional review.
What must be checked before release?
- The audience, reporting period and included entities are visible.
- Totals reconcile and incompatible measures stay separate.
- Missing reports, provisional values and exclusions remain visible.
- Important narrative claims link to evidence and acknowledge uncertainty.
- Permissions and exported files have been tested for the recipient.
- A reviewer has approved the dated version and recorded unresolved limitations.
Freeze the released version while retaining the current working view. If a material correction arrives, issue a revised version with a change note. A live dashboard that changes silently cannot explain what the board saw at its previous meeting.
Frequently asked questions
Can one dataset support several reports?
Yes, when source records and definitions are retained. Each output still needs its own scope, calculations, access rules and review. Shared data does not mean identical reporting requirements.
Does a green dashboard mean the report is compliant?
No. Green must have a defined meaning, such as a completed review or a target met. Compliance requires checking the applicable requirements; a dashboard color cannot establish it.
Should incomplete submissions be excluded?
Exclude unsupported values from calculations where necessary, but show the missing coverage and explain the exclusion. Do not erase the partner from the reporting register.
How often should a dashboard refresh?
Match refreshes to the source cadence and decision. Show both the reporting period and latest update. More frequent refreshes do not make an old source current.
Can AI prepare the filing?
AI may assist with extraction, mapping and draft explanations in an authorized workflow. People must check the instructions, evidence, calculations and applicability before approving the filing.
How is a board report different from a dashboard?
A dashboard supports monitoring; a board report selects material findings, explains their implications and identifies decisions or oversight questions. It should retain the supporting evidence and limitations.
Continue to the board report
Take your specification and exception register into the portfolio board and investor reporting lesson. For writing guidance, use How to Write an Impact Report. Browse the report examples for presentation ideas; their format does not replace your reporting requirements.