Delivery
Programmes and outcomes: registers, surveys and funder reports
Included in every plan.
What it does
How your work is set out
- A tree of departments, programmes, projects, clubs and cohorts, where everything adds up to the level above.
- Start from a shape that fits: regular sessions, departments and projects, courses and cohorts, one-to-one support, or a blank page.
- Each programme counts delivery its own way: time, a count, money or distance.
- People take part by enrolling, by dropping in, or both.
- Venues kept once and used across programmes, a lead for each programme, and the organisation’s own fields.
People on a programme
- A place for each person, from waiting list to enrolled, active, completed, withdrawn or excluded.
- Adding a young person asks for a parent or carer.
- Walk-ins and unnamed head counts are recorded alongside named people.
- Soft limits: a full session warns and never refuses, and people can be flagged after a number of absences or a quiet spell.
Sessions and registers
- Sessions with timetables, venues and facilitators, and repeating sessions created weeks ahead.
- The register on a phone: one tap per person for came, late or absent, a search box, add someone on the spot, a head count and first-timers, and a running total.
- “Tonight” on the Home page, so the register is one tap away, and a list of registers still to close.
- A closed register can be corrected, keeping the original entry.
- Printable sign-in sheets and certificates.
Outcomes
- Indicators declared once and shared across programmes, each answering how much was done, how well, or whether anyone is better off, with targets against them.
- A scorecard grouped by those three questions, results recorded by hand where needed, and case studies as evidence.
- Surveys from a library or written fresh, with scoring and distance travelled between readings.
- Collecting data in one flow: what to ask, when, how and of whom.
- Surveys sent by link at set points, such as joining, a review or leaving, on their due date, with missed ones caught up, and a record of when each link was opened.
Reporting
- Reports and returns arranged the way funders read them: how much, how well, better off, where, and what it cost.
- Compare with last year, and file a return so exactly what was reported is kept.
- Named participants, unnamed visits and erased records reported side by side, never added together.
- Funding and costs for each programme, with cost per participant and the caveats that make it honest.
- Home tiles for sessions delivered, registers to close, participants, attendance, surveys due and data quality, and a list of what is missing.
Bringing history in
- Import programmes, places and attendance, with ready-made starts for GoodCRM, Lamplight and a plain register sheet.
How it works
- Set out your programmes, or start from a shape that fits your work.
- Enrol people, or let them drop in, and set the sessions running.
- Take the register at each session, on a phone or a computer.
- Send surveys at the points you choose and record results against your indicators.
- Open the report for any programme and period, and file it when it goes to the funder.
In your kind of organisation
Examples with made-up people and projects.
Volunteer-led community group
a weekly youth club takes its register on a phone at the door, counting named members and unnamed visitors separately, and Home shows tonight’s session before it starts.
More for this kind of organisationCharity delivering funded services
an employability project tracks “into work” as an indicator, sends a survey when each person joins and when they leave, and shows the change on its scorecard for the funder.
More for this kind of organisationMembership body
course cohorts with bookings and attendance, and a certificate for everyone who completed.
More for this kind of organisationCare or support provider
one-to-one support counted in time delivered, with surveys at the start and at each review showing the distance each person has travelled.
More for this kind of organisation
Control and safety
- Who sees a programme’s people follows branches and teams, like every other record.
- A safeguarding concern can be raised on a person’s place on a programme.
- Withdrawing consent is not erasing delivery: the figures stay correct after a person asks to be forgotten.
- Retention can be set per programme, and a legal hold stops anything being removed.
Works with
- Cases and assessments: casework alongside programme delivery.
- Forms: sign-ups that create places, and surveys sent as forms.
- Automations: enrol people, end places and send survey links.
- Grants: funding linked to the programmes it pays for.
- Calendar and scheduling: sessions on the shared calendar.
- Letters and documents: sign-in sheets and certificates.
- Reports and dashboards: programme tiles on Home.
Good to know
- Registers need a connection; there is no offline register.
- Delivery to a whole household has no screen of its own.
- Helpline calls are kept in the call log, not as programme sessions.
Call it what you call it
Organisations rename this to: Projects, Services, Courses, Groups, Cohorts.
Which plan you need
Included in every plan.
See how Affinux would work for your team
A 30-minute demo, shown with your type of organisation. Or start a free trial and explore with sample data.