Intake ownership
Who receives the request, records it and owns the next hand-off.
Proposed design-partner engagement
For one client workflow, the proposed Readiness Sprint would map up to three agreed systems, identify the owners and retrieval paths, and rehearse one fictional request. The intended output is a source map, a synthetic evidence pack and a prioritised list of gaps.
Three intended outputs
The source map would record systems, identifiers, owners and retrieval paths. The synthetic evidence pack would show how fictional records reach authorised review. The prioritised gap list would identify missing ownership, coverage and next steps.
The Sprint is intended to test one bounded workflow. No live connectors, processing authorisation or future capacity are included, and no production request acceptance is promised.
Proposed engagement
Each stage leaves a visible record. The final recommendation may be to proceed, narrow the scope, fix readiness gaps first or stop.
Map the current workflow without collecting request-specific personal data.
Document up to three systems, identifiers, owners, access paths and limitations.
Make preparation, exception and professional-decision responsibilities explicit.
Run one fictional request through the proposed operating sequence.
Review the evidence pack, readiness gaps and recommendation together.
Detailed proposed scope
These deliverables describe the agreed test environment. They do not certify compliance or replace case-specific professional advice.
A focused walkthrough of the current request workflow, its owners, hand-offs and recurring sources of operational friction.
A record of where requests can arrive, who recognises them and how the next action becomes owned.
A bounded inventory of agreed systems, relevant data domains and proposed evidence paths.
The stable identifiers and assumptions used to connect the same fictional requester across sources.
Who owns each source and which customer-approved export or retrieval method could be used.
Known gaps, unavailable fields, manual dependencies and other limits that must remain visible.
Which questions can be prepared operationally and which require an authorised privacy professional.
One end-to-end dry run using fictional identities and records rather than a live request.
An illustrative case summary, source inventory, evidence manifest, exception notes and activity record.
A prioritised record of missing ownership, coverage, identifiers, controls or decisions.
A written view on whether the mapped workflow is suitable for future coverage, further preparation or neither.
Trace Privacy Request Readiness Model
The model gives the Sprint a consistent way to describe readiness. It is an operating framework developed by Trace, not an external standard or certification.
Who receives the request, records it and owns the next hand-off.
Which identifiers connect the same person across agreed systems.
Which sources are in scope, how they are checked and where gaps remain.
Which questions require an authorised privacy professional.
What records the search, exceptions, decisions and closure path.
Synthetic evidence pack
The rehearsal uses invented people, records and system outputs. It demonstrates what was searched, what was found, what remains uncertain and where an authorised professional must decide.
Commercial boundary
The price is under validation. It is not an online offer and there is no checkout.
After the readout
The team fixes missing ownership, identifiers, access paths or decision boundaries before discussing coverage.
A smaller system or request boundary may offer a safer, more repeatable starting point.
If the workflow proves suitable, planned ongoing coverage can be discussed without implying production availability.
The source map and gap report remain useful even when Trace is not the right operating partner.
Proposed design-partner engagement
Share operating categories only. Do not send request contents, names, identity documents, exports or credentials. Trace will confirm fit, capacity and scope before any paid work.