Unique participants
—Distinct people in selected sessions
Impact Ledger stakeholder report
All records are synthetic. Participation and spending describe activity, not outcomes or causal impact.
THE BIG PICTURE
Good work. Clearer data.
A shared view of who you reach, what you deliver,
and where your resources go.
REPORTING WINDOWYour selected datesAll amounts in USD
Loading your synthetic workspace…
Print report is unavailable while the current view loads.
Compare the immediately preceding equal-duration period using applied filters.
Current period totals
| Measure | Total |
|---|
Attendance
—One person attending one session
Participant hours
—Session hours × people attending
Actual spending
—Against — planned budget
No sessions in this view
Try a different date range or reset your filters. Zero records means zero reported activity.
APPLIED FILTER COMPARISON
Prior period comparison
| Measure | Current | Previous | Delta |
|---|
People are counted distinctly within each window and may appear in both. Delta = current − previous. Activity changes do not establish causal impact; a lower budget variance alone does not establish improvement.
PARTICIPATION OVER TIME
A rhythm of showing up
Repeat visits count each time. People are counted once in the headline.
View attendance data
| Month | Attendance | Participants | Participant hours |
|---|
REACH BY PROGRAM
Different paths. Shared purpose.
Share of attendances in this view.
Total attendance—
View program data
| Program | Attendance | Participants | Budget | Actual |
|---|
Participation tells part of the story. These measures describe activities and reach. They don’t establish outcomes, program effectiveness, or causal impact.
FROM TOTALS TO DETAILS
The session ledger
Every session, including those with no attendance. Spending is counted once per session.
| Date | Program / session | Attendance | Hours / person | Budget | Actual | Variance |
|---|
A CAREFUL HANDOFF
Small files.
Reliable records.
Append synthetic session or attendance records with a validated CSV. Every row must pass before any row is saved.
UTF-8 · up to 1 MiB · 5,000 rows per fileIMPORT SYNTHETIC DATA
Import sessions first, then attendance referencing those session IDs. Use fictional records only. Duplicate IDs are rejected.
Preview is optional and checks the current ledger without adding rows or reserving IDs. Import CSV is a separate action that revalidates the file; the ledger may have changed.
| CSV line | Column | Code | How to fix |
|---|
CSV column guide
Sessionssession_id,program,session_date,duration_hours,budget,actual
Attendanceattendance_id,session_id,participant_id
Dates: YYYY-MM-DD. Hours: 0.01–24 per session. Budget and actual: USD, nonnegative, at most two decimal places. IDs: ASCII letters, digits, dot, underscore or hyphen.
MEASURE WITH INTENTION
A few useful definitions.
- Reach
- Unique participant IDs across selected sessions. Program totals can overlap and should not be added.
- Participant hours
- Each session’s duration multiplied by its attendance count. Assumes each person attends the full session.
- Budget variance
- Actual minus planned session spending. Percentage divides by the selected budget; no percentage is reported when budget is zero.
- What’s outside the ledger
- Eligibility, unmet need, attendance rate, outcomes, and causal impact. This demo has no eligible-population or outcome data.