---
title: "Documents and reports: from blank page to solid draft"
description: "Beat the blank page Starting a document is often the hardest part. AI can give you a structure, a first draft from your notes, and feedback on what's…"
url: https://optimizeall.com/learn/ai-for-everyday-productivity/documents-and-reports
updated: 2026-10-05
---

AI for Everyday Work: Writing, Research, Meetings & Data · Writing and summarizing with AI · lesson 8 of 17 · 12 min

# Documents and reports: from blank page to solid draft

## Beat the blank page

Starting a document is often the hardest part. AI can give you a structure, a first draft from your notes, and feedback on what's missing. You still supply the facts and the judgment.

## The four-step document workflow

**Step 1: Outline first.**

```text
I need to write a [document type, e.g. project update / proposal / policy] for [audience].
Purpose: [what the reader should know or do after reading].
Suggest an outline with headings and one line on what goes under each. Keep it to one page.
```

Adjust the outline yourself. This is where your judgment matters most.

**Step 2: Draft section by section from your notes.**

```text
Using the outline below and my notes, draft the "[section name]" section in about [150] words.
Use only information in my notes. Where something is missing, write [TBC].
Outline: [paste]
Notes: [paste]
```

The **[TBC]** instruction is important: it stops the AI from filling gaps with invented details.

**Step 3: Improve.**

- "Make this clearer for someone new to the project."
- "Turn this paragraph into three bullet points."
- "Add a one-paragraph executive summary at the top."
- "What questions would my manager ask after reading this?"

**Step 4: Final check.** Read the whole document. Check facts, figures and names. Fill every [TBC]. Make sure the tone fits your organization.

## Useful document types and prompts

**Weekly or monthly updates:**

```text
Turn these notes into a status update with sections: Done this week, Next week, Risks/blockers, Help needed. Keep each bullet to one line.
```

**Proposals:** outline with problem, proposed solution, benefits, costs [TBC], timeline, next steps.

**Standard operating procedures (SOPs):**

```text
Turn this description of how we process new orders into numbered steps. Each step should start with a verb. Add a "common mistakes" section at the end.
```

**Policies:** structure and plain-English drafts, always reviewed by the responsible person (and legal or HR where relevant).

## Worked example

Tom, an operations assistant at a logistics firm in Birmingham, needs a monthly report for his director. He pastes his bullet notes and last month's report as a structure example. The AI drafts the report with [TBC] for two missing figures. Tom gets the figures from the system, fills them in, and asks: "What would the director ask after reading this?" The AI suggests she'll ask why late deliveries rose. Tom adds a short explanation. The director replies: "Clear and useful, thanks."

## Sample output check

A strong draft follows the outline's headings exactly, uses only facts from your notes, and marks gaps clearly. Watch for "filler" sentences such as "This demonstrates our continued commitment to excellence"; delete them. Readers value specific facts over generic statements.

## Getting feedback before your manager does

Before you send a document, ask the AI to review it from the reader's point of view:

```text
Read this report as my director would. What is unclear, what is missing, and what would you question? List the top 5 issues in order of importance. Don't rewrite it.
```

This often catches missing context, unexplained jargon or a buried conclusion. Fix the issues yourself, then do your final check.

## Formatting tips

- Ask for **headings and short paragraphs** for readability.
- Ask for **tables** for comparisons and figures.
- If your document tool has built-in AI (for example, in Google Docs or Microsoft Word), you can draft directly in the document; features depend on your plan and your organization's settings.

## Hands-on: from notes to a report in four prompts

Run these in order in one chat (or inside a project that holds your style guide and a past example).

```text
PROMPT 1 - Outline
I need a [monthly operations report] for [our director, who reads it on her phone].
Purpose: she should know what went well, what went wrong and what decision she needs to make.
Suggest an outline with headings and one line per heading. One page maximum. Don't write it yet.
```

```text
PROMPT 2 - Draft one section
Using the approved outline and my notes, draft the "Deliveries" section in about 120 words.
Use only my notes. Write [TBC] for anything missing. No filler sentences.
Notes: [paste]
```

