play icon for videos

Social Impact Assessment: AI-Ready Methodology & Tools

Step-by-step guide to social impact assessment methodology, process, and reporting. Includes examples, frameworks, and tools built for nonprofit programs.

Updated
May 18, 2026
360 feedback training evaluation
Use Case

Use case · how to build a defensible social impact assessment

Boards and funders no longer accept activity counts as impact evidence. The question is what changed for the people the project, program, or policy actually touched — and whether the evidence chain holds up when someone asks. A defensible SIA is a build problem before it is a writing problem. This page walks the build, in four shapes.

01

The eight-stage SIA process — what each stage produces and which data layer it draws from.

02

The seven sections of an SIA report — what goes in each, where the evidence comes from, what reviewers look for.

03

Four worked walkthroughs by shape — project, program, policy, portfolio. Built from raw input through dictionary rule to assembled report fragment.

Definition · 30-second answer

What a social impact assessment actually is.

A social impact assessment is a structured process for evaluating how a project, program, policy, or investment affects people and communities — measuring what changed, for whom, by how much, and why. It runs across eight stages, from initial screening through long-term monitoring, and applies across four working shapes: project-level (a new development), program-level (a cohort intervention), policy-level (legislation or regulation), and portfolio-level (multiple programs or grants).

The output is an SIA report. Reviewers use it to decide whether the intervention is doing what was promised, whether it requires mitigation, and whether the next cycle is worth funding. The report's defensibility rests on the data architecture underneath — not on the document layout.

Most SIAs lead with activity counts, treat outcomes as a paragraph at the end, and present qualitative voice as a handful of pull quotes. A defensible SIA inverts that: pre/post participant outcomes lead the report, qualitative themes explain the quantitative pattern, and every finding traces back to the response that produced it. The eight stages of the process are how that architecture gets built — and the next section walks each one.

Process · the eight SIA stages

The social impact assessment process, stage by stage.

Each stage produces a different kind of evidence. Each stage also draws from a different mix of three data layers — primary stakeholder voice, live administrative measurement, and archived prior assessment. Naming which layer feeds which stage turns the process from a checklist into a build plan.

01 · SCREEN

Screening

Decide whether a full SIA is required, based on intervention scale, stakeholder sensitivity, funder requirement, or regulatory threshold.

Secondary · past

02 · SCOPE

Scoping

Define what the assessment must cover — which outcomes, which life domains, which stakeholder groups, which framework alignment.

Primary · core

03 · BASE

Baseline profiling

Document conditions before the intervention. Quantitative outcome baselines + qualitative community context + indigenous and lived-experience knowledge.

Primary + live + past

04 · PREDICT

Impact prediction

Model how the intervention will alter conditions for different groups. Evaluate magnitude, distribution, and direction of probable change.

Secondary · past + primary scoping

05 · SIGNIFY

Significance evaluation

Apply explicit criteria for what magnitude of change crosses a threshold of concern. Critical for adverse-effect early warning.

Primary · stakeholder priorities

06 · MITIGATE

Mitigation & enhancement

Design specific measures to minimize negative effects and maximize positive ones. Each measure tied to a target and a monitoring protocol.

Primary · co-designed with stakeholders

07 · VALIDATE

Stakeholder validation

Confirm findings, prediction logic, and mitigation plan with affected stakeholders. Where FPIC applies, secure consent on record.

Primary · core

08 · MONITOR

Monitoring & adaptation

Track actual performance against predicted impacts and mitigation commitments. Adjust intervention design when monitoring deviates.

Primary + live, continuous

The four stages most often flagged inadequate by reviewers — scoping, baseline, significance, validation — all draw heavily from the primary stakeholder layer. The next section breaks down what that means inside the report itself.

Format · canonical structure

What goes in a social impact assessment report.

Funder, regulator, and framework templates rename and reorder these sections — IRIS+ asks for indicator-aligned outcomes, the IAIA principles ask for stakeholder-validated mitigation, IFC PS asks for ESS-mapped chapters, CSRD asks for double materiality. The data architecture underneath does not change. Seven sections, each with one specific shape of evidence behind it.

01

Executive summary

2–4 pages · 600–1,200 words

The plain-language synthesis the funder's program officer or the board chair reads first and the community reads in translation. Findings, recommendations, mitigation summary, outstanding-risk statement.

Assembled from §02–07 No new evidence

02

Project, program, or policy description

6–14 pages · 2,000–5,000 words

