13.1 Portfolio — one workbook, one report, one deck
Written against this subject area's own modules, August 2026
What you'll be able to do
Finish this subject holding three pieces of work that prove it: a workbook, a report and a deck, each exercising the modules you passed through. Plus the one-page write-up that makes them readable to somebody deciding whether to trust you with real work.
Before you start
Pick one set of data you genuinely care about: your own expenses, a college club's records, cricket statistics, anything with a few hundred rows. All three pieces grow from it, and caring about it is what carries you through the finishing.
The work
- Same either way: the workbook uses the Excel modules from end to end. Raw data lands on a data sheet through an import that can be refreshed. Power Query, the importing and cleaning tool, cleans it with recorded steps that run again next month. A calculation layer holds the PivotTables and, where they are earned, measures. One dashboard sits on top, on one screen, answering five questions, with slicers and a restrained palette. A README sheet follows the hygiene lesson. Here is the test it must pass. Change the raw data, press refresh, and watch the dashboard update. Then a stranger explains the workbook back to you from its README alone.
- Same either way: the report uses the Word modules from end to end. It is a styled document about what the data shows, with real heading styles and sections giving it a cover and a numbered body. It has captioned charts pasted from the workbook, cross-references, a contents page that builds itself, and the CtrlA then F9 field update before you export the PDF. Here is its test. Insert a new figure in the middle, and watch every number and reference correct itself, while the Navigation pane shows the argument as an outline.
- Same either way: the deck uses the PowerPoint modules from end to end. Ten slides on your own master, with theme colours and your layouts, presenting the findings. One idea per slide. A big-number slide where the finding is a number. Notes carrying the words, and backup slides holding the detail. It is delivered aloud, timed, in five minutes. Here is its test. The rehearsal clock says five minutes, and the deck passes the accessibility checker on titles, alt text and reading order.
- Same either way: the write-up is one page, and it is what reviewers read first. For each piece of work, write three sentences. What it does. What skills it exercises, naming the features: Power Query, sections and fields, the slide master. And one decision you made, with the reason. "Medians, because the amounts are skewed" is the shape of that third sentence. The write-up is the way in, and the three pieces are the proof.
- Same either way: package and publish it as the sharing lesson taught. One folder, holding the three pieces and the write-up, on OneDrive, shared by a link that allows viewing only. Put PDFs beside the live files. The PDF shows anybody the result at once. The .xlsx, .docx and .pptx show how it was built, to anybody who knows what to look for. How it was built is what you are really exhibiting. This folder is this subject's entry in the learning log and portfolio habit. The AI and machine learning orientation module recommends it: evidence rather than assertion.
Try it
Block three sessions, one for each piece of work. Use the practice-file versions you already built through the modules as the frame for your own data's versions. Then do the write-up, the folder and the link, and get one round of feedback from a person who fits the audience.
Check yourself
What is the workbook's test, and what does passing it prove?
New raw data plus a refresh gives an updated dashboard, and a stranger can operate it from the README. That proves the pipeline is real, with its query, model and presentation layers, rather than a one-off built by hand.
What does the report's insert-a-figure test exercise?
The whole field system. Captions renumber, cross-references follow, and the contents page updates on F9. That is the difference between a styled document and a decorated one.
Why must the deck be delivered rather than only built?
The delivery skills — timing, notes, presenting to the room — are half the PowerPoint modules, and a deck never spoken is untested. Five minutes on the clock is the proof.
What belongs in the write-up, for each piece of work?
Three sentences: what it does, which named skills it exercises, and one decision with its reason. Reviewers read the write-up first, and it makes the work readable.
Why publish the live files and not only the PDFs?
Because how it was built is the exhibit: recorded query steps, real styles and fields, a genuine master. The PDFs prove the output, and the live files prove you built it properly.
Go deeper
We haven't checked most of these for screen reader use yet.
Back to Portfolio — one workbook, one report, one deck: work through the checklist