Skip to main content

Connected programme operations

Run the programme from first invitation to final review.

Create the programme, receive registrations, communicate essential details, capture attendance, record programme finances and review what happened—while keeping team responsibility visible.

One programme · multiple responsibilities

Programme

Dates, venues, sessions

Registrants

Status and confirmation

Attendance

People and session check-ins

Review

Reports and programme finance

Programme lifecycle

Keep one operational journey in view.

These are connected programme capabilities, not a promise that every stage runs without configuration, staff action or review.

  1. 01

    Create programme

    Establish the programme record and operational settings.

  2. 02

    Add structure

    Record dates, venues and sessions.

  3. 03

    Publish registration

    Offer a configured public registration journey.

  4. 04

    Receive registrations

    Review status, pathway and supplied details.

  5. 05

    Issue confirmation

    Generate programme information and record attempt status.

  6. 06

    Capture attendance

    Use permitted staff or enabled self-check-in routes.

  7. 07

    Record programme finance

    Maintain budget and actual event-level records.

  8. 08

    Review and follow up

    Use reports and programme follow-up status for review.

Registration and confirmation

Move from public interest to structured programme information.

A configured public page can collect the fields needed for that programme. Registration status, pathways, approval or capacity settings depend on the programme configuration.

Public registration

  • Configurable programme fields
  • Guest and member registration pathways
  • Registration status and review
  • Capacity or approval behavior when configured
  • Consent and privacy prompts configured for the journey

Do not use a historical customer form as a product demo. Each active registration page is organisation- and programme-specific.

Confirmation and communication

  • Sent, queued, failed, skipped or unrecorded application states
  • Programme dates, sessions and venue information
  • Calendar-action presentation where generated
  • Retry and review information where supported
  • Team review when communication needs attention

SENT means the application recorded a send attempt; it is not described as provider-confirmed delivery.

Sessions and attendance

Keep people counts and participation measures distinct.

StewardOS supports simple and multi-session programme structures. Unique attendees answer a different question from total session check-ins, because one person can attend several sessions.

Privacy-safe product view · Sample details

Unique attendees

Distinct confirmed registrations present in at least one session, according to the applicable report definition.

Session check-ins

Present registration-and-session pairs. One attendee may contribute more than one check-in.

  • Session-specific attendance states
  • Walk-in handling under the relevant configured flow
  • Staff check-in and enabled self-check-in routes
  • Pending-review, attended, late and absent distinctions

Programme finance

Review the programme’s budget and actual activity at event level.

Programme records can capture budgeted income, budgeted expenditure, actual income, actual expenditure, supporting evidence and budget-versus-actual review.

Budgeted income

Planned programme income categories

Budgeted expenditure

Planned programme expense categories

Actual activity

Recorded programme income and expenditure

Review

Variance, evidence gaps and reporting state

Follow-up and review

Bring recorded activity into a reviewable picture.

Programme follow-up can record ownership, due dates, status and completion for programme-scoped work. Reports help permitted users review registrations, attendance and programme finance.

Programme follow-up does not automatically become People follow-up. Leadership and pastoral decisions remain the responsibility of the ministry team.

Registration review

Attendance review

Finance review

Follow-up status

Customer story · Fresh Fire 2026

17–19 July · Milton Keynes

A real multi-day programme with two venues and at least four supplied sessions.

Real programme evidence

See the lifecycle through one connected customer story.

Fresh Fire shows the journey from public invitation and structured confirmation to programme administration, attendance and event-level review—without publishing unverified totals.

Read the Fresh Fire case study

Give your next programme one connected operational view.

Begin with the programme structure, then keep registration, attendance, programme finance and review connected.