```text
PROMPT 3 - Reader review
Read the full draft as my director would. List the top 5 things that are unclear,
missing or likely to be questioned, most important first. Don't rewrite it.
```

```text
PROMPT 4 - Tighten
Cut the draft by 25% without losing any number or decision. Put the decision needed in the first paragraph.
```

**Before:** "Write my monthly report" produces 600 words of generic praise ("strong performance across key areas") with invented percentages.

**After:** a one-page report in your director's preferred order, two [TBC] markers you fill from the system, and a first paragraph that says exactly what decision is needed.

## Writing inside your document tool

Word with Microsoft 365 Copilot and Google Docs with Gemini let you draft, rewrite and summarize without leaving the document, and can reference other files you have access to. Canvas-style editors in ChatGPT, Claude's artifacts and document features, and Notion AI in Notion pages let you edit a draft side by side with the assistant. The four-prompt workflow is the same in all of them.

## A final-check list for any AI-assisted document

- Every [TBC] replaced; search the document for "TBC" before sending.
- Every number traced to a source you can name.
- No filler sentences ("demonstrates our continued commitment...").
- Headings match what the reader needs, in the order they need it.
- Any policy, legal or HR wording reviewed by the responsible person.

## Pitfalls

- Asking the AI to write the whole document in one go with no notes; you'll get generic content.
- Leaving [TBC] markers in the final version.
- Letting AI invent figures, quotes or references.
- Using AI for final legal or HR wording without the right review.

## Video lecture: Documents and reports: from blank page to solid draft

Lecture coming soon · 10 chapters · about 8 minutes. Read the full transcript below.

1. Beat the blank page
2. Why whole-document prompts fail
3. The architect analogy
4. Example 1: the monthly report
5. Example 2: the new SOP
6. Watch me do it
7. The reader review, up close
8. Write where you work
9. Common mistakes
10. Recap and try this now

## Lecture transcript

### Beat the blank page

What's the hardest part of writing a report? For most people it isn't the writing. It's starting. The blank page, the cursor blinking, and a vague sense that you should have started yesterday. AI is brilliant at getting you past that. But used badly, it gives you six hundred words of confident, generic filler with numbers nobody can trace. In this lecture you'll learn a four prompt workflow that turns your notes into a solid document you'd happily put your name on. You'll see two examples, watch me run the workflow on a monthly report, and leave with a final check list.

### Why whole-document prompts fail

So why does write my monthly report go wrong? Because the AI has no facts, but it still has to produce a report. So it fills the space with what reports usually sound like. Strong performance across key areas. Continued commitment to excellence. And, worst of all, it may invent numbers that look precise, like a twelve percent improvement, that come from nowhere. None of that is malicious. It's the AI doing its best with an empty brief. The fix is to split the job into steps, feed in your real notes, and give the AI a clear instruction for what to do when something is missing.

### The architect analogy

Think of it like building a house. You wouldn't let a builder start pouring concrete before you'd approved the plan. So step one is the outline. You approve the plan. Step two, the AI builds one room at a time: one section, from your notes, with a clear rule. Use only my notes, and write TBC for anything missing. That TBC marker is the most important trick in this lesson, because it turns a hidden guess into a visible gap. Step three, an inspection: ask the AI to read the draft as your reader would and list what they'd question. Step four, tighten it. Cut the waffle, keep every number and decision.

### Example 1: the monthly report

Here's a simple example. Tom is an operations assistant at a logistics firm in Birmingham. He pastes his bullet notes and last month's report as a model for the structure. The AI drafts this month's report and marks two missing figures as TBC. Tom pulls the real numbers from the system and fills them in. Then he asks: what would the director ask after reading this? The AI says she'll probably ask why late deliveries went up. Tom adds a two line explanation. The director replies: clear and useful, thanks. Total time, about half what it used to take, and nothing in it he can't defend.

### Example 2: the new SOP