What's being assessed, where, by whom, on what schedule, against what theory of change. The alternatives analysis — including what happens if the intervention doesn't run — that demonstrates the chosen approach is justified by what alternative paths would produce.

Sponsor-provided Framework-aligned

03

Baseline social conditions

15–40 pages · 6,000–15,000 words

Who the affected stakeholders are, where they live, how they live, what social and economic conditions characterize them before the intervention. Household composition, livelihoods, education, health, cultural ties, community cohesion, equity baselines. The reference point against which every future change gets measured.

Primary · stakeholder & household Secondary · administrative Secondary · census & prior studies

04

Predicted & observed social impacts

15–40 pages · 6,000–14,000 words

For each life domain — livelihoods, health, education, housing, dignity, agency, cohesion — the predicted magnitude and direction of change, disaggregated by demographic and geographic segment, then compared against actual measured change. The section reviewers spend most time on.

Primary · pre/post outcomes Primary · qualitative themes Secondary · administrative deltas

05

Mitigation, enhancement & benefit-sharing plan

8–20 pages · 3,500–8,000 words

For every predicted adverse impact above an acceptable threshold, a specific measure to avoid, minimize, or offset. For every predicted positive impact, a plan to maximize and share benefits equitably. Each measure carries a performance target, an assigned responsibility, and a monitoring protocol.

Primary · stakeholder preference Co-designed

06

Stakeholder engagement & validation summary

6–18 pages · 2,500–6,000 words

Who was engaged, when, how. What concerns surfaced, ranked by frequency and intensity. Where FPIC applies, the consent record and decision conditions. How each significant concern got reflected in the final intervention design and the mitigation plan.

Primary · 100% of this section FPIC-mandatory for indigenous contexts

07

Monitoring plan & technical appendices

30–150 pages · raw evidence

The data behind the findings — survey instruments, response distributions, theme codings with source citations, statistical workings, framework crosswalks. The section funders' independent reviewers and legal counsel turn to when a finding gets contested.

Primary · raw responses Secondary · raw administrative Secondary · prior baseline records

The template argument. Funder templates rename and reorder these sections. IRIS+ frames the same evidence under indicator codes, the IAIA principles frame it under participation standards, IFC PS frames it under ten Performance Standards, CSRD asks for double materiality. The data architecture underneath does not change — and that's the place to push.

Each section above draws from a specific mix of three data layers. The next section names the three layers — and shows what a dashboard built across all of them actually looks like for an SIA.

Data architecture · three layers behind every defensible SIA

The data layers that decide whether an SIA holds up.

A defensible SIA needs three kinds of evidence, collected in three different ways. Social impact assessment is the most primary-data-dependent of the four assessment domains — roughly 80% of the evidence base comes from stakeholders directly, because most of what matters in social outcomes is voice-based and not measurable by sensors.

Layer 01 · Primary · ~80%

Stakeholder & participant evidence

Collected directly from the people the intervention affects. Carries voice, context, and the lived experience that no administrative record captures.

  • Scoping & stakeholder mapping
  • Baseline community profiling
  • Lived-experience & narrative interviews
  • Pre/post participant outcome tracking
  • Equity & disaggregation analysis
  • Stakeholder validation & co-design
  • Ongoing feedback & grievance loops

Owned by Sopact · clean from source

Layer 02 · Secondary · Live

Administrative measurement

Records produced by systems that touch the same population — employment, education, health, housing, justice. Quantitative outcomes for cross-validation, generally narrow on context.

  • Employment & wage records
  • School enrollment & attainment
  • Health system utilization
  • Housing stability & tenure
  • Public assistance receipt
  • Justice system contact
  • Service delivery logs

Integrated via Claude pipes & APIs

Layer 03 · Secondary · Past

Archived & historical record

Documents and datasets produced before this assessment that establish context, baseline, precedent, and historical comparison.

  • Prior SIA & evaluation reports
  • Census & demographic registries
  • Sector benchmark databases
  • Academic baseline studies
  • IRIS+ & SDG indicator archives
  • Government program records
  • Comparable cohort evidence

Read via Claude · summarized into context

Sopact handles the primary layer — collection through one clean instrument, theme coding at submission, persistent participant and household IDs threading every later touchpoint. The administrative and archived layers stay with the systems that already own them — HR, school, health, registry — and integrate with the primary data through Claude or other generative AI tools that pipe context across layers. The result is one assessment, one evidence chain, three sources reconciled at query time rather than at report time.

