Specifications a procurement process can actually use
Everything in the enterprise tier, plus the paperwork a framework submission asks for and discounted credit for public bodies.
Written to survive a procurement process
A specification that cannot go into a framework call-off without being rewritten has not saved anybody any time. The output is structured for the submission, and the paperwork behind it — accessibility statement, DPA, sub-processor list, data residency — is published before anyone asks for it.
- Primary data held in the UK, sub-processors published.
- Article 28 terms available in advance.
- Reduced rates for public bodies and registered charities.
What public bodies get
Procurement-ready output
A specification structured so it can go into a framework call-off without being rewritten.
Accessibility statement
A published conformance statement covering the platform itself.
UK data residency
Primary data held in the UK, with the sub-processor list published.
Published DPA
Article 28 terms available before you ask for them.
Discounted credit
Reduced rates for public bodies and registered charities.
Audit trail
A record of who specified what, and when — which is usually the question afterwards.
Who reviews a government plan
A Blueprint for a public body is routed to the Public sector Track — the discipline a reviewer is accredited in — and only reviewers holding a live accreditation in that Track can claim it. Accreditation is not a sign-up: every applicant, at every level of seniority, sits a 45 to 60 minute blind Calibration on a seeded document from their own field, and what they have already done decides what passing it is worth rather than whether they are asked.
How demanding the work is decides who may take it. Band is derived from the plan itself — regulatory flags, data classification, integration count, scale — and never declared by either side, so a regulated service cannot be reviewed by somebody cleared only for a simple one.
- Reviewers hold accreditation per Category, and public sector work routes only to the Public sector Track.
- Conflicts are declared before a job is claimed, and a whole Category can be suppressed for a reviewer whose day job makes every engagement in it a conflict.
- Everything in your plan is confidential to the reviewer under the published code of conduct, and that does not end when the review does.
- What we do not have yet: no security-clearance register, and no separate cleared or NDA-only reviewer group. If a plan cannot be read by somebody outside your organisation, do not put it in front of an external review.