Now a business scenario with illustrative details. A dental clinic group in Toronto is opening a third location and needs a standard operating procedure for new patient intake. The practice manager, Leila, has never written one. She records herself describing the process, just talking, then pastes the transcript and asks: turn this into numbered steps, each starting with a verb, and add a common mistakes section at the end. Use only what I described, and write TBC where I skipped something. The draft has fourteen steps and three TBCs, including one she genuinely hadn't thought about: who checks insurance details. She fills the gaps, the lead receptionist reviews it, and the new clinic opens with a clear process from day one.

### Watch me do it

Let me run the whole workflow. Prompt one: I need a monthly operations report for our director, who reads it on her phone. She should know what went well, what went wrong, and what decision she needs to make. Suggest an outline. Don't write it yet. It gives me five headings. I move the decision needed to the top, because that's what she cares about. Prompt two: draft the deliveries section in about one hundred and twenty words, from my notes only, TBC for gaps, no filler. Good. I repeat for each section. Prompt three: read it as my director would and list the top five issues. It says the cost overrun isn't explained. Fair. I add a line. Prompt four: cut it by a quarter without losing any number or decision. Done.

### The reader review, up close

Let's zoom in on step three, the reader review, because it's the step most people skip and the one that makes you look best. Here's the prompt. Read this report as my director would. What is unclear, what is missing, and what would you question? List the top five issues, most important first. Don't rewrite it. Why don't rewrite it? Because you want to stay the author. A list of issues lets you decide which ones matter and fix them in your own words. And the ranking matters, because you might only have time to fix three. Typical catches include a conclusion buried in paragraph four, jargon your reader won't know, a number with no comparison, like sales were four hundred units without saying whether that's good. Fix those, and your document answers questions before anyone asks them.

### Write where you work

You don't have to do this in a chat window. If your organization uses Microsoft 365 Copilot, you can draft and rewrite right inside Word, and it can reference other files you have access to. Gemini does the same in Google Docs. ChatGPT's canvas, Claude's document features and Notion AI all let you edit a draft side by side with the assistant. The tools look different, but the workflow doesn't change. Outline, section by section from your notes, reader review, tighten. And the rules don't change either. Only your facts, TBC for gaps, and you check it before it goes anywhere.

### Common mistakes

Common mistakes. Asking for the whole document in one prompt with no notes. You'll get generic content every time. Leaving TBC in the final version. It happens more than you'd think, so search the document for TBC before you send. Keeping filler sentences. Readers value specific facts over generic statements, and filler is the easiest giveaway of an unedited AI draft. Letting the AI invent figures, quotes or references. If you can't trace a number to a source, it doesn't go in. And using AI wording for anything legal, HR or policy related without the right person reviewing it. AI can draft it. A responsible human signs it off.

### Recap and try this now

Let's recap. Don't ask for a whole document at once. Outline first and approve the plan. Draft section by section from your real notes, with TBC for anything missing. Ask for a reader review before your manager does it for you. Then tighten, keeping every number and decision. Finish with the final check list: no TBC left, every number traced, no filler, headings in the reader's order, and the right review for policy or legal wording. Here's your try this now. Take a document you need to write this week and run the four prompts from the lesson text. Keep track of how long it takes. I think you'll be pleasantly surprised.

## Key takeaways

- Outline first, then draft section by section from your notes; your judgment matters most at the outline.
- Tell the AI to use only your notes and write [TBC] for gaps, then fill every [TBC] before sending.
- Ask for a reader review ('what would my director question?') before your manager sees it.
- Delete filler sentences and trace every number to a source you can name.

## Try it

Use the four-step workflow for a real document you need this week. Count how many [TBC] items appeared and fill each from a reliable source.

- [Previous: Email drafting that sounds like you](https://optimizeall.com/learn/ai-for-everyday-productivity/email-drafting-with-ai)
- [Next: Summarizing anything: reports, threads, articles and videos](https://optimizeall.com/learn/ai-for-everyday-productivity/summarising-anything)
- [All lessons of AI for Everyday Work: Writing, Research, Meetings & Data](https://optimizeall.com/learn/ai-for-everyday-productivity)