SIA · Workforce program · Cohort 03 dashboard Live · last updated 9 min ago

Cohort outcomes · current performance

Linked to participant ID · cross-referenced to administrative data · qualitative theme attached to every quantitative shift

Employed at 90 days · IRIS+ PI2387

71%

↗ +18 pts vs baseline

Avg wage gain vs intake

$14.2k

↗ vs $4.8k comparison

Equity gap · BIPOC vs total

4 pts

↑ widened from 1 pt

Confidence shift · post vs intake trace → 142 exit reflections coded "peer support"
Drop-off cluster · weeks 4–6 trace → 29 participants · childcare theme
Credential earned · admin verified trace → awarding body API · 184 records
Wage parity vs prior 2022 cohort trace → archived baseline + IRIS+ benchmark

Use cases · primary-data collection

Seven primary-data collection use cases inside an SIA.

Each one a different reader, a different cadence, a different destination. All seven share one architectural choice — a persistent participant or household ID assigned at first contact and reused at every later touchpoint.

01 · Scoping

Scoping & stakeholder mapping

Source: Stakeholder interviews · power-relations mapping · scope-of-impact workshops
Destination: Scoping report · framework alignment · sampling plan

Most SIA reviews fail because scope missed a group, a domain, or a power dynamic. Catching this at scoping is one week of work. Catching it at endline rewrites the assessment.

02 · Baseline

Baseline community profiling

Source: Household surveys · participatory mapping · cultural & livelihood interviews · focus groups
Destination: Baseline conditions chapter · pre-state of record

Cannot be measured by administrative data alone. The piece that makes outcome comparison defensible — and the piece reviewers most often flag as inadequate.

03 · Lived experience

Narrative interview & ethnographic documentation

Source: Structured narrative interviews · participant journals · case studies · life-history documentation
Destination: Impact chapter qualitative evidence · individual trajectory anchors

Stories that aggregate. Each interview keyed to a participant ID so the same person's quantitative outcome ties to their own words. The piece that turns metrics into evidence.

04 · Pre/Post

Pre/post participant outcome tracking

Source: Intake · mid-program · exit · follow-up surveys — all on the same instrument, all keyed to the participant ID
Destination: Cohort outcome chapter · per-participant trajectory · funder dashboards

The architecture-defining choice for any program-level SIA. A persistent participant ID across waves turns a pile of surveys into a longitudinal study.

05 · Equity

Equity & disaggregation analysis

Source: Demographic fields captured at intake · cross-tabulated with every outcome variable
Destination: Equity chapter · disaggregated outcome tables · adverse-effect alerts

The question funders ask now: who did this work for and who did it not work for. Disaggregation has to be structured at intake — retrofitting it from open-ended fields is fragile and error-prone.

06 · Validation

Stakeholder validation & co-design

Source: Findings-validation workshops · community feedback on draft mitigation plan · co-design sessions
Destination: Validation chapter · binding mitigation commitments

Required by IAIA principles. Reviewers check whether findings were validated with the people they describe. Documentation here is the audit chain that holds.

07 · Feedback

Ongoing feedback & grievance loops

Source: Mobile-accessible feedback form · grievance log · pulse surveys · sentiment surveillance
Destination: Adaptive management triggers · year-over-year comparison

Required by IFC, EBRD, World Bank. Most feedback logs are PDFs nobody reads. Linked to participant IDs means pattern detection across complaints — and live adaptive triggers.

+1 · Automation

Adaptive trigger automation

Source: All seven feeds above, coded by AI at submission
Destination: Sentiment-drift alerts · auto-assembled quarterly brief · funder dashboard updates

When three feedback items of the same theme arrive within seven days from the same demographic segment, the system flags the pattern. Adaptive program adjustment in days, not at the next report cycle.

Shape 01 · Program-level SIA

Building the program social impact assessment.

Workforce training, vocational programs, social services, health interventions, scholarship programs. The unit of analysis is the cohort, the architecture-defining choice is a persistent participant ID, and the funder's question is whether participants ended up materially better off than they started — and whether the program is what made the difference.

Reader of the report

Foundation program officer · board · participant community

Lead primary input

Intake + mid-program + exit + 90-day follow-up · same instrument · same participant ID

Cycle

First cycle 4 months · subsequent cycles continuous

Raw input

What came in

"I came in convinced I'd never code. Week 4 I built my first web app. Week 8 I got my partner to try a coding class too. The mentor matching changed everything — having someone who looked like me show me she'd done it made me believe I could."

