Your BEP was approved three months ago. Is anyone actually following it? This guide covers day-to-day BEP compliance - QA/QC gates, information exchanges, CDE workflows, and what to do when an audit lands on your desk.
Most teams write the BEP during mobilisation and never open it again. Six months later, the actual delivery process has drifted so far from the document that an audit would fail on contact. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. The fix isn't to write a better BEP - it's to build compliance into your daily workflow so the BEP stays current without heroic effort.
The core problem: BEP compliance isn't a document problem - it's an operations problem. If your team doesn't have a daily workflow that naturally enforces what the BEP says, no amount of documentation will save you in an audit.
The BEP typically specifies a quality assurance process. In practice, this is where compliance breaks down first - because QA gates require time and discipline, and both are in short supply on active projects. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. A robust QA process needs at least three independent checks before any information reaches the CDE in "shared" status.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident. The key is that no person signs off on their own work. Gate 1 catches the obvious errors. Gate 2 catches the coordination issues. Gate 3 catches the compliance gaps.
JES runs a three-tier quality gate on every deliverable - here's exactly how it works.
ISO 19650 defines four CDE statuses: work-in-progress, shared, published, and archived. The BEP should specify exactly what triggers each status transition - and who has authority to trigger it. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
This is the most abused transition. Teams routinely push models to "shared" before they've passed internal QA because the project programme is pressing. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Published means the appointing party has reviewed and accepted the information. This requires a formal approval workflow - not just a verbal "looks good." Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Audit tip: The most common audit finding is information in "shared" status that was never formally reviewed. If your CDE doesn't enforce a review step between shared and published, you need a manual process - and that process needs to be documented in the BEP.
The MIDP (Master Information Delivery Plan) is the schedule that says when each information container is due, from whom, and to what LOD. If your project doesn't have one, you're not compliant. If you have one but nobody checks it, you're not compliant either. Lorem ipsum dolor sit amet.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Get both in the ISO 19650 template pack - pre-structured with section headings and guidance notes.
Revisions are inevitable. The question is whether your revision workflow maintains BEP compliance or breaks it. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Every revision should go back through the QA gates - not just the final gate. If a modeller changes a model, it needs to be self-checked (Gate 1), coordination-checked (Gate 2), and signed off (Gate 3) before republishing.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
If you've been running the processes above, an audit is just a confirmation exercise. If you haven't, it's a scramble. Here's what auditors typically check.
The shortcut: If you have an ERP system that logs tasks, QA gates, and revision history automatically, audit preparation takes hours, not weeks. This is why process-driven delivery matters - the compliance evidence generates itself.