/For Programme Teams
Multi-vendor programmes without the spreadsheet.
Group multiple Work Requests under a single programme. Invite participating organisations with the role they actually play, prime, contributor, observer. Keep status, documents, and activity in one umbrella record.
If any of these sound familiar, Partnr is for you.
“Who's prime on this, and who's just observing?”
Check the kickoff deck from six months ago.
“What's the status across all five workstreams?”
Five separate updates, manually compiled.
“How do we onboard the new contributor?”
Share folders, send invites, hope it sticks.
“The sponsor wants a programme-level view.”
Give us a day.
Partnr models the programme as a real thing, participants, roles, linked work, shared documents, programme-level activity, so the umbrella view is the workflow, not the report.
/The programme view
The umbrella is the workflow. Not the report.
Five steps from kickoff to steady state.
Create the programme
Name it, give it a goal, set start and end dates. Mark the outcome recipient (usually the client). Mark the sponsor and owner.
Invite participating organisations
Add organisations as participants with the role they play: prime, contributor, observer. Roles affect what they see and what they can do. Roles can change as the programme evolves.
Link Work Requests to the programme
Existing Work Requests can roll up into a programme. New ones can be created inside it. The programme view shows them all, stages, statuses, vendor responses, outstanding questions.
Programme-level documents and notes
Share documents at the programme level for everyone to see, or at the Work Request level for one specific piece. Notes work the same way, scoped to where they belong.
Stakeholder updates without the assembly work
The programme view is the update. Stages, dates, blockers, recent activity, already there.
Built for cross-organisation work.
Run the programme, not the spreadsheet.
Bring one programme. Bring the participants. See the umbrella view.