How we work · PreFlight

Quality isn't declared. It's measured.

PreFlight is the quality framework that runs through every Raptors SAP engagement. Four structured instruments, applied phase by phase, scored throughout delivery. Projects don't go live until they clear.

raptors.tech/preflight
PreFlight project quality dashboard — composite score across the four instruments in real time

The principle

Most SAP projects find quality problems at UAT. By then it's too late.

We built PreFlight because we kept seeing the same pattern — programmes that looked healthy in steering committee reports until acceptance testing exposed what blueprint reviews and informal sign-offs had missed. We wanted a delivery model where quality was scored continuously, gated formally, and visible to the client at every stage.

PreFlight is not sold separately. It is built into every Raptors engagement.

How it works

How PreFlight reads a project.

Every Raptors project is scored continuously across discrete delivery instruments. Together they produce the project's PreFlight score — a single number that determines whether the next phase is authorised.

01

Deliverable Review

Every project artefact reviewed against a scored rubric before it progresses to the next stage.

Continuously through every Activate phase

02

Session Effectiveness Review

Every workshop scored anonymously by attendees across four dimensions — clarity, preparation, value, outcomes.

After every workshop

03

Stage Gate Review

Each Activate phase formally assessed against entry and exit criteria before progression is authorised.

At every Activate phase boundary

04

Acceptance Testing Governance

Structured test cycles — tester assignment, step execution, defect routing, clear sign-off.

Through Realise and Deploy phases

The score

A single number. A clear threshold.

The instruments roll up into a project quality score from 0 to 100. The threshold is non-negotiable.

≥ 85

Cleared

Project may proceed to next phase.

70–84

Monitor

Specific findings must be remediated; revalidation required.

50–69

Intervene

Steering committee notified; remediation plan mandated.

< 50

Grounded

Programme paused; root-cause review before resuming.

This is the threshold framework Raptors applies to its own delivery. Every active Raptors project is scored against it, every week.

Visibility

The client has read access from day one.

Every Raptors client receives access to the PreFlight dashboard from project kick-off. Stage gate reports are shared formally at every Activate transition. There is no version of project quality that we know and the client doesn't.

raptors.tech/preflight
PreFlight quality history — score trend across the engagement lifetime
Project quality history — trend over the lifetime of the engagement.
raptors.tech/preflight
PreFlight stage gate review — Activate phase clearance record
Stage gate review — every Activate phase formally cleared before progression is authorised.
raptors.tech/preflight
PreFlight acceptance testing — tester assignment, step execution, defect routing
Acceptance testing — tester assignment, step execution, defect routing, sign-off.
raptors.tech/preflight
PreFlight workshop QR-code evaluation — attendees score sessions anonymously
Workshop evaluation — attendees scan a QR code, score the session anonymously across four dimensions.

Next step

Ask any current Raptors client what their PreFlight score was last week.