Lesson 3 of 5 · 6 min

Documents and Reports Without the Blank Page

Go from outline to first draft, then shorten, sharpen and adapt the tone of any work document for a new reader.

In this lesson

  • Ask for an outline before asking for full text
  • Give your own facts so the draft is accurate
  • Shorten a draft and rewrite it for a different reader

The blank page problem

Reports, proposals, procedures, project updates: a large part of office work is writing documents. The hardest moment is often the very beginning. AI is excellent at giving you a structure and a rough first version, so you can spend your energy on what only you can add: the real facts, your judgement and your knowledge of the reader.

Step 1: outline first

Do not ask for the whole document in one go. Ask for an outline, check it, and only then ask for text. This costs one extra minute and saves a lot of rewriting later.

Before: “Write a report about our new customer service process.”

After: “I need a two-page internal report for my manager about a new customer service process we tested for one month. The readers are busy managers. Suggest an outline with five or six headings and one line under each heading explaining what belongs there.”

Now you can move, remove or add sections before any real writing happens. If something important is missing, such as risks or costs, add it to the outline yourself.

Step 2: the first draft

Next, give the assistant your facts for each section: results, numbers, problems, examples. Bullet points are fine. Ask it to write one section at a time in plain language. Short pieces are easier to check, and the assistant is less likely to wander off topic or add filler.

Keep in mind that the AI knows nothing about your company. Without your facts, it produces general text that sounds good but says very little, or it may even insert figures that are not real. Every number in your document should come from you or from a source you trust.

Step 3: shorten and sharpen

First drafts are almost always too long, and AI is a very good editor. Try requests like these:

  • “Cut this to half the length but keep every number.”
  • “Write a three-sentence summary to put at the top.”
  • “Turn this paragraph into five bullet points.”
  • “Which sentences repeat the same idea? Remove them.”

Ask for one change at a time. If you request shorter, friendlier and more detailed all together, the result is usually a compromise that fits none of those goals.

Step 4: change the tone

The same content often needs to reach different readers. A technical note for colleagues may need to become a simple update for a client, or a more formal version for a partner organisation. Paste the text and describe the new reader: “Rewrite this for a client who is not technical. Keep it friendly and professional, and replace internal terms with plain words.” You can also ask for a translation, then have a fluent speaker review anything important before it goes out.

Your name is on it

Read the finished document from start to end as if you were the reader. Check every number, name and date against your sources. Remove phrases that do not sound like you or your company, because readers quickly notice text that feels generic. Some organisations ask staff to mention when AI helped with a document, so follow your company’s guidance. AI makes you faster; it does not make you less responsible for what you publish or send.

Practice

Copy this prompt into a fresh chat with your usual assistant. Fill each [BRACKETS] part with general information only, with no client names or confidential figures.

Prompt
You are an experienced business writer. I need a [DOCUMENT_TYPE] for [READER]. The main message is: [MAIN_MESSAGE]. First suggest an outline with up to 6 headings and one line under each. Then write a 3-sentence summary for the top of the document. Use plain English and do not invent numbers: write XX wherever a figure is needed.
[DOCUMENT_TYPE]
e.g. one-page project update, short proposal, internal report
[READER]
e.g. my manager, the finance team, a new client
[MAIN_MESSAGE]
e.g. the new booking system saves time, and we should use it in all branches
See an example result

Outline:
1. Purpose: why we tested a new booking system and what this update covers.
2. What we tested: which team used it, for how long, and how.
3. Results: time saved per booking and the change in missed appointments.
4. Problems found: issues during the test and how they were solved.
5. Recommendation: roll out the system to all branches, step by step.
6. Next steps: who does what, with a suggested timeline.

Summary:
Over XX weeks, one branch tested a new online booking system. Staff saved about XX minutes per booking and missed appointments fell by XX%. We recommend rolling out the system to all branches, starting with the two busiest ones.

What to notice: Because you asked for XX instead of numbers, the draft cannot contain invented figures, and you can see exactly where your real data must go. If a heading is missing, such as costs or risks, ask the assistant to add it before writing the full text.

Key takeaways

  • Outline first, then draft one section at a time
  • All facts and figures must come from you
  • Edit with one clear request at a time