Build review in 10 minutes
Run a structured build review pass that catches the most common issues fast.
Why this matters
A build review is not reading the unit again. It is checking that the build matches the storyboard and the platform's own quirks. Here is the working sequence.
The 10-minute pass
Open on a phone first
Most learners will. Most bugs will be visible there before they're visible anywhere else.
Unit introduction
Are unit titles italicised? Is spacing between paragraphs intact?
Italics check
Italics aren't always copied from storyboard to build. Look for module titles, language examples, end-of-unit references.
Font sizes
20 for main text. 24 for reflection / note taking / tips. 16 for asset titles and transcripts.
Grouped blocks
Where the same pattern repeats (e.g. text + audio + reflection × 3), is each group numbered with a Continue between?
Asset titles match storyboard
"Teacher 1 audio" / "Teacher 1 audio transcript" — and so on.
Try it
On a unit you've built, run the six checks above in order. Time yourself. Most experienced reviewers land between 8 and 12 minutes.
One thing to take back to work today
Use this list on your next build review. Don't reread the unit — check the six things, in this order.