Structuring Messages: Bottom Line, Rationale, and Details

Hello! In the previous lesson, you selected facts that make a BLUF credible and actionable without turning the message into a record of everything that happened. Now you’ll give those facts a useful order. The goal is a message whose bottom line comes first, rationale follows, and details appear where they help the audience evaluate or act on the point. Allow about 35–40 minutes to read, watch, and work through the examples.

Let the reader know what each part is doing

Suppose you need someone to approve a change. You could describe the events that led to your proposal and reveal the request at the end. But until the reader reaches that request, they must guess which facts matter. A more useful order gives them the conclusion first, then the reason for it, then the particulars they may need to check or use.

Read the “Pyramid Principle Structure” section of The Pyramid Principle Applied from Management Consulted. Its terms—assertion, arguments, data—correspond closely to the three parts we will use: bottom line, rationale, detail.

Here is a practical way to distinguish the layers:

1. Bottom line — what should the audience know or do? State the conclusion, status, or request before explaining how you arrived at it.
2. Rationale — why is that the right conclusion or action? Give the principal reason or reasons. This is the bridge between your point and the supporting facts.
3. Detail — what does the audience need to verify, qualify, or carry it out? Supply the relevant evidence, conditions, logistics, or background beneath the reason they support.

“Rationale” and “detail” are not just two labels for everything after the opening. A rationale explains why a fact matters. A detail makes that explanation more concrete. For example, “Monday’s training would teach a soon-to-be-outdated workflow” is a reason to change a session. “The updated workflow goes live Tuesday” is the scheduling fact that supports it.

The layers need not have equal length. A routine message might use one sentence for each. A consequential recommendation may need several distinct reasons, each with its own evidence. In either case, a reader who stops after the first sentence should still know the main point; a reader who continues should find a clear path to assessing it.

Turn a timeline into a message

Watch the comparison in The 1 Tip to Improve Your Communication Skills at Work by Jeff Su. The first workplace reply follows the complications as they happened; the second starts with the result that the recipient needs.

The lesson is not to conceal complications. The revised reply still includes developments that could affect cost or scheduling. It simply tells the recipient the overall status before asking them to interpret those developments.

Consider a different, hypothetical set of notes about a workplace training session:

The current session is booked for Monday. A workflow update goes live Tuesday. The trainer could revise the screenshots Tuesday afternoon. A room is available Wednesday at 10 a.m. but is being held only until 3 p.m. Friday. Attendees will need a revised invitation if the session moves.

A chronological message might begin with the Monday booking, proceed through the update and room search, and eventually ask whether the session can move. That order reflects the writer’s experience, not the recipient’s task. Here is the same information arranged for a recipient who must decide:

Bottom line: Please confirm moving the workflow training from Monday to Wednesday by 3 p.m. Friday, so attendees learn the updated process.

Rationale: The workflow changes on Tuesday; a Monday session would teach steps attendees will no longer use.

Detail: A room is available Wednesday at 10 a.m. The trainer can revise the screenshots after Tuesday’s update, and I’ll send attendees a revised invitation once you confirm.

The opening names the requested decision and puts its deadline where a hurried reader will see it. The rationale explains why moving the session is worth doing. The detail shows that Wednesday is feasible and what will happen after approval. The room availability would be less meaningful if the reader had not first learned why a different date was proposed.

This is message order, not discovery order. You may have learned about the room before you realized the Monday session was a problem. You do not have to recount that sequence. Arrange the finished message around what the audience needs to understand.

Keep the reason above the logistics

The image below shows a short professional email with a request at the top and supporting information underneath. Notice that its supporting information does more than one job.

The email first asks whether the recipient is available for a call. The next paragraph explains the goal of that call: improving the work so it needs fewer tone or style edits. Later lines identify who can join and offer possible times. The image labels all of that material “supporting information”; we can make a further distinction within it. The goal supplies the rationale for the call, while the participants and time windows supply details that help arrange it.

That distinction is useful when editing. If the email began with available time slots, the recipient would have to infer why the meeting was needed. If it offered the goal but no scheduling information, the request might be clear yet harder to complete. Placing the reason before the logistics lets each part answer the next likely question: Why this call? What would it involve? How can I respond?

For a routine request, the resulting shape is often just a short opening, a short explanation, and the necessary particulars. You do not need to print the labels “Bottom line,” “Rationale,” and “Detail” in the message itself. They are a drafting aid; the recipient should experience a natural progression.

Put next steps where they cannot be missed

A bottom-line-first message may still end with an action or a courteous closing. Read the “Direct Approach” portion of Direct Routine Messages – Intercultural Business Communication. It describes an opening that states the main point, a middle that explains it, and a closing that can specify the response or next step.

There is no conflict between putting the request up front and ending with what happens next. In the training example, the opening makes the decision and deadline unmistakable. The final detail tells the recipient what the writer will do once that decision arrives. A closing could briefly repeat “Please confirm by Friday” if that helps, but it should not be the first place the reader discovers that approval is needed.

Use judgment about what belongs in the opening. If a deadline determines whether action is possible, include it with the bottom line, as in the training request. If the timing is merely a scheduling option, it can sit with the details, as the call windows do in the email image. The test is: What must someone understand even if they read only the opening?

The direct pattern is especially useful for routine, neutral, or welcome messages. It is not a claim that every sensitive message should use exactly the same opening or degree of detail. Later in the course, you’ll address difficult news and conversations where clarity must be paired with particular care.

Takeaway

Arrange the message for the audience’s decision, not in the order events occurred. State the bottom line first; give the reason it makes sense; then provide the evidence, qualifications, and logistics needed to assess or act on it. If an action or deadline is essential, make it visible in the opening rather than saving it as a surprise at the end.

In the next lesson, you’ll use a concise clarity-and-action checklist to evaluate whether a BLUF message actually works for its intended reader.