Source · Participant #P-118 · exit reflection · 14 March
Plus · Intake confidence score: 2.3/5 · Exit confidence: 4.6/5
Plus · State employment file: hired at $24/hr · 60 days post-program
Plus · Credential body API: certification awarded

Across the cohort

247 participants · 4 waves · 184 administrative matches

Data dictionary

What gets named

Rubric dimensions · technical skill · confidence · job-search readiness · network strength · belonging
Outcome metrics · credential earned · employment · wage · retention · IRIS+ PI2387
Demographic disaggregation · race · gender · prior education · prior employment · zip code
Theme codes · peer support · mentor matching · curriculum · access barriers · employer pathway

One rule that does most of the work

Persistent participant ID assigned at intake · used at every later wave · joins to administrative records · joins to qualitative themes

Report fragment

What ships

Per-participant trajectory · 247 confidence × skill movements traced wave-by-wave · individual stories anchor cohort averages
Cohort distribution · 71% employed at 90 days · $14.2k wage gain vs $4.8k comparison · disaggregated by 5 demographic cuts
Why it worked · top 3 themes ranked by frequency in exit reflections · "peer support" cited by 142 of 218 respondents (65%)
Equity check · BIPOC participants gained 4 percentage points less than cohort average — flagged for next-cycle program design

Section landing

Section 04 · Predicted & observed impacts · Section 03 · Baseline · Section 06 · Validation

Why this build works

The architecture-defining choice is the persistent participant ID. Without it, the intake survey, the exit survey, the follow-up survey, the state employment file, and the credential awarding body's API live in five different worlds. The "report" that comes out is the analyst's best-effort manual reconciliation, six weeks after the cohort closes. The funder reads the report two months later and asks the one question the data can't answer: did this person, this specific person, earn more because of the program — and the analyst has to start a separate study.

With the ID threaded from intake, the question is a query, not a project. Every quantitative outcome ties to the same person's qualitative reflection. The cohort average doesn't displace the individual trajectory — it's built on top of them. Funders read this report and don't have to guess whether the average represents the experience; they can click through to the participant who is the average, and to the participant who is two standard deviations off it.

Decision this build enables: whether to renew the program, where to adjust the curriculum, which demographic gaps need new design before the next cohort starts, and which participant trajectories the foundation will profile in its annual narrative.

Shape 02 · Project-level SIA

Building the project social impact assessment.

A new transit line, a hospital, an industrial facility, an urban development. The intervention is geographically anchored and affects everyone within a defined catchment — homeowners, renters, vendors, schools, churches, informal-economy workers. Unlike a program SIA where participants opt in, here the stakeholder population is whoever lives, works, or moves through the affected geography.

Reader of the report

City planning office · funder or development bank · affected neighborhood coalition

Lead primary input

Catchment-area household survey · 480 households across 6 neighborhoods · 2 waves

Cycle

8–18 months · pre-construction baseline + post-implementation follow-up

Raw input

What came in

"My family has run the corner shop since my grandmother opened it. The new station entrance will be where our loading dock is now. We could relocate — but everyone on this block walks past us on their way home. If the entrance moves, the foot traffic moves with it. The relocation grant doesn't cover the customers."

Source · Household #H-302 · 8 February
Geo · Neighborhood 04 · 38m from station footprint
Demographic · Informal vendor · 3-generation household · tenant
Plus · Census 2020 baseline: median income · racial composition · displacement-vulnerability score

Across the catchment

480 households · 6 neighborhoods · 2,180 open-text statements

Data dictionary

What gets named

Life-domain codes · housing · livelihood · social ties · access · cultural ties · safety · noise · environment
Displacement category · physical · economic · cultural · service-access
Distance bins · 0–50m · 50–150m · 150–400m · 400m+
Demographic disaggregation · tenure · income quartile · race · age · household composition

One rule that does most of the work

Every response code links to one household ID · every household links to a census parcel · every parcel links to the project footprint geometry

Report fragment

What ships

Displacement matrix · households × displacement category × magnitude — visible at parcel level
Top 5 themes by neighborhood · housing displacement, livelihood disruption, cultural ties loss, transit access gain, safety
Equity check · economic-displacement concerns concentrate in the bottom two income quartiles by a 2.4× factor
Mitigation match · each concern category mapped to the mitigation commitment that addresses it

Section landing

Section 03 · Baseline · Section 04 · Impacts · Section 05 · Mitigation plan

Why this build works

