All use cases

Assess controlled-document migration evidence.

Reconcile source documents, revisions, approvals and references against a proposed migration inventory before accepting the target system.

Book a demo
Illustration of a seal following successive procedure versions and the version used for a batch.

You: We migrated all 120 current documents. Is the migration evidence complete?

neil

The source and target both contain 120 current files, but three prior-revision mappings are missing. Matching current-file counts does not establish that revision history and its relationships were preserved.

File counts match; history is incomplete
File counts match; history is incomplete. 120, 3, Files imported, History gaps. Example records.1203Files importedHistory gaps

You: What should we verify besides the file count?

neil

Identity, content, revision relationships, metadata and relevant access behaviour within the migration scope. I would trace the three exceptions back to their source history and test the mapping, not invent prior links or overwrite the target merely to make the counts agree.

You: Write this up for review, with the sources and the follow-up work we need.

neil

Here is the draft. I have kept the supported finding separate from the open questions, and prepared the evidence requests for the responsible roles.

Controlled-document migration reconciliationReview draft · source evidence and assessment

Controlled-document migration reconciliation

The 120-to-120 current-file count checks one part of the migration only. Three documents still lack mappings to required prior revisions, so current-file parity cannot establish history fidelity. Trace those source revisions to target identities and verify their relationships and access. Record missing mappings separately from content mismatches; neither should disappear behind a successful current-file total.

Source evidence and search scope

SRC-313 (Source inventory); TGT-313 (Target inventory); MAP-313 (History mapping)

SRC-313 / Source inventory

Recorded evidence
120 current documents plus required revision history

TGT-313 / Target inventory

Recorded evidence
120 current files imported

MAP-313 / History mapping

Recorded evidence
Three documents have no mapped prior-revision records
Inputs needed for your own records
  • Source inventory and authorised migration scope
  • Target inventory, mappings and migration logs
  • Acceptance criteria for versions, approvals, files and references

The migration and quality owners verify fidelity and accept the target. A matched file count does not establish that controlled history and relationships were preserved.

Fictional source snapshots. No live query, assignment or approval.

Follow-up work and evidence requests2 proposed tasks · not assigned

Evidence to request

Resolve the three history mappings
Migration owner
Identify the affected source revisions, intended target relationships and reason for each missing map. Preserve both source and target evidence.
Verify content and relationship preservation
Migration verifier
Execute the agreed checks for content, identities, history, metadata and access, retaining observed outcomes and unresolved exceptions.
Example conversation · prepared replies

See this job with your team.

Tell us how your team handles this job today. We’ll walk through the analysis, supporting evidence and review steps in a demo.

Book a demo
What to bring for this job
  • Source inventory and authorised migration scope
  • Target inventory, mappings and migration logs
  • Acceptance criteria for versions, approvals, files and references

Source access, permissions and permitted actions are agreed for your environment.

Source excerpt

SRC-313

Source inventory

Recorded evidence
120 current documents plus required revision history

Selected fictional record, not a live source-system view.

Browse all use cases