BLUF format: write a work email with a clear request

Make it easy for the recipient to find what this email asks them to know or do. BLUF stands for Bottom Line Up Front: put the main judgment or request early, then provide the context needed to understand it. Establish what the material supports before choosing the opening.

This exercise produces a subject line, opening request, supporting paragraphs, and response deadline from fictional progress material. A clear opening can be courteous and retain conditions. It does not turn a proposal into an approved decision.

For a long email, or one you have just shortened with AI, check two things: can the recipient find the response needed early, and has the revision changed any conditions, deadlines, or authority? The original-and-revision comparison accepts the complete email and retains the original for an item-by-item review.

BLUF addresses where the information appears

The BLUF writing exercise hosted by the University of Illinois demonstrates intelligence reporting. It uses a paragraph's first sentence to cover the paragraph, with supporting information inside that scope and ordered by importance. Here we apply the idea to a work email. The request and deadline belong to this case; they are not mandatory fields in every BLUF message.

An email for awareness may begin with the status and say whether a response is needed. An action request should identify the action. Keep qualifications close when they affect how the main point should be understood. BLUF does not build your argument or verify your facts.

Write an email someone can respond to

Fictional teaching example: a team is preparing a configuration demo. Eight units in this week's plan were due by the agreed check-in; six are complete and two await interface information. The overall task has 12 units. Today, tomorrow, and Friday are relative times in the exercise. Replace them with actual dates before adapting the email.

Subject: Please confirm the interface contact by 17:00 today; Friday demo impact remains open

Hello,

Could you confirm the interface contact by 17:00 today so we can follow up on information for two configuration units? The exact impact on Friday's demo is still unconfirmed, and any scope change needs approval.

Six of the eight configuration units due at this week's agreed check-in are complete. Two await interface information. The 12-unit overall task is not this week's denominator; the full causes of the deviation are still being checked.

We will check information availability and update the demo impact at 12:00 tomorrow. If information is still missing then, we propose demonstrating the six completed units on Friday and arranging the remainder separately. This conditional alternative is not approved.

Please reply with the confirmed contact, or explain what still needs checking if you cannot confirm yet. Thank you.

The request deadline is 17:00 today. The check and update are at 12:00 tomorrow; these times are not interchangeable. The request has not secured approval of the alternative demo scope.

Open diagram at full size

Give each paragraph a job

Do not add a background paragraph simply to fill a template. Add actual record locations or attachments when needed. This exercise supplies no real attachment, so it invents no link to delivery records.

Compare three openings

Brevity is not the only goal. Removing the condition that information remains missing tomorrow makes the alternative unconditional. Removing the open-cause statement can make waiting for information look like a proven sole explanation.

Follow the communication agreement

Greeting, tone, subject format, and length depend on your team. You do not have to put the acronym BLUF in the message. Sensitive situations may need additional explanation; clarity does not require removing courtesy or necessary context.

If urgent matters require a call or work message, follow that agreement. Sending an email does not replace timely communication. Sending, receiving a response, and obtaining approval are separate events. Follow your actual policies for retaining work records.

Check an email of your own

Read the first two sentences. Can the recipient identify what to know, do, or decide? Check whether each paragraph supports the opening, deadlines are clear, unknowns remain visible, and alternatives retain their approval status. Confirm that the recipient has the relevant authority.

Select passages in the original to retain, labeling each as a request, response deadline, trigger condition, or approval status. Paste or edit the revision, then read just the opening and the full text. A paraphrase can be appropriate. Exact-text presence only establishes that the passage occurs, not that its context and meaning are intact; absence can mean either a paraphrase or an omission. Review each item yourself.

For example, “update at 12:00 tomorrow” does not say who needs to reply with what by 17:00 today. Keeping “six-unit demo” while dropping the trigger condition and unapproved status changes the nature of the arrangement. Record reasons for intentional changes rather than treating every difference as an error.

Subject:

Recipient and authority:
Opening judgment or request (retain key conditions):
Response deadline (date and time):
Supporting information and actual record locations:
Known facts, possible impacts, and open questions:
Next update:
Conditional alternative and approval status:
Response needed:

Work-email comparison; retention items are selected by you, with meaning and actual agreements reviewed by you

Full original:

Subject:
Recipient and authority:
Opening judgment or request (retain key conditions):
Response deadline (date and time):
Supporting information and actual record locations:
Known facts, possible impacts, and open questions:
Next update:
Conditional alternative and approval status:
Response needed:

Full revision:



Retention items and current review:



Review notes:



Exact-text presence does not establish semantic completeness. Editing the revision resets all review statuses. Sending, receiving a response, and approval are separate events.

The practice pack retains the fictional email and blank outline. If several groups of reasons need to support one proposal, try the Minto grouping exercise. If the material needs a short spoken update, use the concise-update example and timed rehearsal. Choose the next guide for the difficulty you actually have.