Author: Nadali. Prepared with AI assistance.
A customer receives instructions but cannot quickly find what to bring, where to collect an order or how to report a change of plans. AI-assisted editing can shorten the text. It does not turn bold lines into real headings or verify the reading order of the finished file.
This guide is for small hotels, repair shops and other service businesses that send customers instructions. The goal is a clear document with a verifiable structure that preserves the agreed service conditions. The workflow is an editorial proposal, not accessibility certification or a test of a particular application.
1. Separate facts from presentation
Choose one current instruction document. Keep its original, date and content owner. List the fixed facts: address, hours, required documents, agreed contact methods and exceptions. Leave unclear conditions for the process owner to resolve rather than asking a model to decide.
Define the reader’s task separately: for example, “collect a completed order without another phone call.” That is more useful than “make a modern PDF.” An anonymized template is sufficient for this editing task; real order numbers and customer details are unnecessary.
Agree the deliverable: an editable source document and a checklist for its customer-facing version. Do not authorize automatic distribution of the rewrite merely because it sounds convincing.
2. Ask for an outline, not decoration
W3C WAI recommends meaningful headings and link text. A heading should explain its section, and a link should describe its destination. A larger font alone does not establish semantic structure.
For this workflow, first ask AI for a short outline based on customer questions. Under each heading, have it identify which original points belong there. This is an editorial reconciliation method: an important exception must not disappear during “simplification.”
A working prompt:
“Restructure these approved customer instructions. Return a title, section hierarchy, short paragraphs and an action sequence. Preserve every address, time, condition and exception. Do not add deadlines, guarantees or contact methods. For each section, identify the original points used. Separately flag contradictions and information conveyed only by color or a diagram. Do not publish anything.”
3. Example: collecting an order
This is an entirely fictional training example. An imaginary repair shop releases orders at its reception desk from 10:00 to 18:00. Customers provide their order number. If someone else will collect the order, the change must be agreed with the shop in advance. The original instructions already include a contact.
The initial passage reads: “Collect at the stated time. Everything you need is on the green diagram below. If not yourself, get in touch. Contacts here.”
An editorial draft, clarified using the approved facts:
- “When and where to collect”: “Go to the reception desk between 10:00 and 18:00.”
- “What to provide”: “Give your order number.”
- “If someone else will collect”: “Agree the change with the shop in advance.”
- Link text: “Shop contact details,” pointing to the verified destination.
There is no promise of immediate handover, requirement to show a passport or new contact channel. If the original does not contain those conditions, AI must not add them. If the diagram contains another mandatory step, transfer that step into text after verification rather than replacing it with “see diagram.”
4. Implement the structure in the file
A chat draft supplies content only. Someone must implement its structure in the editor. Microsoft recommends built-in heading styles, a logical hierarchy and proper lists in Word. Important information should not appear only inside an image or be conveyed solely through color.
For our instructions, choose a straightforward sequence of blocks without decorative rearrangements. Check that a customer receives the same conditions when reading only the main text. A diagram can supplement the steps, but must not hide the only mention of required approval.
In the working log, separate “wording approved” from “structure applied.” Do not mark the second item complete based on a model’s assurance. Open the file and check the relevant paragraph properties, heading list and actual link destinations.
5. Check the version the customer will receive
If customers will receive a PDF, check the export separately. W3C technique PDF3 explains how tagged PDF structure contributes to reading order and warns about conversion problems with complex layouts. A page’s appearance does not establish that it will be read aloud in the correct sequence.
For this example, we propose three checks: can the reader find the collection hours, the condition for another collector and the shop’s contact details? Ask a competent reviewer to work through the document using assistive technology they know. Separately check keyboard navigation to links. Record the file, version, application, checking method, barrier found and correction.
Do not limit delivery to PDF when a reader needs another format. WAI recommends formats readers can adapt to their needs for event materials. This is a useful selection principle for service instructions, not a claim that any Word file or HTML is automatically accessible.
When the document is not ready
Do not distribute a new version if an exception has disappeared, a link goes to the wrong destination or the reading-order check reveals scrambled steps. Correct the source version first, repeat the export and repeat the necessary checks. Label checks not performed as “not checked,” rather than “passed.”
WAI cautions against generalizing from a few users and recommends combining user involvement with standards evaluation. Our short check is likewise not a comprehensive audit and does not establish legal compliance.
Takeaway: AI prepares an outline and clearer wording. A person preserves the service conditions, implements the structure and checks the actual customer file. Start with one instruction document rather than rewriting everything at once.
Editor, export and checking capabilities depend on version and format. Nadali has not tested this fictional workflow with customers. Sources checked on 3 November 2026.
