Use one record to capture the approved source, permitted fields, observed mismatch, held action, named owner, safe evidence, stop condition, and recheck. A preparer documents the difference; an authorized owner decides what happens next.
This record does not authorize imports, mappings, merges, overwrites, deletions, retention decisions, permissions, exports, automation, reporting conclusions, or production changes. Authorized data, CRM, catalog, privacy, business, and system owners control those decisions.
It gives the right owner a clear starting point. It does not turn a file or a request into approval.
Use an opaque batch reference, the named system and object, and the written mapping version. Do not paste records, raw files, exports, credentials, recovery material, or confidential attachments into this record.
Name the dated approved source, file or feed version, and fields the owner has allowed. Hold the record when a source, field list, or mapping is absent or conflicts.
Describe the mismatch, duplicate candidate, restricted field, or missing mapping without guessing what the data means or how many records should change.
Hold import execution, mapping, merge, overwrite, deletion, retention outcome, permission change, automation, report conclusion, and production change until the authorized owner decides.
Name the authorized data owner, system owner, business owner, reviewer, and written decision reference. Preparation does not grant approval, access, or system-administration authority.
Keep safe references to the approved source, permitted fields, preview or test evidence, rollback path, stop condition, and a business-set recheck. Do not invent a universal review deadline.
These fictional records do not approve a source, mapping, duplicate outcome, price, retention rule, permission, report, or live-system change. On smaller screens, scroll the table sideways to read every field.
| Fictional import record | Approved source and fields | Exception and hold | Owner route | Evidence and recheck |
|---|---|---|---|---|
| Fictional contact-list import CLI-184 | Fictional owner-approved event-registration source and written contact-import field list. Allowed fields: opaque contact reference, organization, approved source tag, and source date. | The approved source tag has no written destination mapping, and one row resembles an existing record. Mapping, import, duplicate handling, and overwrite stay held. | Fictional data owner reviews the field mapping. Authorized CRM owner decides any permitted change; privacy or sales owner joins when the written route requires it. | Safe source and field-rule references, mapping-preview reference, duplicate-comparison reference, stop on a missing rule, then recheck after written owner decision. |
| Fictional product-catalog import CAT-042 | Fictional catalog source in the approved intake location. Allowed fields: SKU reference, approved product title, and approved category code. | The proposed file includes a restricted price field and a duplicate SKU candidate. The source version is not on the approved list, so the full import stays held. | Fictional catalog and data owner validate the source and permitted fields. Authorized system owner controls any test, import, rollback, or production change. | Safe file-version and source-approval references, allowed-field list, exception note, stop on any restricted field or unclear retention rule, then recheck after owner records an outcome. |
Paste this into the business's approved restricted system. Use safe references, not raw files, exports, credentials, recovery material, personal or customer data, or confidential attachments.
DATA-IMPORT EXCEPTION PREPARATION RECORD RECORD CONTROL Safe import batch or reference: System and object: Mapping or feed version: Prepared by: Named data owner: Named system owner: Business owner / question owner: Reviewer: Review date: Status: [Draft / Under review / Held / Approved in writing / Applied by authorized owner / Rechecked / Superseded] APPROVED SOURCE AND PERMITTED FIELDS Approved source reference and date: File, feed, or source version reference: Written mapping or SOP reference: Permitted fields: Restricted or excluded fields: Source conflict, missing fact, duplicate candidate, or open question: EXCEPTION AND BOUNDARY CHECK Observed exception and safe affected-row reference: Held import action: Does this touch a mapping, merge, overwrite, deletion, retention, permissions, automation, reporting conclusion, or production change? If yes, named authorized owner and escalation reference: Stop condition: OWNER REVIEW, EVIDENCE, AND RECHECK Owner decision reference: Allowed preview or test evidence reference: Authorized person who ran any approved action, if applicable: Rollback or prior-state reference: Approved evidence location: Recheck owner and date: Recheck outcome: Use safe references to approved records and locations. Do not paste raw files, exports, credentials, recovery material, personal or customer data, restricted source material, or confidential attachments here. Completing this record does not approve an import, mapping, merge, overwrite, deletion, retention decision, permission change, export, automation, reporting conclusion, or production change.
The full record stays visible and selectable. Nothing is uploaded or saved.
A preparer can compare approved sources, preserve the mismatch, and route a held correction. The authorized owner decides whether anything changes.
Use the written escalation route when the source, field list, mapping, duplicate outcome, access rule, or downstream effect is unclear.
A preparation record cannot repair unclear permissions or missing decision rights. Start with approved sources, permitted fields, limited access, named owners, and a written escalation route.