Plan and manage compliance
In the app: Project → Compliance
PMP ECO · Business Environment (26%) · Task B2. Find every requirement the project has no choice about, give each an owner and a date, prove it's met, and measure honestly how much is.
What it is
Compliance covers the requirements the project must meet: laws, regulations, building and safety codes, permits, standards, certifications and contractual obligations. Unlike most project decisions, there's no trade-off: you meet them, or you face the consequence.
Managing compliance means, for each requirement:
- Identify and classify it: regulatory, health & safety, environmental, sustainability, data privacy. Note why it applies to this project.
- Plan how it will be met: who owns it, and by when. Many requirements gate a specific piece of work: no fire certificate, no occupancy; no occupancy, no opening.
- Track it with evidence. "Compliant" means there's a record that proves it: a certificate, a test result, an audit.
- Review it. Many requirements need re-checking: monthly monitoring, periodic audits.
- Know the consequence of failing it, so priorities are obvious.
Then measure the extent of compliance: how many applicable requirements are met. Count every applicable requirement, not just the ones with a final answer, or the measure flatters the project.
Why it matters
- Non-compliance stops work. A revoked clearance or a refused certificate isn't a variance; it's a halt.
- Some requirements can only be met at the right time. A sustainability rating that depends on design choices can't be added after the design is frozen.
- Evidence is what counts in an audit. "We did it" without a record is a finding.
Where you do it in VanillaPM
- Project → Compliance is the register. The top shows the extent of compliance: compliant over applicable, with a bar for compliant, in progress and non-compliant. Then the counts: compliant, in progress, not started, non-compliant.
- Needs attention lists every requirement that's non-compliant, not met by the date it's needed, overdue for review, or has no owner.
- Each requirement carries its category and source, owner, needed by (and the schedule activity that needs it), next review and status. Click one to see why it applies, its evidence and the consequence of failing it.
Walked example — Coral Ridge Resort
Coral Ridge has six requirements; one (guest data privacy) belongs to the operator's system, so it doesn't apply to the build. Of the five that do:
- Compliant (2): the coastal (ECA) clearance, with monthly monitoring reviewed next on 27 November; and the building code, with its evidence including the concrete record from Pr7: 15 of 16 pours met the strength spec, and pour 10 was broken out, re-cast and re-tested.
- In progress (2): fire safety, owned by the MEP lead and needed by May 2028 for the occupancy certificate, which is on the critical path (Pr8); and worker health & safety, audited monthly.
- Not started (1): LEED Gold. It has no owner and no evidence. Its credits depend on design choices, so it was needed by the design freeze in January 2026, which has passed. This is why the LEED benefit in Pr3 was at risk.
So the extent of compliance is 40%: 2 of 5. A measure that counted only decided requirements would show 100%.
The workspace — the theory behind each screen
Every screenshot is the actual sample project, not a mock-up.
1 · The extent of compliance, measured honestly
The theory: measure the extent of compliance. Compare what's met with everything that applies. Then look at what needs action: overdue, unowned, or out of date.

Reading the screenshot: Extent of compliance 40%, 2 of 5 applicable requirements met, with the bar split into compliant (green) and in progress (blue). Compliant 2, in progress 2, not started 1, non-compliant 0. Needs attention: CMP-005 LEED Gold certification: needed by 15 Jan 2026 (architectural design), and not met. Nobody owns it.
✅ Do divide by everything that applies, not by what's been decided.
❌ Avoid reporting "no non-compliance" as "fully compliant". Not started isn't compliant.
2 · The register: owner, date, review, status
The theory: plan compliance. Each requirement is planned like any other piece of work: an owner, the date it must be met, the work that depends on it, and how often it's re-checked.

Reading the screenshot: CMP-001 ECA clearance, Imran Hossain, compliant, next review 27 Nov 2026. CMP-002 building code, compliant. CMP-003 fire safety, Tanvir Ahmed, needed by 14 May 2028 for the occupancy certificate & fire-safety approval, in progress. CMP-004 worker health & safety, next review 30 Nov 2026. CMP-005 LEED Gold, no owner, needed by 15 Jan 2026, still only identified, flagged red. CMP-006 guest data privacy, not applicable.
✅ Do tie each requirement to the activity that can't proceed without it.
❌ Avoid a register with no dates. Without them, nothing ever looks late until it's too late.
3 · Evidence: what "compliant" rests on
The theory: compliance evidence. A compliant status is a claim; the evidence is the proof. Record it with the requirement, including any failure found and how it was corrected.

Reading the screenshot: CMP-002 Bangladesh National Building Code (cyclone wind zone). Applies because the structure must meet coastal wind and seismic loads. Evidence: the structural peer-review certificate, and the concrete cube record: 15 of 16 pours at or above 40 MPa; pour 10 (38 MPa) broken out, re-cast and re-tested. If not met: permit refusal; an unsafe structure.
✅ Do record the failure and its correction in the evidence. An honest record survives an audit.
❌ Avoid marking a requirement compliant because nobody has complained yet.
Best practices & pitfalls
- Do identify compliance requirements early, at planning, and revisit them as the project changes.
- Do give every requirement an owner, a date and a review cycle.
- Do keep the evidence with the requirement, not in someone's inbox.
- Pitfall: measuring compliance only over decided items. It always looks better than it is.
- Pitfall: discovering a design-dependent requirement after the design is frozen.
On the PMP exam
Know that compliance requirements come from laws, regulations, standards and contracts, and that the PM must identify them, plan how to meet them, monitor compliance, and analyse the consequences of non-compliance. Compliance is a non-negotiable constraint: the right answer meets it, or escalates when it can't be met, and never trades it away for schedule or cost. In scenarios where a regulation changes mid-project, assess the impact and raise a change request.