The register on the back of a flyer
Your youth worker runs three drop-in sessions a week in different community centres. Attendance is recorded on a paper register, sometimes on the back of a flyer when the forms run out. After each session she is supposed to note who came, what they did and anything significant. She is tired, the centre is closing, and she writes it up at home, when she remembers.
Once a month the admin assistant collects the paper and types it into a spreadsheet. Names are spelled three different ways. Some sessions have no register at all. When the funder asks how many different young people attended over the quarter, and how many came more than five times, the figure takes two days to produce and nobody fully trusts it.
Why frontline data is so patchy
The people with the information are doing the actual work, and the forms were designed for the report, not for them.
- Forms ask for more than frontline staff can record in the moment.
- Paper registers are separated from the session they belong to.
- Nobody sees the value of the data at the point of collection.
- Each project uses its own version of the form, so data cannot be combined.
- Retyping introduces spelling variations and duplicates.
- Signal is buried in notes: a young person's progress might be written but not counted.
The deeper issue is that monitoring was designed backwards from the funder's form, not forwards from the session.
What patchy data costs
Reports to funders are harder to write and less convincing than the work deserves. Numbers that cannot be defended weaken renewal applications. Admin time goes on retyping rather than on something useful.
Frontline staff resent paperwork that eats into their evenings, and good workers leave partly because of it. And the charity loses the ability to see patterns in its own work, such as who stops coming and when.
How we build frontline capture
- We sit with frontline staff and agree the smallest set of things each session type needs to record, working backwards from what funders and trustees actually use.
- A mobile web form, which works on a work phone or tablet and saves offline if the centre Wi-Fi fails, records attendance by tapping names from the project's list.
- New attendees are added with the minimum details your policy allows, and possible duplicates are flagged for a person.
- Outcome prompts are simple choices, with free text optional, so a session record takes a couple of minutes.
- Voice notes can be dictated and transcribed into a draft note that the worker checks, for those who prefer talking to typing.
- Records feed a reporting view that counts unique people, attendance frequency and outcomes by project, period and funder.
- Staff see their own sessions and trends, so the data is useful to them too.
| Question a funder asks | Where the answer comes from |
|---|---|
| How many different people attended? | Unique attendees across session records |
| How many attended regularly? | Attendance count per person over the period |
| What outcomes did people report? | Outcome prompts recorded at sessions |
| Which communities did you reach? | Monitoring fields your policy allows collecting |
What personal information you collect about service users, and how, is for your own policy and data protection lead. We build to that policy.
A normal week for frontline staff afterwards
At the end of a drop-in, the youth worker taps the names of those who came, picks a couple of outcome prompts and saves. It takes a few minutes before she locks up, and nothing needs writing up at home. The admin assistant stops retyping and instead spends time checking the flagged duplicates.
When the funder's quarterly form arrives, the project lead runs the report for the period and the numbers are there, with the sessions behind them.
Signs your impact data needs this
- Frontline staff write up sessions in their own time.
- Paper registers are retyped monthly.
- Reporting figures take days to produce.
- Each project has its own form and spreadsheet.
- You cannot say how many unique people you supported.