Cases, not theory. Each of these is a failure I have watched happen, taken apart to show the mechanism — because the mechanism is the part that repeats.
A programme showed completion past the Time for Completion. The Engineer said nothing. The contractor read that silence as acceptance, and as notice of delay. It was neither — and there is a sting in the tail most people miss.
The most common finding is not that quality activities are absent. They are happening. It is that nobody outside the project can prove it — and your best people are the reason you cannot see the gap.
By the time the completion date moves, the delay is old news. It happened months ago, on a path nobody watched, in a number nobody reports. And you may have paid for it twice.
A claim dies because the records that would have proved it were never made. A quality system fails an audit because the trail was never built. A project loses its float in March and finds out in September.
Same failure, three costumes.
The record you need on the bad day has to be created on the ordinary day, by someone who has no idea the bad day is coming.
That is the whole discipline. Everything else is detail — and everything on this site, the tools included, exists to make that one thing easier to do.
FIDIC cases, quality systems, schedule control, and new tools. Written from real projects, not from a classroom. No filler, and nothing you could have found in a textbook.