The PMBOK (Project Management Body of Knowledge) Guide is the Project Management Institute's (PMI) standard for managing projects. It gives builders, and homeowners running an owner-build, a common framework and language for planning and controlling a job. A house is a project, and most of the problems on a build are project management problems.

Whether you're a builder running five houses at once or a homeowner managing an owner-build, the same ideas apply: scope (your plans and specification), schedule (your build program), cost (your contract and variations) and quality (your ITPs and checklists).

What is the PMBOK Guide?

The PMBOK Guide is published by PMI and is used internationally. It's also the basis for PMI's Project Management Professional (PMP) certification. It doesn't tell you exactly how to run every project. It's a framework you tailor to the job in front of you.

How it has changed

If you learned the PMBOK years ago, it looks different now.

Up to the 6th edition (2017), the guide was process-based, built around five process groups (initiating, planning, executing, monitoring and controlling, closing) and ten knowledge areas:

  • Integration management
  • Scope management
  • Schedule management (called "time management" before the 6th edition)
  • Cost management
  • Quality management
  • Resource management (previously "human resource management")
  • Communications management
  • Risk management
  • Procurement management
  • Stakeholder management

The 7th edition (2021) moved away from detailed processes to a set of 12 principles and 8 performance domains, with more emphasis on delivering value and tailoring the approach.

The 8th edition (released November 2025) is the current version. It consolidates the guide into:

  • Six principles: adopt a holistic view, focus on value, embed quality, lead accountably, integrate sustainability, and build an empowered culture.
  • Seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk.
  • Five focus areas: initiating, planning, executing, monitoring and controlling, and closing, which bring back practical processes alongside the principles.

The labels change from edition to edition, but the core ideas don't.

What it looks like on a house build

Here's how the main PMBOK ideas line up with a residential build:

  • Scope: the plans, specification and inclusions list. Anything not in them isn't in the job, and anything added is a variation.
  • Schedule: the build program, from site start to handover, with the order of trades and inspection stages.
  • Finance (cost): the contract price, progress payment stages, provisional sums, prime cost items and variations.
  • Quality: the builder's quality management plan, Inspection and Test Plans (ITPs) and stage inspections.
  • Risk: site conditions, weather, material supply, trade availability and the builder's financial health.
  • Resources: trades, materials, equipment and the supervisor's time.
  • Stakeholders: you, the builder, the certifier, the council, the bank, neighbours and the trades.
  • Governance: who makes decisions, how variations get approved, and how disputes are resolved under the contract.

The life cycle works the same way. Initiating is choosing your builder and design. Planning is approvals, selections and the contract. Executing is construction. Monitoring and controlling is stage inspections, progress claims and variation control. Closing is practical completion, handover and the defects period.

Why builders should use it

  • A common language. When everyone means the same thing by scope, baseline and variation, there are fewer misunderstandings.
  • Fewer surprises. Planning risk, schedule and cost up front catches problems before they reach site.
  • Consistency. A standard approach across every job, instead of each supervisor doing it their own way.
  • Professional development. A licence is the minimum. Project management training such as the PMP or PRINCE2 shows a builder is investing in how they manage your job.

Why homeowners should care

You don't need to read the PMBOK to build a house. But knowing the basics helps you ask better questions:

  • Is the scope fully defined in the plans and specification before I sign?
  • What's the build program, and how will I be told about delays?
  • How are variations priced and approved?
  • How is quality checked at each stage, and can I see the records?
  • What are the main risks on my site, and who carries them?

A builder who can answer those clearly is managing your job as a project, not just building a house.

How to apply it

  1. Tailor it. Use what fits the job. A single house doesn't need the paperwork of a hospital project.
  2. Use it from start to finish, not just at the planning stage.
  3. Keep your project plan up to date. The PMBOK is a published standard; your plan, program and budget are what should evolve as the job progresses.
  4. Record lessons learned at the end of each job, and use them on the next one.

The bottom line

The PMBOK isn't a rule book to follow line by line. It's a framework that captures decades of project management experience. Builders who use its ideas tend to deliver jobs that are better planned, better controlled and easier for their clients to follow.