Build the monthly report, end to end

Everything in this course, applied to the folder from lesson 0, in the order you would actually do it.

Lesson 0 promised an afternoon of work that happens without being asked. This is that setup, and each piece is something you built alone in an earlier lesson.

The pieces

The brief, now that everything else exists

Run the monthly sales clean-up on Sales/2026, then write the
manager summary and a five slide deck.

Stop and tell me rather than guessing if a file is missing or a
column does not match. Do not invent numbers.

Say the row count before and after, and how many rows were dropped.

Three short paragraphs, where lesson 2 needed four and every one of them was about the data rather than the job. The columns, the region spellings and the date format are in the skill. Who reads it and what clean means are in the project. The formatting and the never-send rule are global. What is left is the job.

The order to build it in

Doing this in one sitting produces a setup for a job you imagined. Doing it across two real months produces one for the job you have, and the difference shows up the first time an export arrives in a shape nobody expected.

How you know it is working

• The result arrives before anyone asks for it.
• The numbers in the summary match the spreadsheet, and it says so itself.
• When something is wrong with the data, it stops and tells you instead of producing a tidy answer.
• The brief has stopped changing.

What this course left out

Each of those is documented in the Help Centre, and none of them changes anything you learned here. They are the same product with more administration around it.

You are done

You can tell a job from a question, describe one well enough to leave it alone, and say where the result should land. You know where the work runs, what it can reach, and why that boundary is the thing that makes prompt injection survivable. And you can turn a procedure into a skill, hand it to somebody else, and let the calendar start it.