Assurance system
A single assurance layer connecting Raeburn's existing trust, supplier, delivery, research and client-verification controls.
Material claims should map to a source class: client-verified evidence, public authority data, reproducible technical evidence, repository/release evidence, or clearly labelled estimate/model. Unsupported prestige claims are prohibited.
Supplier assurance, public-sector readiness, policies, conflicts, security, privacy, accessibility, continuity and corporate identity are maintained as procurement evidence. Registration is never described as contract award or endorsement.
Work follows controlled scope, documented inputs, review/acceptance criteria, change control, corrective action, lessons learned and continual improvement. This is an internal quality framework and is not presented as ISO 9001 certification.
Engagements define accountable owner, scope, assumptions, evidence, deliverables, dependencies, acceptance criteria, change route, escalation, handover and closure.
Baseline, intervention and outcome are separated. Realised, client-reported, estimated, modelled and projected values must be labelled. Savings include assumptions and avoid double counting.
Where appropriate, benefits are reviewed at baseline, delivery and post-delivery checkpoints such as 30/90/180/365 days rather than assuming deployment equals value.
Raeburn designs for reasonable portability: client-owned deliverables, documented handover, exportable data where technically/contractually available, credential transfer/revocation and no deliberate lock-in.
Scopes identify deliverables, assumptions, exclusions, IP/data treatment, change control, dependencies, exit/handover and material vendor incentives. Commercial terms remain engagement-specific.
Capability is classified as Delivered, Demonstrated, Research/Methodology, Ecosystem relationship, or Not claimed. Technology logos alone are not proof of delivery or partnership.