Proposed design-partner engagement

Know where the next request would get stuck.

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

A source map. A synthetic case. A clear gap list.

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

Five stages from context to a decision.

Each stage leaves a visible record. The final recommendation may be to proceed, narrow the scope, fix readiness gaps first or stop.

  1. 01

    Context interview

    Map the current workflow without collecting request-specific personal data.

    Discuss
  2. 02

    Source mapping

    Document up to three systems, identifiers, owners, access paths and limitations.

    Map
  3. 03

    Boundary design

    Make preparation, exception and professional-decision responsibilities explicit.

    Define
  4. 04

    Synthetic rehearsal

    Run one fictional request through the proposed operating sequence.

    Test
  5. 05

    Readout

    Review the evidence pack, readiness gaps and recommendation together.

    Decide

Detailed proposed scope

What the three outputs would contain.

These deliverables describe the agreed test environment. They do not certify compliance or replace case-specific professional advice.

  1. 01

    Operating-context interview

    A focused walkthrough of the current request workflow, its owners, hand-offs and recurring sources of operational friction.

  2. 02

    Request-intake map

    A record of where requests can arrive, who recognises them and how the next action becomes owned.

  3. 03

    Up to three source-system maps

    A bounded inventory of agreed systems, relevant data domains and proposed evidence paths.

  4. 04

    Identifier and matching logic

    The stable identifiers and assumptions used to connect the same fictional requester across sources.

  5. 05

    Source-owner and access-path register

    Who owns each source and which customer-approved export or retrieval method could be used.

  6. 06

    Retrieval limitations

    Known gaps, unavailable fields, manual dependencies and other limits that must remain visible.

  7. 07

    Decision and exception matrix

    Which questions can be prepared operationally and which require an authorised privacy professional.

  8. 08

    Synthetic request rehearsal

    One end-to-end dry run using fictional identities and records rather than a live request.

  9. 09

    Fictional evidence pack

    An illustrative case summary, source inventory, evidence manifest, exception notes and activity record.

  10. 10

    Readiness-gap report

    A prioritised record of missing ownership, coverage, identifiers, controls or decisions.

  11. 11

    Recommendation for ongoing coverage

    A written view on whether the mapped workflow is suitable for future coverage, further preparation or neither.

Trace Privacy Request Readiness Model

Five dimensions make the workflow inspectable.

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.

01

Intake ownership

Who receives the request, records it and owns the next hand-off.

02

Identity matching

Which identifiers connect the same person across agreed systems.

03

Source coverage

Which sources are in scope, how they are checked and where gaps remain.

04

Decision boundary

Which questions require an authorised privacy professional.

05

Evidence trail

What records the search, exceptions, decisions and closure path.

Synthetic evidence pack

A fictional case makes the gaps concrete.

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

Target price €2,500

The price is under validation. It is not an online offer and there is no checkout.

  • Final scope in writing. Systems, deliverables, timing, roles and terms must be agreed before payment.
  • No live request data required. The rehearsal uses synthetic data.
  • Acceptance is not guaranteed. Trace must confirm fit and delivery capacity.
  • No production access by default. Legal and security requirements must be satisfied first.

After the readout

The next step follows the evidence.

01

Readiness gaps first

The team fixes missing ownership, identifiers, access paths or decision boundaries before discussing coverage.

02

Narrower scope

A smaller system or request boundary may offer a safer, more repeatable starting point.

03

Coverage discussion

If the workflow proves suitable, planned ongoing coverage can be discussed without implying production availability.

04

No further engagement

The source map and gap report remain useful even when Trace is not the right operating partner.

Proposed design-partner engagement

Apply for a Readiness Sprint

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.