How do I write instructions for submitting a document or request?

Treat the guide as a map of the task, not a substitute for the organization’s official requirements. Before drafting, identify who will use it, what they are trying to submit, and what action they should take next. Those reader-focused questions help you check whether the instructions give people the information they need to act. [S1]

Then verify the actual requirements with the responsible office or its current official instructions. Check the required materials, acceptable formats, submission channel, deadline if applicable, and how or whether a receipt is provided. Do not fill gaps with common practice or assumptions. General revision guidance can help you assess whether your writing is complete; it does not establish an organization’s submission policy. [S1]

A useful guide can still say what readers should verify and where to insert the confirmed answer. Mark unfinished details clearly, for example: “Accepted file types: [confirm with responsible office].” Don’t publish placeholders as if they were settled requirements.

Use a short opening followed by complete, ordered steps. Put each instruction beside the action it applies to; readers should not have to hunt elsewhere for an important condition. Clear, concise wording and useful examples can make task instructions easier to follow. [S2]

A practical outline is:

1. Purpose: Who should use this guide and what kind of document or request it covers.
2. Before you begin: List verified requirements and identify anything the reader must confirm.
3. Prepare: Explain how to complete or assemble the materials, using only confirmed directions.
4. Submit: State the verified route and any confirmed steps for sending or handing over the materials.
5. After submission: Explain only confirmed receipt or follow-up expectations; otherwise direct readers to verify them.

For example, a draft might say: “1. Check the current requirements with [responsible office]. 2. Prepare [confirmed materials]. 3. Submit them using [verified channel]. 4. For questions about receipt or next steps, use [official contact route].” Replace every bracketed item with confirmed information before publication. If a detail remains unknown, keep it visibly marked for the guide’s editor rather than presenting it as an instruction.

Create a requirements verification list before writing the final version. Give each item a status such as confirmed, needs confirmation, or not applicable. Record the responsible authority or official instruction for each confirmed detail in your working notes, so the guide can be checked and updated. Keep those notes separate from reader-facing claims unless the information is useful to readers.

For example:

• Required materials: [confirmed list / needs confirmation]
• Accepted formats: [confirmed formats / needs confirmation]
• Submission channel: [confirmed route / needs confirmation]
• Deadline or timing: [confirmed details / not applicable / needs confirmation]
• Receipt or follow-up: [confirmed process / needs confirmation]

These are verification prompts, not claims that any particular requirement exists. Do not name a file type, portal, email route, deadline, or expected response unless the responsible authority confirms it. General step-by-step writing advice helps with organization; it cannot tell you which formats or channels an organization accepts, or whether it sends confirmation. [S2]

Review it from the reader’s point of view: Can they tell whether the guide applies to their task? Can they identify what to prepare, what to verify, and what to do next? Are the actions in order, with conditions placed next to the relevant step? General revision guidance recommends checking the reader’s purpose, needed information, and next action; step-by-step guidance supports complete, ordered actions and concise wording. [S1] [S2]

Finally, ask someone unfamiliar with the draft to follow it using the official instructions, if that is practical. Treat this as an editorial clarity check, not proof that the policy is correct. Reconfirm changeable details with the responsible authority before publication and whenever the guide is updated. If there is no verified confirmation process, say that readers should check the official guidance rather than promising a receipt or response.