Proof a Form Explanation Before Sending It

Catch ambiguity in instructions written for another person.

The reading problem

Catch ambiguity in instructions written for another person.

A concrete example

A form note saying “send it after approval” leaves both “it” and “approval” unclear. A reader may not know whether a signature, file, or email should come first.

Try this edit

Circle every pronoun in the instruction. Replace any pronoun that could point to two things with the named item. Then ask someone unfamiliar with the form to describe the sequence back to you.

Proof on the page

Rewrite “send it after approval” as “After the coordinator signs the form, email the signed PDF to the contact address on page two.” Then test the sentence by hiding the rest of the form. Does the reader know which form, who acts first, and what gets sent? Put the sequence in numbered steps only if there are several distinct actions.

Where the method stops

Do not use a local preview as proof that a form’s official instructions are complete or valid. The responsible organization may require a particular file type, signature, or channel. Link to that source where possible, and avoid copying a procedure from memory if the real form has changed.

One final check

Read the instruction with the attachment removed. If it refers to “the document above,” name the file or page so the sequence survives forwarding.

Primary reading

These W3C sources inform the general method; they do not certify this guide or your document.