BS 202001 is a British Standard that sets out project controls as an auditable specification. The current edition, BS 202001:2025, is voluntary unless a contract, client, or regulator requires it.
Most organisations running project controls today are working from the same unstructured playbook: a cost report built in one tool, a schedule maintained in another, a risk register somewhere else, and a set of informal habits holding it all together. It works, until someone asks how a number was produced and the honest answer is a chain of spreadsheets and judgement calls rather than a documented process.
BS2001 is the first British Standard to set out project controls as an auditable specification and how an organisation can demonstrate that those controls are working as intended.
In this blog, we explore what BS 202001 covers, who it applies to, and what it means in practice for project controllers.
What is BS 202001?
BS 202001:2025 is a specification published by the British Standards Institution (BSI) in September 2025, that defines what project controls look like and how organisations can evidence it.
It sets out requirements for project controls themselves, how those controls integrate with each other and with wider business systems, and how they are implemented, monitored and assured across a project or programme's life cycle. It also includes a competence framework component covering the people side of project controls, not just the process and data side.
It is written to apply to projects of any size, sector or delivery model, which is a deliberate departure from earlier guidance that tended to be written around a specific industry or contract type.
What does BS 202001 require?
The specification is organised around a small number of themes:
- Project controls requirements, and how they integrate with critical business systems
- Principles of data definition, so cost, schedule and other data mean the same thing across a project
- Data gathering and analysis
- Integrated cost, schedule and risk control systems, rather than three systems that don't talk to each other
- Implementation, monitoring, assurance and audit of controls
- A competence framework covering the people responsible for running project controls
Who does BS 202001 apply to?
Ask the supplier the same questions and score the answers against your requirements. Share these findings with project and procurement teams. Request a demo that runs one of your own BIM workflows, from model upload to sign-off.
How does a CDE improve construction data management?
Because it is written to apply across sectors and delivery models, BS 202001 is relevant to anyone with a stake in how a project's numbers are produced and governed, for example:
- Project controls and commercial teams
- Project Management Offices (PMOs) and programme directors
- Consultants and cost managers
- Contractors
- Developers, government bodies, and investors who rely on project reporting
Is BS 202001 mandatory, and can you be certified against it?
Like most BSI specifications, BS 202001 is voluntary unless a contract, client or regulator specifically requires it. Organisations and programmes choose whether to adopt it, there is no default legal obligation. As at [publication date], no product-level certification scheme exists.
It is assessed at organisational or project level, not awarded to a piece of software. That makes it an important standard for project controllers to build toward now, and a good benchmark to look for when evaluating a project management tool.
How does BS 202001 relate to the PMBOK Guide, 8th edition (2025)?
The PMBOK (Project Management Body of Knowledge) Guide, 8th edition (2025) published by the Project Management Institute, is structured around six core principles and seven performance domains:
- Governance
- Scope
- Schedule
- Finance
- Stakeholders
- Resources
- Risk
It offers non-prescriptive process guidance rather than a set of testable requirements, meaning it describes good practice but is up to organisations to decide how they want to apply it.
BS 202001 works differently. It's a specification, written in a form that can be assessed and audited against, so it sets out requirements rather than principles.
That's the core distinction: PMBOK is a body of knowledge: there is no accredited scheme that certifies a product or organisation against it, only individual credentials such as the Project Management Professional (PMP). BS 202001 is a specification, written in a form that supports being assessed against. In practice, many project controllers will use PMBOK for shared vocabulary and discipline, and BS 202001 as the more auditable reference point when building or reviewing a controls framework.
How does BS 202001 compare to ISO 21500 and ISO 21502?
ISO 21500 provides the vocabulary and context for project, programme and portfolio management. ISO 21502 gives guidance on practices for project management. Both are international guidance documents: they describe what good practice looks like and leave each organisation to decide how to apply it. The APM Body of Knowledge works the same way.
BS 202001 differs on two counts. It is a specification rather than guidance, so it states requirements that can be tested and audited. And it addresses project controls specifically — cost, schedule, risk and the data underneath them — in more depth than either ISO document, which treat controls as one part of a wider management framework.
In practice the two sit together rather than compete: ISO 21502 for the management framework, BS 202001 for the controls that evidence it.
What this means for project controllers
For most teams, BS 202001 will not describe anything unfamiliar. Linking cost, schedule and risk data; defining data consistently across a project; monitoring and auditing controls rather than trusting them by default: these are things experienced project controllers already push for. What the standard adds is a shared reference point. It gives teams language to make the case internally for tighter controls, and a checklist to test a software vendor's claims against, rather than taking "integrated" or "compliant" at face value.
As the standard gains traction, expect more platforms to describe themselves against it. The organisations best placed to benefit are the ones that ask a simple follow-up question: which parts of that claim are verified, and which are still on the roadmap?
Five questions to ask a vendor claiming BS 202001 alignment
-
Which clauses of BS 202001 does the product support, and which does it not?
-
Are cost, schedule and risk held in one linked data model, or reconciled between separate modules?
-
Is governance enforced by the system, or by written policy a user can work around?
-
Can you trace a single reported number from source data to published report, with a complete audit trail?
-
Which parts of that claim are live today, and which are on the roadmap?
Frequently asked questions
When was BS 202001 published?
BS 202001:2025 was published by the British Standards Institution on 30 September 2025.
Is BS 202001 mandatory?
No. It is voluntary unless a contract, client or regulator specifically requires it.
Can a software product be certified to BS 202001?
No. It is assessed at organisational or project level. At the time of writing, no product-level certification scheme exists.
Does BS 202001 replace an existing standard?
No. It sits alongside existing guidance such as ISO 21502 and the APM Body of Knowledge, and addresses project controls specifically.
What is the competence framework in BS 202001?
The specification includes a competence component covering the people responsible for running project controls, not only the process and data requirements.
Is there a companion standard?
Yes. BSI positions BS 202001 alongside BS 202002, which covers benefits management on portfolios, programmes and projects.
Where Asite fits
Asite's Project Management Information System (PMIS) is built around the same structure BS 202001:2025 specifies: linked cost, schedule and risk data, governance enforced at the database level, and a full audit trail rather than a policy document.
We describe our own position honestly as alignment-ready, designed to support the standard's requirements, rather than certified or compliant, since no product-level certification scheme exists yet.
If you are reviewing your own project controls against BS 202001, or want to see how a governed, connected approach to cost, schedule and risk works in practice, contact the Asite team today.
5 minute read
Asite Insights in your inbox.
Sign up for product news and our latest insights.