Project SIAs break when the analysis flattens to averages. Average displacement concern across the catchment reads "moderate" when one neighborhood is reporting four-alarm distress and four neighborhoods report mild improvement from the transit access. The fix is to keep every household ID intact through coding, then disaggregate by distance bin, demographic segment, and life domain when the report assembles. Equity reviewers and community advocates look at exactly this geographic disaggregation.

The household-level matrix is what makes mitigation commitments stick. A transit agency can defensibly fund a tailored relocation package for the 38 households in the bottom income quartile within 50m of the station entrance because the data shows exactly who they are. A bar chart of theme frequency by neighborhood wouldn't get that package funded.

Decision this build enables: which neighborhoods need targeted mitigation packages, where the station entrance footprint must move to honor heritage and livelihood concerns, and which secondary effects warrant ongoing monitoring after construction concludes.

Shape 03 · Policy-level SIA

Building the policy social impact assessment.

A new affordable-housing policy. A workforce regulation. A schooling rule change. A welfare program revision. The unit of analysis is the population the policy reaches — sampled across jurisdictions where the policy is in force and compared against jurisdictions where it is not. Lived experience and administrative outcomes have to be cross-referenced because the policy's intent and the policy's effect are routinely different things.

Reader of the report

Government department · civic coalition · research partner · legislative body

Lead primary input

Cross-jurisdictional household survey · 1,200 households across 4 markets · public-comment submissions

Cycle

12–24 months · pre-policy + 6 months + 18 months post

Raw input

What came in

"The rent stabilization provision did keep our rent from rising as much as our neighbor's building. But our landlord stopped doing repairs after the law passed, and started moving people out of stabilized units when leases came up. Two of my neighbors got non-renewal notices last month. The law protects the unit, not the tenant."

Source · Tenant focus group 03 · 22 March · Market B
Plus · 3,400 public-comment submissions during legislative review
Plus · Local housing court filings · 2 years pre and post policy
Plus · Census tract-level tenant turnover data

Across jurisdictions

1,200 households · 4 markets (2 policy-on, 2 comparison) · 6,800 open-text segments

Data dictionary

What gets named

Policy-provision schema · rent-stabilization tier · just-cause eviction rule · habitability standard · enforcement mechanism
Affected-population codes · tenant of stabilized unit · tenant of market unit · landlord · housing court actor
Outcome categories · rent burden · displacement risk · habitability · tenure stability · neighbor turnover
Intent-vs-effect tag · each finding tagged as policy-intended, unintended-positive, unintended-adverse

One rule that does most of the work

Every primary record from every jurisdiction is tagged with the policy-provision the household interacts with — so the platform can compare outcomes for households touched by each provision against those not touched

Report fragment

What ships

Policy-vs-population matrix · each provision × each affected population × measured outcome — across 4 jurisdictions
Winners & losers ranking · which subpopulations gained, which lost, which saw no change — with the qualitative why for each
Adverse-effect early warning · 14% rise in non-renewal notices in policy-on markets vs. 3% in comparison — the gap the policy didn't anticipate
Recommended policy amendment · tied to specific public-comment submissions arguing the same fix

Section landing

Section 04 · Predicted & observed impacts · Section 05 · Mitigation · Section 06 · Validation

Why this build works

Policy SIAs frequently report "the policy worked" by comparing aggregate outcomes pre and post implementation. The aggregate hides the most important finding — that the policy worked for one subpopulation and produced a measurable adverse effect for an adjacent subpopulation. The intent-versus-effect tagging is what makes that visible, because every finding gets sorted into did the policy do what it was designed to do versus what did the policy do that nobody predicted.

Public-comment submissions are the under-used corpus in most policy SIAs. Thousands of submissions arrive during legislative review and almost no SIA codes them at scale — they show up as a paragraph saying "stakeholders raised concerns." Coded at submission with a population segment and a concern category, those 3,400 submissions become the dataset that says this exact subpopulation predicted this exact adverse effect — and the post-policy data confirms it. That's an evidence chain regulators take seriously.

Decision this build enables: which policy provisions deliver as intended, which produce adverse second-order effects on adjacent populations, and what specific legislative amendments would close the gaps the data exposes.

Shape 04 · Portfolio-level SIA

Building the portfolio social impact assessment.

A foundation evaluating twelve grants across four regions. A corporate funder rolling up CSR programs in six countries. A government department tracking outcomes across forty grantees. The unit of assessment is no longer one program — it's a portfolio of programs that share a framework but operate in different contexts. Cross-cutting patterns are the analytical centerpiece, and they're the analysis almost no grantee-by-grantee SIA produces.

