/Programmes

Multi-vendor, multi-workstream engagements with structure that fits.

Group Work Requests under a single programme. Invite participating organisations with the role they play. Track stages, documents, and activity across the whole engagement, without the weekly slide deck.

The problem

What this replaces.

Who's prime on this programme?

Whoever talked last in the kickoff.

What's the status across all five workstreams?

Five people, five updates, you assemble.

How do we onboard the new contributor?

Share five folders, send three invites.

Sponsor wants a programme view by Friday.

We'll need most of Thursday.

How it works

Programmes, end to end.

/01

Create the programme

Name, goal, start and end dates. Mark the outcome recipient, the sponsor, and the owner.

/02

Invite participants with roles

Add organisations as prime, contributor, observer (or your custom roles). Roles control visibility and capability.

/03

Link Work Requests

Existing Work Requests roll up. New ones are created inside the programme. Stages, statuses, vendor responses, all in one view.

/04

Programme-level documents and notes

Some documents are programme-wide, some belong to a single Work Request. Scope where it makes sense.

/05

Activity log across the programme

Every change, every reply, every document, visible at the programme level. The stakeholder update writes itself.

/What's included

The full capability list.

  • Programme entity with goal, sponsor, owner, dates
  • Multi-organisation participants with role assignment
  • Configurable roles (prime, contributor, observer, custom)
  • Many-to-one linking with Work Requests
  • Programme-level document library
  • Programme-level notes (rich text)
  • Programme status lifecycle (active, completed, cancelled)
  • Cross-programme activity log
  • Soft-delete with restoration
  • Dashboard widget for active programmes
Related features

Works well with.

The programme view is the workflow.

Bring one programme. Watch the slide deck disappear.