Rather than start with the builder, this lesson starts with a workflow already running, on a progress claim partway through its approval.
A live run
Open the claim and a strip of chips sits across the top of the record. That strip is the run: one chip per step, in order, coloured by state. Two steps are complete, a project manager endorsement and a commercial review, and the final approval is sitting with someone right now.
Reading the chips
Hover a chip and you get who acted and when. That is the whole audit trail, in the place you were already looking, which is the point: nobody should have to go and ask where a claim is up to. Complete, current and upcoming steps look different from each other, so an item where it is genuinely your turn is distinguishable at a glance from one merely heading your way.
Where the run came from
The chain did not happen by accident. Somebody designed it as a template, and the template was bound to this contract. Everything else in this course is about those two things: the shape, and the binding.
One engine, every module
The same engine runs progress claims, variations, contract execution, procurement recommendations, site diaries, bookings, timesheets, submittals, incidents, inductions and more. Learn it once here and every module's approval behaviour is already familiar.