Reader of the report

Foundation board · program officers · cross-grantee learning network

Lead primary input

Aggregated primary data from 12 grantee programs · 4 regions · shared indicator dictionary

Cycle

24–36 months · multi-grant cycle aligned to portfolio strategy

Raw input

What came in

"Grant A in Region 1 hit its employment target. Grant B in Region 2 hit its employment target. Grant C in Region 3 hit its employment target. Looked at separately, all three are wins. Aggregated, we noticed the wage gain in Region 3 is half of Regions 1 and 2 — and the qualitative theme behind it is the same in every Region 3 exit interview: the local employer pool is concentrated in two low-margin industries."

Source · Cross-grantee portfolio review · February
Plus · 12 grantee programs · 2,800 participants total · all on shared IRIS+ indicator schema
Plus · Census & labor-market data for 4 regions · administrative employment file matches

The structural problem

Each grant's report looked at its own cohort and stopped. The strategic pattern lived in the gap between them.

Data dictionary

What gets named

Geographic aggregation · region · sub-region · zip cluster — every primary record tagged with all three
Outcome harmonization · each grantee's outcome metric mapped to a common IRIS+ indicator · cross-grant comparable
Cross-cutting themes · shared theme codes across all 12 grantees · "employer concentration," "transportation access," "credential portability"
Cohort comparison schema · same metric · same demographic cut · across 12 cohorts · ready for benchmark

One rule that does most of the work

Every primary record from every grantee carries the shared indicator codes — so the platform can roll up across the whole portfolio at any time without recoding

Report fragment

What ships

Portfolio outcome heatmap · 12 grants × 8 IRIS+ outcomes — visible at a glance · color-coded by performance vs. benchmark
Cross-cutting theme analysis · "employer concentration" theme accounts for the wage gap in Region 3 — the same theme appears in three other grantees' qualitative data
Strategic resource shift · Region 3 grantees recommended for industry-diversification technical assistance · budget redirect $480k
Cohort-comparison brief · per-region performance benchmark for next funding cycle · framework-aligned

Section landing

Portfolio strategy document · annual board report · grantee-network learning brief

Why this build works

Grant-level SIAs are the unit of nonprofit reporting production. Strategic patterns are the unit of foundation learning. The fix isn't to ask each grantee for more rigorous individual reports — it's to thread a shared indicator dictionary and a shared theme schema through every primary record at every grantee. Sopact's role is to make that schema enforceable at intake without forcing each grantee onto identical surveys, so grantees keep their context and the foundation gets comparability.

Cross-cutting theme analysis is the under-developed muscle in foundation strategy. Twelve grantees might independently identify "employer concentration" as a barrier — but unless their qualitative data sits in the same coded structure, the foundation will see twelve different framings rather than one strategic signal. Coded against a shared dictionary, the same theme aggregates — and the strategic resource shift becomes defensible at the board level.

Decision this build enables: which grantees get renewed at scale, where the foundation invests in technical assistance versus new grants, which cross-cutting issues warrant a separate funded learning initiative, and how the portfolio strategy gets refreshed for the next cycle.

For the analytical methods behind these builds

Each shape is one cohort, one catchment, or one portfolio. The architecture is shared. See the social impact analysis page for how qualitative themes and quantitative outcomes get joined inside each shape.

Read the analysis methods →

End-to-end · evidence chains that hold up

What a defensible SIA looks like when the chain holds.

Three trace lines a funder, regulator, or community reviewer would follow. Each one starts in primary stakeholder evidence, picks up administrative data along the way, and ends in a defensible finding tied to a specific decision. Each click can be replayed in either direction — from finding back to the participant who produced it, or from participant forward to the finding their data contributed to.

Chain 01 · Community concern → mitigation commitment → monitoring verification

Urban transit project · economic-displacement risk · 3-year trace

01

Primary · scoping

Informal vendor at household #H-302 submits scoping concern: "the new station entrance will move foot traffic away from our shop and the relocation grant doesn't cover the customers."

02

Primary · baseline

Catchment survey codes the same concern across 38 informal vendors in the affected block · disaggregated by income quartile.

03

Mitigation commitment

SIA §5.3 commitment: tailored relocation package for 38 vendors, including customer-pathway preservation, 18-month transition stipend, and reserved storefront in the new station retail corridor.

04

Secondary · live

