Free · private · no identifiers unless you opt in

Find the weak link in your DROP cycle.

Eight operational questions. You will get a downloadable gap brief and a prioritized implementation path. This is an engineering diagnostic, not a legal determination.

01 · Access

How do you retrieve and return DROP files today?

No working pathAccess exists, but there is no repeatable retrieval/reporting workflow. Manual portal workflowA person downloads and uploads files through the portal. Tested API workflowAuthenticated download and status upload are repeatable.

02 · Sources

How many systems can contain matching consumer data?

One authoritative sourceA single database or export covers the selected identifiers. Two or three sourcesMatching or actioning spans a small data estate. Four or more sourcesIdentity and deletion must be coordinated across systems.

03 · Suppression

Can a deleted or unmatched request affect newly collected records?

No suppression gateThe current workflow ends after a point-in-time search. List exists, gate is partialIdentifiers are retained but not checked across every relevant intake. Live, tested gateNewly collected records are screened before sale or sharing.

04 · Processors

How do downstream providers receive and evidence actions?

No consistent routeProvider propagation is not part of the current cycle. Email or ticket, manually trackedActions are sent but evidence is assembled by hand. Systematic and evidencedTasks, acknowledgements, and exceptions share one ledger.

05 · Status

Has your response output been accepted end to end?

Not generatedNo exact Id,Status output exists yet. Generated, not automatedOutput exists but naming, validation, or upload is manual. Validated and acceptedThe complete reporting path has passed.

06 · Sandbox

How much of the official sandbox path has passed?

Not startedNo authorized sandbox dry run yet. Hashing checks onlySome standardizers pass, but the full cycle has not. Full cycle passedDownload, match, disposition, and upload were validated.

07 · Ownership

Who owns exceptions and production approval?

No named ownerEngineering, privacy, and legal responsibilities are unclear. Shared informallyPeople are involved, but gates and escalation are undocumented. Named owners and gatesEach exception and production step has an accountable approver.

08 · Repeat

What starts the next 45-day cycle?

Nothing reliableThe next retrieval depends on someone remembering. Calendar or task reminderA human-triggered control starts the cycle. Automated, monitored triggerFailures alert an owner and preserve evidence.

Your operational readiness

Exposed

Building your implementation note…

BoundarySchema metadata only

Recommended modeCustomer-owned pipeline

Immediate priorities

Optional saved-brief email

Want a copy of this brief in your inbox? Enter your email and give separate consent. The handoff contains only this schema-free report.

Delivery may be unavailable while setup is pending. The local download remains available.

Reserve a 48-hour build →

This score is an operational heuristic. It does not determine legal compliance.