A directory correction is easier to maintain when its purpose is narrow. This guide covers how to preserve an extension stored in a separate phone column, using raw import values and field-level transformation rules to separate an approved change from an unresolved question. It is written for a directory data editor, with a final check of the public-facing result.
Set the boundary of this directory import quality check
To preserve an extension stored in a separate phone column, first distinguish the affected public detail from neighbouring information that serves a different purpose. Inspect the raw file and the target field mapping before submitting a bulk update. Record the question in ordinary language before editing. This keeps the review focused when several profile fields appear to need attention, and lets a second person understand why this change is being proposed.
Build a usable source note
The source note for “Preserve an extension stored in a separate phone column” should identify raw import values and field-level transformation rules, the relevant date or version if known, and the person able to confirm the arrangement. Preserve identifiers as text where necessary and reconcile accepted records with rejected or missing rows after the import. Keep a source claim separate from the wording you plan to publish. When one part remains unconfirmed, write down that gap explicitly instead of allowing the rest of the evidence to imply that everything has been established.
Test the likely misunderstanding
Consider “Preserve an extension stored in a separate phone column” as a hypothetical editing exercise: a shared switchboard can answer a call correctly but still send the caller to a different branch. Recording that the number rang is therefore an incomplete test. This is an illustrative decision test, not a report about a real business. Ask the directory data editor to explain which part of the current display could produce that misunderstanding and which supported detail would prevent it. A cosmetic rewrite alone may leave the underlying confusion intact.
Prepare the public-facing change
For the actual edit to preserve an extension stored in a separate phone column, preserve the smallest useful distinction and avoid changing unrelated approved facts. Check the announced business, extension and destination team with an authorised controlled call. If the platform supports a dedicated field, use it for its intended purpose. Where explanatory text is needed, put the qualification close to the information it limits; visitors should not need to discover it in an unrelated section.
Finish with a reproducible check
Treat “Preserve an extension stored in a separate phone column” as complete only after reviewing what the public record now shows. Compare the saved result with raw import values and field-level transformation rules, including any formatting or truncation introduced by the platform. Record the affected field, the visible outcome and any remaining question for the directory data editor. A submitted update and a visible correction are separate milestones; retain the distinction so that a later editor does not assume a pending change is already live.
Before marking this task complete
- Can a new visitor understand the result of “Preserve an extension stored in a separate phone column”?
- Is the relevant directory import quality detail supported by raw import values and field-level transformation rules?
- Are the directory data editor’s unresolved questions kept separate from the approved change?