One platform for nine awards programmes

The brief

Care Events UK runs nine care-sector awards programmes across England, Scotland and Wales: the Great British Care Awards and eight specialist sister programmes. Every programme follows the same annual cycle of nominations, regional finals, judging, finalist communications and a gala evening, and until 2026 the whole of it ran on spreadsheets, inboxes and the memory of a small team. The same person chased the same tasks nine times over.

The ask was one purpose-built system that owns the cycle for every brand, so the team works from a single place and the programmes stop competing for attention.

What we built

A multi-tenant operations platform with a programme toggle in the top bar. One system for every programme; switching programme changes the regions, categories, dates, logo and palette.

• Admin dashboard across all nine programmes: a photo and bio tracker for every finalist, mass reminders, an editable checklist for each event, sponsor records and analytics.
• Automation engine: reminder emails drafted with Claude in the team's voice, a judge confirmation sequence, and bio and photo chasers that run on a schedule rather than on someone remembering.
• Finalist portal: finalists upload their bio and photo themselves, with nothing else to learn.
• Public nomination forms, one per programme, embedded in the public websites, with spreadsheet export for the team.
• Interview and judging schedules, including the regional rotas the team sends out to judges and finalists.
• Document vault per programme, and an event photo gallery with print purchases through Stripe.

How it runs

The platform went into production on 1 September 2026 with the East of England programme imported and its finalists invited, and the remaining programmes were activated in turn. It runs on Vercel with Supabase for data, Resend for email, Inngest for scheduled jobs and Claude for drafting. William stays on a monthly retainer for hosting, fixes and the next features, so the client has one person to call rather than a ticket queue.

Outcome

The team now runs nine programmes from one screen. Chasing, scheduling and finalist communications happen inside the platform instead of across personal inboxes, and every programme's records live in one place with a full history. The build replaced a stack of separate awards, forms, email and storage subscriptions with one system the client owns.