What does the monthly check actually look at?

The check is a comparison, not an inspection. On a project it reads what the systems captured against what the month actually contained: the instructions given against the instructions recorded, the changes that happened against the variation record, the CVR against the position being reported. At business level it reads the month-end the same way: what rolled up on its own against what got re-keyed, where the pack matches the jobs' records and where a number was reshaped by hand on its way to the board. Alongside both sits a check on the tools themselves, because features move and settings reset without asking. The output is deliberately small: a short list of what drifted, each item fixed with the person it belongs to rather than filed in a report, so the check stays a working habit instead of a document nobody reads.