Nobody has read the whole package

Anyone who has issued a consultation package knows this. Each discipline has checked its own part. Nobody has read the whole package, or the plan description next to the plan maps. That is where the conflicts sit, and the product review comes last, after everything that ran late.

One case on our Try page: the consultation documents for a road, reviewed against the kontrollprogram before issue. Yesper handed back one protocol, 204 findings, nine of them critical. The sharpest: protective measure S3 is a noise barrier in the plan description and a wildlife fence on the plan map.

S3 gets one meaning while both can still change. The conflicts come up in your own review, not in the client's. Same for any delivery with a kontrollprogram, and the rest of the Try page: a cross-check between documents, drawing revisions against the drawing list, a coordination review of a design package.

Try it yourself →