Why a record says awaiting approval, and who it is waiting on. Progress claims, variations, site diaries, bookings, timesheets, submittals, incidents and inductions all go for approval, and one engine carries every one of them.
The chips on a record
When something is submitted, a strip of chips appears across the top of the record. That is the running workflow: each chip is a step, coloured by state, and hovering one tells you who acted and when. Reading the chips answers "where is this up to" without asking anyone.
Where the shape comes from
Every run comes from a template, and templates live on each tool's Workflows tab in the project's Tools area. Above the project's own list sits your organisation's list: organisation templates hold the shape of the process, and a project copy holds the actual approvers for this job. Set the standard once, name the people per project.
The builder
A template is a diagram you read left to right: a trigger starts the run, decision blocks put it in front of people, and each outcome is a path. Approve moves forward; reject drops into a lane that sets the status, notifies the submitter and loops back for revision. Around the human blocks sit notify, wait, conditional and status blocks.
Binding
A template does nothing until a record type points at it, which is called binding. A contract binds its claim workflow in its own settings; other tools bind theirs per type or inherit the organisation default. If something genuinely needs no review, bind an auto-approve template rather than nothing, so there is always a recorded path.