Quarterly business-license renewal data tracks which 38 vendors remain in operation 12 months and 24 months post-relocation.

05

Primary · follow-up

Annual vendor follow-up survey · same instrument · captures revenue, customer base, and qualitative experience of the relocation package.

Destination

SIA monitoring section shows the original concern, the commitment that addressed it, the administrative data verifying the vendors are still operating, and the follow-up survey confirming livelihood holds. One click traces back to a Tuesday-morning scoping submission from three years before. The chain survives the next funder supervision visit.

Chain 02 · Baseline + outcome tracking → causal explanation

Workforce training cohort · pre/post evidence + qualitative "why" · 18-month trace

01

Primary · intake

Participant #P-118 at intake: confidence rubric 2.3/5 · prior employment record sparse · stated motivation to learn coding.

02

Secondary · past

Comparison cohort baseline from 2022 archive · same demographic profile · same skill area · used as counterfactual reference.

03

Primary · exit

Exit reflection: confidence rubric 4.6/5 · qualitative theme "peer support" coded by AI at submission · linked to participant ID.

04

Secondary · live

State unemployment file: hired at $24/hr · 60 days post-program · credential body API confirms certification awarded.

05

Primary · follow-up

90-day follow-up: retained in role · wage stable · qualitative reflection confirms mentor matching as the decisive program element.

Destination

Cohort outcome chapter reports 71% employed at 90 days with $14.2k wage gain over $4.8k comparison — backed by 184 administrative-record matches AND the same number of qualitative reflections explaining the gain. The board reads the average and clicks through to the participants who are the average. The funder reads the same report and writes the renewal check at scale.

Chain 03 · Cross-grantee pattern → strategic resource shift

Foundation portfolio · 12 grants across 4 regions · 24-month trace

01

Primary · grantee data

All 12 grantees collect outcomes against shared IRIS+ indicator dictionary · 2,800 participants total · same demographic disaggregation schema.

02

Secondary · past

Census & labor-market data for each of the 4 regions · used as contextual baseline · employer-concentration index calculated.

03

Primary · cross-cutting

Theme "employer concentration" surfaces in exit reflections across 4 grantees · same theme code · 312 of 614 Region 3 participants cite it.

04

Strategic shift

Portfolio strategy revision: Region 3 grantees recommended for industry-diversification technical assistance · $480k budget redirect · board-approved.

Destination

Foundation board strategy session opens to one slide: 12 grants × 8 IRIS+ outcomes heatmap, with Region 3 wage outcomes flagged red. The board chair asks why. The dashboard answers: 312 Region 3 participants in their own words. The strategic shift becomes defensible at the next funder convening, the next grantee learning network, and the next IRS Form 990 narrative.

Carry-forward · sibling reading

Where each shape lives in the rest of the cluster.

For the analytical methods that join qualitative and quantitative inside each shape, the social impact analysis page covers theme coding and mixed-method joining at depth. For the audience-facing report that comes out of a finished assessment, the social impact report page covers the eight-section template and four shape-specific examples. For the broader four-domain overview that contextualizes social impact assessment alongside environmental, organizational, and sustainability assessment, the impact assessment page is the entry point. The terminology guide and additional reading sit below this section in the existing page structure.

FAQ · social impact assessment

Common questions about SIA, the process, the report, and the build.

What is a social impact assessment?

A social impact assessment is a structured process for evaluating how a project, program, policy, or investment affects people and communities — who is affected, how, by how much, and what measures will enhance positive effects or mitigate harm. It runs across eight stages, from initial screening through long-term monitoring, and applies across four working shapes: project-level, program-level, policy-level, and portfolio-level.

What is the social impact assessment process?

The SIA process runs across eight stages: screening, scoping, baseline profiling, impact prediction, significance evaluation, mitigation and enhancement design, stakeholder validation, and monitoring with adaptive management. Each stage draws from a different mix of three data layers — primary stakeholder evidence, live administrative measurement, and archived historical records. The primary layer is what most SIAs underuse and what reviewers most often flag as inadequate. The process section above walks each stage with its dominant data layer.

What goes in a social impact assessment report?

A standard SIA report has seven sections: executive summary; project, program, or policy description; baseline social conditions; predicted social impacts by life domain and demographic; mitigation, enhancement, and benefit-sharing plan; stakeholder engagement and validation summary; and monitoring plan with technical appendices. Funder and regulator templates rename and reorder these sections — IRIS+ frames the same evidence under indicator codes, IFC PS frames it under ten Performance Standards, CSRD asks for double materiality. The data architecture underneath does not change.

