Affected-record reconciliation

What does the affected-record reconciliation produce?

Compare actual source lists, duplicate keys and missing affected-record populations.

Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.

What do you need before you start?

• Define your exact task, source population and method.
• Keep the unchanged original files and the selected source versions.
• Review missing, invalid and unresolved facts before preparation.

What information do you enter?

Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.

• Reference. Stable reference for this exact supplied population.
• Working pack version. Customer-controlled version.
• Organization. Actual organization owning this work.
• Approved jurisdiction scope. Select and support the actual jurisdiction and instrument for each exact scope.
• Responsible reviewer. Accountable human reviewer.
• Review timestamp. Exact timestamp with seconds and confirmed offset.
• Approved task scope. Included and excluded scopes, populations, assumptions and intended use.
• Scope approval reference. Actual accountable approval reference.
• Approved method version. Actual your method and calendar assumptions.
• Method source reference. Exact original file supporting the selected method.
• Approved method source locator. Exact JSON pointer or reviewed locator.
• Method approver. Responsible human approver.
• Method approval timestamp. Approved instant no later than review.
• Scope population. Selected or declared complete supplied population.
• Declared scope count. Required for a declared complete population.
• Compare actual source lists, duplicate keys and missing affected-record populations scope inputs. Readable named rows, exact relationships, original sources and responsible decisions.
• Source Populations. Readable named rows, exact relationships, original sources and responsible decisions.
• Reconciliations. Readable named rows, exact relationships, original sources and responsible decisions.
• Evidence. Readable named rows, exact relationships, original sources and responsible decisions.
• Actions. Readable named rows, exact relationships, original sources and responsible decisions.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the affected-record reconciliation work?

1. 1
   Define the approved scope

   Reference. Stable reference for this exact supplied population.

2. 2
   Enter task-specific evidence

   Parse actual local JSON/CSV source arrays using explicit key and compare columns. Preserve exact strings and duplicate source rows, flag conflicting duplicates, calculate intersection/left-only/right-only and field contradictions, and verify each declared whole-source count. No person identity or affected legal status is inferred.

3. 3
   Inspect complete findings

   Review all named calculations, original source bindings and unresolved findings.

4. 4
   Keep recoverable work

   Exact original bytes and unfinished strings save locally. Restore validates exact tool, revision, row shape, source hashes and history before replacement. Earlier work and purchases remain separate.

5. 5
   Prepare the finalized pack

   Prepare 7 plus selected attachments complete files, then download them free. Review the fictional sample below.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• NIST Privacy FrameworkSupports named source-bound preparation and precise reviewed criteria. Current applicability and actual outcomes require accountable review. Voluntary Privacy Framework version 1.0, January 2020. Identify-P and Control-P support inventories, data processing purposes, individual preferences, minimization, accountability and actual privacy risk evaluation. The framework does not create statutory obligations or validate a supplied decision or declaration.US National Institute of Standards and Technology. Reviewed 2026-10-09.

Common questions

What still needs review?

This browser preparation compares actual supplied source bytes and your policy, method and jurisdiction assumptions. It does not determine legal applicability, authenticate reported tests, certify anonymity or secure redaction, or execute preference fixtures. Unsupported surfaces, missing populations and pending human decisions stay visible. No replay, scan, DROP access, remote AI or provider call occurs. Originals remain local. Original files are not saved to the cloud.

At most 500 rows/200000 characters per table, 20 files/10 MB each/25 MB total, 900 KB input and 8 MB output metadata. HAR has at most 500 entries. Parsed text and document surfaces are bounded.

No comparison establishes anonymous release, secure redaction, statutory applicability or actual live test results. Your operative source versions and actual evidence remain required.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all privacy and data rights tools.

• Breach chronology builderProduce a consistent timeline from verified events. Try a free example, then review your inputs and the result. No account or payment required.
• Notification assessment packOrganize jurisdiction-specific questions without deciding notification automatically. Try a free example. Review the result.
• Notification deadline calculatorApply rules after the relevant trigger is confirmed. Try a free example, then review your inputs and the result. No account or payment required.
• Breach communication drafterDraft notices from facts and conclusions. Try a free example, then review your inputs and the result. No account or payment required.
• Incident notification trackerRecord recipients, dispatch evidence and follow-up. Try a free example, then review your inputs and the result. No account or payment required.