Rehearse the catalogue export with the person taking over

A handover document can be accurate about where to click and still omit the setting that preserves the data. The successor needs to complete the ordinary task and inspect the result, not merely confirm that an export file exists.

This fictional rehearsal follows editor Lenka as she exports a small catalogue, opens it for an approved description edit and returns it through the supported import route.

Use a fixture that exposes automatic conversion

The source contains literal item codes 3-4, A-12 and 0008. These are identifiers, not dates or quantities. The export stores them as text values alongside a numerical quantity field.

The old instructions say to open the CSV in Excel, edit the description and save it. In the inspected workstation configuration, opening the file automatically interprets 3-4 as a date. The source export was correct; the value changes during spreadsheet handling.

Lenka notices that the code no longer matches the original before importing it. The rehearsal stops at that boundary. A successful save is not treated as proof that the catalogue can safely accept the file.

Inspect the supported import settings

The selected procedure uses the application's supported text/CSV import workflow and explicitly assigns the item-code column a text type before loading the values. The quantity column retains its numerical type.

The exact controls depend on the installed spreadsheet version and configuration. Microsoft's guidance on automatic date conversion describes ways to preserve intended text. The handover should document the actual supported route used by the team rather than a generic instruction to change a cell's display after conversion.

Formatting an already converted date as text does not reliably recover the original identifier. In this fixture, Lenka discards the changed working copy and starts again from the unchanged source export.

Complete the successor's task

Using the revised procedure, Lenka imports the source with the code column treated as text. She confirms the three exact codes, changes the approved description for A-12 and saves through the agreed exchange route.

The receiving trial catalogue retains 3-4, A-12 and 0008 exactly. Only A-12's description changes. The numerical quantity remains numerical and unchanged, demonstrating that the procedure did not convert every field into an undifferentiated text value.

A repeat export confirms the same identifiers and the intended description. Lenka can explain which setting protects the code column and where to find the source copy if the working file is changed unexpectedly.

Leave instructions that identify the decision

The revised handover includes the source export location, the inspected import profile, the fields requiring text treatment and the reconciliation step before re-import. Screenshots can help identify controls, but the field definitions explain why the settings matter.

The original source copy remains available according to the organisation's agreed retention arrangements. The runbook names who approves a description change and who may perform the receiving import. It does not give every editor unrestricted access to all catalogue operations.

Include the surrounding ownership

The same handover should identify account ownership, billing, recovery, source access and the relevant provider subscriptions. Credentials belong in an appropriate private management process, not embedded in a public checklist or shared example file.

Czech wording needs its appointed reviewer. Technical facts need their product owner. A successful data round-trip does not approve either the language or the underlying specification.

Support arrangements should explain where the successor reports an unexpected result and which information helps investigate it. In this example, the unchanged source, converted working copy and exact code comparison locate the failure without guessing.

The support guide explains those continuing responsibilities. A maintenance assessment can include a practical successor rehearsal when the existing instructions are incomplete.