Portfolio analytics built for impact, not only returns: the four data layers, cohort and vintage analysis, outcome benchmarking, and the tools compared.
Portfolio analytics for impact is the practice of reading outcomes across every investee or grantee together, so a funder sees the whole portfolio, not one report at a time. The distinction that matters is whether a rolled-up figure cites the records behind it. Sopact treats a portfolio roll-up as a cited query over persistent investee records on the Evidence Thread.
A funder can usually chart totals: dollars deployed, grantees supported, an average score. The hard part is analytics that hold up under scrutiny, where a portfolio-level result can be opened and read back to the investees that produced it. When analytics run over numbers imported from investee spreadsheets, the aggregate looks clean and cannot explain itself.
Key takeaways
Standard portfolio analytics import a value per investee, average or sum it, and draw the result. The individual response and the reason it moved stay in the source spreadsheet, so the aggregate cannot answer why the portfolio looks the way it does. An average that hides a struggling cohort is worse than no average, because it reads as reassurance.
Sopact is evidence-centric: a portfolio analytic is a query that resolves to the investee responses on persistent records, so an aggregate can be opened and read back to the people behind it. See the head practice on portfolio intelligence, and how monitoring reads the same records over time on portfolio monitoring software.
Impact analytics are most useful across time, not in a single frame. Because each investee keeps a persistent ID on the Evidence Thread, an analytic can compare committed to actual, wave over wave, and surface the direction a cohort is moving while there is still time to act. A one-off snapshot cannot do that.
The blended measures that funders ask for, such as a portfolio SROI, are only defensible when each input traces to an investee record. The practice around the underlying claim is set out on impact measurement and the wider IMM discipline on impact measurement and management.
Funders commonly run portfolio analytics through Tableau or Power BI over exported data, an impact platform such as Fluxx or UpMetrics, or an Excel model maintained by hand. Each computes an aggregate well, and each was built around imported numbers, so the qualitative reason a portfolio moved sits in files the analytic never opens. Sopact is built to add the analysis layer, not to replace the system of record.
The one test that sorts portfolio analytics: pick any aggregate figure and ask the tool to show the investee responses that produced it. A dashboard-centric analytic returns the number and stops. Sopact answers from the Evidence Thread, because the aggregate is a cited query over the records.
Roll up by treating the portfolio figure as a cited query over investee records, so any aggregate can be opened and read back to the responses behind it. The table contrasts an imported-total roll-up with an evidence-backed one.
| The question | Imported total | Cited query |
|---|---|---|
| What the aggregate is | A summed export | A query over records |
| Can you open it? | No, detached | Yes, on the Evidence Thread |
| Reads over time? | Snapshot only | Longitudinal by ID |
| Explains variance? | Reason elsewhere | Reason on the record |
See the head practice on portfolio intelligence, or how monitoring uses the same records on portfolio monitoring software.
An annual impact report is a lagging artifact: it summarizes a year that is already over, and its figures are assembled from data nobody read while there was still time to change anything. The value of impact evidence is highest while a program is running, when a weak result can still be improved. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment data arrives, improve while there is still time to act.
The Loop is also what makes an impact claim defensible: every figure in a report traces back to the participant response it came from, the standard detailed in Loop traceability, so a funder or an investor can follow any number to its source rather than taking it on trust.
One method, three moves that never stop
Then the cycle runs again, a little sharper each time. Read the method: the Loop methodology →
The fastest way to see the difference is to run it on your own portfolio. Export an aggregate figure and the investee responses behind it, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Roll up a grant portfolio
Here are our per-investee outcome records on persistent IDs: [ATTACH]. Roll them into a portfolio figure, and for each rolled-up number show which investee records it came from, so the roll-up stays a cited query over the records rather than a detached total.
Academy walkthrough → Calculate blended portfolio SROI
Here are the costs and outcomes per investee: [ATTACH]. Calculate a blended SROI across the portfolio, state every assumption, and show which investee records drive the result, so the ratio traces to evidence rather than resting on estimates.
Academy walkthrough → Compute grantee variance
Here are committed versus actual results per grantee on persistent IDs: [ATTACH]. Show which grantees vary most from plan, quote a response explaining each gap, and tell me which variances are large enough to act on this cycle.
Academy walkthrough → Write a funder narrative that cites its evidence
Here is our portfolio data and the responses behind it on shared IDs: [ATTACH]. Draft a short funder narrative where each claim is followed by the quoted investee evidence, and mark any point where the evidence is thin.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: portfolio analytics where each rolled-up figure resolves to the investee responses behind it.
Portfolio analytics for impact is reading outcomes across every investee together. Sopact treats a portfolio roll-up as a cited query over persistent investee records on the Evidence Thread, so any aggregate can be opened and read back to the responses behind it.
A dashboard aggregates numbers imported from investee spreadsheets, detached from their reasons. Sopact keeps the roll-up on the Evidence Thread as a query over records, so the aggregate figure still points to the investee responses that produced it.
Yes, and it is only defensible when each input traces to an investee record. Sopact keeps every input on the Evidence Thread, so a blended portfolio SROI can be opened and read back to the costs and outcomes behind it.
It should. Because each investee keeps a persistent ID on the Evidence Thread, Sopact reads committed versus actual wave over wave, so an analytic surfaces the direction a cohort is moving rather than a single snapshot.
A portfolio average can mask a struggling cohort and read as reassurance. Sopact keeps the outliers and their explanations attached to the number on the Evidence Thread, so the analytic shows who the aggregate holds for and who it does not.
Pick an aggregate figure and ask the tool to show the investee responses that produced it. A dashboard-centric analytic returns the number and stops; Sopact returns the responses, because the aggregate is a cited query over the records.
No. Sopact adds the analysis layer that keeps each aggregate traceable to a response on the Evidence Thread. It sits alongside a BI stack or grants system rather than replacing the system of record.
Portfolio analytics for impact is the analytics detail; portfolio intelligence is the head practice. Both rest on the Evidence Thread, where a portfolio figure traces to the investee record behind it.
Next: see the head practice on portfolio intelligence, or how the same records are monitored on portfolio monitoring software.
