Customer Instructions: A Web Page, a PDF, or Both?

A customer needs to know how to prepare for tomorrow’s appointment. Your email points to a PDF. Before you redesign that file, decide whether the instructions should be a web page, a printable document, or both. The answer depends on where the customer will read them and who will keep them accurate.

Choose around the moment of use

Write down one actual situation before choosing a format. Is the reader checking parking directions on a phone outside your building? Printing a preparation sheet to put on the kitchen counter? Saving an equipment checklist for a place without reliable internet? Those are different jobs.

For information people consult online, a normal web page is a useful starting point. GOV.UK recommends HTML wherever possible, including because it can respect users’ browser settings. We are drawing on its publishing practice here; its rules for UK government documents are not a statement of your business’s legal obligations.

HTML is not automatically easy to use. A page with tiny text, vague headings and an intrusive popup can still obstruct the reader. Build a short, clearly titled page with the steps in order and a visible route to ask a question. Use our website accessibility checklist for the broader checks.

What the evidence does—and does not—say

Do not replace a PDF merely because someone says Google cannot read it. Google explicitly supports indexing PDF files. That tells you the format is supported. It does not tell you whether your particular file is indexed, whether customers find it useful, or whether converting it will improve rankings.

Likewise, being able to select the text in a PDF does not settle how it works with assistive technology. W3C describes how tags and reading order affect navigation and understanding. A visually obvious two-column layout can have a confusing reading sequence. Check the exported document, rather than assuming the source file’s appearance carried through correctly.

These sources give you reasons to examine usability, maintenance and document structure. They do not supply a universal percentage of customers who prefer downloads. Ask the people who actually use your instructions what they need to carry away, and observe where they get stuck.

Work through one preparation sheet

Consider an illustrative, non-safety-critical example: a repair shop sends customers a two-page “Before your estimate visit” PDF. It contains the address, parking instructions, items to bring, appointment-change instructions and a decorative cover. This is a planning example, not a report about a client or a tested improvement.

The main task is preparing for a visit. Publish that answer at a stable page such as /prepare-for-your-estimate/. Give the customer the practical information first: where to arrive, what to bring, how to identify their booking, and how to ask about access needs. Keep appointment-specific details in the customer’s confirmation rather than putting personal information on a public page.

Then decide whether the PDF earns its maintenance cost. If the front desk regularly hands out printed instructions, a concise printable edition may help. Remove the cover, use the same wording, and include the web address and a revision date. If nobody has a printing or offline need, maintaining a second edition may add work without helping the task.

For safety instructions, regulated notices or manufacturer documents, involve the person responsible for that material before rewriting or replacing it. A convenient web summary must not silently change an instruction that needs to remain exact.

Give the page and download one owner

The common operational problem is two editions drifting apart. The website says to use the side entrance; last year’s PDF says reception. Assign one named role to the instruction set, including every downloadable version. That person needs a place to receive changes from the staff who know the current procedure.

Keep a small working record: instruction title, public page address, PDF address if any, content owner, last substantive revision, and what would trigger another check. A changed entrance, service process or contact method should trigger a review. An arbitrary new date should not replace that review.

Draft the facts together, then prepare the two outputs. Before releasing them, compare their actual instructions line by line. A printable edition can omit navigation and decoration, but it should not quietly give different preparation steps. If you can generate both from one maintained source, that can reduce duplicate editing; it still needs an output check.

Handle the old PDF as a real entrance

Look for links to the existing file in confirmation emails, service pages, saved templates and printed QR codes. A new page in your menu will not update those routes. Record the old address before you remove anything.

Where the old file has a genuinely equivalent replacement, ask your website operator to plan the appropriate redirect. If a document must remain available as a historical edition, label it clearly and link to the current instructions. Do not overwrite an archive that has a reason to preserve its original wording or date. This is a content decision to make with its owner.

Update messages your team will send from now on, then test an older email’s link as well. Our content refresh guide covers deciding what to retain or replace when an existing resource changes.

Accept the result with a customer task

Open the page from an actual confirmation email on a phone. Find the arrival instructions, enlarge the text, follow the question link and return to the steps. On a keyboard, make sure the links are reachable in a sensible order. Review the complete PDF separately if you are keeping one, including its reading order, link order and printed output.

Ask a colleague who did not write it to explain what they would bring and where they would go. Record any uncertainty in the wording. This is a practical acceptance exercise, not a substitute for a full accessibility assessment. Release the resource when the instructions are accurate, the required formats work, and someone owns the next correction.