Format a Request So the Action Is Visible

Make the requested action easy to locate and answer.

The reading problem

Make the requested action easy to locate and answer.

A concrete example

In a message asking a building manager to fix a hallway light, a long description of previous conversations can bury the actual request. The reader needs the location, problem, and requested next step together.

Try this edit

Put the action in a sentence near the opening. Follow with only the context needed to act. End with a practical way to reply, not a second, differently worded request.

Proof on the page

Take the hallway-light message and mark the sentence that actually asks for repair. Move it below a subject line such as “Hallway light outside flat 4.” Then put the observed problem and access detail in two short lines. Leave earlier correspondence in a final sentence or link if it is needed, not between the subject and the action.

Where the method stops

Do not invent a repair deadline or imply an emergency when none has been confirmed. If the issue really affects safety, use the building’s official reporting route. This guide only improves the readability of a request; it cannot determine urgency, responsibility, or whether the recipient has enough authority to act.

One final check

Before sending, verify that the subject line names the correct place. An otherwise clear request can be misrouted when its heading points to another location.

Primary reading

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