Documents and reports: from blank page to solid draft

0:00 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.

0:44 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.

1:31 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.

2:20 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.

3:06 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.

3:59 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.

4:57 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.

5:57 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.

6:41 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.

7:28 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.