What is the difference between social impact assessment and impact evaluation?

Assessment documents what changed for the people affected, using structured mixed-method evidence. Evaluation goes further and tests whether the program caused the change, typically through a comparison condition like a control group or quasi-experimental design. Most programs run continuous assessment year-to-year and a formal evaluation periodically when a funder commissions one. Both rest on the same primary-data architecture — persistent participant IDs, baseline-and-follow-up structure, framework-aligned indicators.

What is the difference between social impact assessment and environmental impact assessment?

Social impact assessment measures effects on people, communities, livelihoods, dignity, and cultural continuity. Environmental impact assessment measures effects on ecosystems, air, water, biodiversity, and physical resources. EIA is more often legally required; SIA is more often funder-driven. They share the same eight-stage process structure and the same architectural commitments — persistent IDs, mixed-method evidence, framework alignment, continuous monitoring. Many regulators now require a combined ESIA covering both.

What methods are used in social impact assessment?

Standard SIA methods include scoping consultations, baseline household surveys, participatory mapping, narrative interviews and ethnographic profiling, pre/post participant outcome tracking with persistent IDs, equity disaggregation by demographic group, stakeholder validation workshops, and ongoing feedback mechanisms. Quantitative methods include rubric scoring, statistical comparison against a baseline, and equity-gap analysis. Qualitative methods include theme coding, sentiment analysis, and content analysis applied to open-ended responses at scale. The methodology section of an SIA report names which methods were applied to which evidence.

What tools are used in social impact assessment?

Tools fall into three categories. Survey and forms tools collect responses (SurveyMonkey, Qualtrics, Google Forms). Data analysis tools code qualitative data and run statistical comparisons (NVivo, SPSS, R). Impact intelligence platforms thread all of these together with persistent participant IDs and framework alignment, producing reports that trace every finding back to its source response (Sopact Sense). The third category is what closes the gap between data collection and decision-ready assessment — most teams need it because the first two leave reconciliation as a manual project at every cycle.

How long does a social impact assessment take?

Project-level SIAs run six to eighteen months because community baseline data needs to span seasons and validation workshops take time. Program-level SIAs configure once per cohort and produce continuous outcome reporting; the first cycle takes two to four months to set up, every subsequent cycle takes weeks. Policy SIAs can run six to twenty-four months because cross-jurisdictional sampling and longitudinal follow-up are involved. Portfolio SIAs run on the foundation's strategy cycle, typically 24–36 months. The variable that compresses or extends every timeline is whether data is collected cleanly from day one or reconciled at reporting time.

What is the difference between primary and secondary data in a social impact assessment?

Primary data is collected directly from stakeholders for the assessment — consultation responses, household surveys, FPIC dialogue, lived-experience interviews, pre/post participant outcomes, grievances, narrative reflections. Secondary data is already in existing systems — administrative records like employment, school enrollment, health utilization, plus archived prior assessments and demographic registries. SIA is the most primary-data dependent of the four assessment domains — roughly 80% of the evidence base is primary, because most of what matters in social outcomes is voice-based and not measurable by sensors.

How is AI used in social impact assessment?

AI applied at the collection layer codes open-ended responses by theme as they arrive, summarizes per-participant and per-household profiles automatically, extracts evidence quotes for the report, and flags drift between intended outcomes and observed effects. The same workflows pipe clean primary data into general-purpose tools like Claude for secondary system integration, framework alignment checks, and draft report assembly. The result is an SIA that traces every finding back to its source data and updates as new responses arrive, rather than freezing at a single point-in-time snapshot. Reporting cycles compress from weeks per cycle to hours.

How is social impact assessment different from social impact reporting?

Assessment is the work of measuring change — scoping, baseline, methods, evidence collection, analysis. Reporting is the work of translating the assessment into an audience-facing document. The same primary dataset can produce a technical assessment for funders, a community-facing summary for the affected population, and a board report — three different framings of one evidence base. The assessment is what makes the report defensible. The report is what makes the assessment usable.

Who is the audience for a social impact assessment?

Funders use SIAs to decide whether to renew or scale a program. Boards use them to fulfill governance responsibility. Regulators use them when SIA is part of permitting requirements. Affected communities use them to verify the project, program, or policy is delivering what was promised. Research partners use them to inform sector knowledge. A well-built SIA is layered so the same dataset answers each audience without rebuilding from scratch — that layering is what the four shape walkthroughs above demonstrate.