Skip to content
Astera Technology

Attribute shared programme delivery to the recorded provider

Keep attendance, provider and referral roles distinct before reporting the charity’s activity count.

Name the activity provider in each participation record

Synthetic joint programme has L1 attending a charity-run session, L2 attending a partner-run session referred by the charity, and L3 booked into a charity session with no attendance yet. The local measure counts verified participation delivered by this charity only. L2 is a verified partner service and a charity referral, not another charity-delivered session.

Synthetic joint-activity reporting requirements
ConstraintRequired recordExample decision rule
Provider identityActivity ID + delivering organisationL2 provider is partner
ParticipationVerified attendance separate from bookingL3 not yet counted
Role attributionReferral and delivery fields separatelyDo not count one referral as delivery
Download editable CSV ↓

Test delivered, referred and booked activity

Filled synthetic acceptance cases
CaseInputExpected decision
L1Charity provider; attendance verifiedCount 1 charity participation
L2Partner provider; charity referralReferral count only for charity
L3Charity booking; no attendancePending participation
Download editable CSV ↓
  1. Read provider for each activity
  2. Read attendance evidence
  3. Keep referral role separate
  4. Count scoped delivered participation

Unknown provider remains unassigned in the delivered count; do not default it to the reporting organisation.

How many charity-delivered participations are supported now?

Show the worked answer

One, L1. L2 is partner-delivered and L3 has no attendance evidence.

Keep provider and referral dimensions in the export so collaborative work can be acknowledged without doubling delivered counts.

Related resources