Tailoring: the skill PMBOK® Guide 8 expects

The PMBOK® Guide – Eighth Edition from PMI® gives you 40 processes and then tells you not to run them all. Tailoring is the skill that sits between the book and the job: choosing how much process, control and paperwork a project actually needs, and writing that choice down. This lesson explains what PMBOK 8 means by tailoring, walks through its four-step sequence, and builds a tailoring log for Northgate Distribution Centre, our fictional warehouse project in Vaughan.

Learning outcomes

• Define tailoring and explain why PMBOK 8 treats it as an expected skill, not an option.
• Name the three things PMBOK 8 says you tailor and the four steps it uses to do it.
• Decide, domain by domain, whether a project needs lighter or heavier treatment than the organization's default.
• Record tailoring decisions in a short log that an auditor, a sponsor or your replacement can follow.

The lesson

What tailoring means

Tailoring is the deliberate adjustment of the project management approach, governance and processes to fit a specific project and its environment. PMBOK 8 ties it back to the principles in The Standard for Project Management. The guide's own example is risk appetite. An organization with a low tolerance for risk will want more structure and oversight. One with a higher tolerance can accept a lighter, more agile setup.

Two points are easy to miss.

• Tailoring goes both ways. It isn't only about cutting process. A first-of-its-kind facility, a public owner or a lender-funded job may need more control than the organization's default.
• Tailoring is a decision, so it needs a reason. “We didn't have time” is not tailoring. “We dropped formal earned value because the contract is stipulated price and progress draws already track it” is.

What you tailor

The guide's tailoring chapter names three things to tailor.

1. The life cycle and development approach. The phases, and whether each piece of work is predictive, adaptive or hybrid. Lesson 4 covered this.
2. The processes. Which of the 40 you use, how formally, and with which tools and outputs. You can add, drop, combine or simplify them.
3. Engagement. Who takes part, how decisions get made and how much authority the team has.

The guide also gives tailoring considerations for each of the seven performance domains, and a set of diagnostics: signs that the current setup is not working.

The four-step sequence

PMBOK 8 sets tailoring out as four steps. The names below are BRC's paraphrase.

• Step 1: pick a starting approach. Decide whether the work is mainly predictive, adaptive or hybrid. Treat it as a working assumption, not a label you are stuck with.
• Step 2: fit it to the organization. Apply what the organization requires: approval authorities, PMO standards, reporting formats, audit rules. For an owner, this is usually a capital projects policy and a delegation of authority.
• Step 3: fit it to the project. Adjust for this job: its size, complexity, contract form, team, regulators, site and stakeholders. This is where most of the judgement lives.
• Step 4: keep improving it. Review the setup at milestones and whenever something goes wrong. Is a control producing paperwork nobody reads? Did a problem slip through because a control was missing? Adjust, and feed what you learn into the organization's template.

Tailoring by performance domain

A practical way to apply step 3 is to go through the seven domains and set each one, like a dial, lighter or heavier than standard. The questions BRC asks:

• Governance: how many approval levels, and how fast must a decision be made?
• Scope: how firm is the design, and how formal must change control be?
• Schedule: how much detail does the owner need to see, and how often?
• Finance: how much money, how many funding sources, how much contingency to control?
• Stakeholders: how many outside parties, and do any of them have a veto?
• Resources: does the owner supply people, equipment or contracts of its own?
• Risk: how new is the work, and what happens if the key date is missed?

Diagnostics: is the tailoring wrong?

Step 4 needs evidence. These symptoms usually mean the dials are set wrong.

• Too heavy: reports nobody reads, approvals that take longer than the work, a change log full of $500 items, a team that works around the process instead of through it.
• Too light: surprises at the monthly meeting, decisions nobody can trace, contingency spent without a record, a schedule update that can't explain why a milestone moved.

Write it down

PMBOK 8 expects tailoring to be deliberate. In practice that means a short tailoring log in the project management plan: one line per decision, with the domain, what was changed from standard, why, who agreed and when it will be reviewed. It takes an hour to write. It saves days when an auditor, a new Owner's PM or a claims consultant asks why something was or wasn't done. The format is BRC's practice, not something PMI prescribes.

Northgate worked example

Northgate Distribution Centre (fictional) has a $38.0M construction budget: a $34,950,000 CCDC 2-2020 stipulated price contract with Halvorsen Builders Ltd. (fictional) plus a $3,050,000 owner contingency. The design team is led by Ridgeline Architects Inc. (fictional). The owner's master schedule is a Microsoft Project file, NDC_OwnerMaster_2027-01-11.mpp. Halvorsen's Oracle Primavera P6 submissions are reviewed in the owner's P6 database using the shared “NDC Owner Review” layout.

Step 1 was settled before tender: a predictive contract with a hybrid owner plan, as lesson 4 explained. Step 2 came from Northgate's own rules at the owner's internal handoff meeting on January 14, 2027. Step 3 is the log below, shared with Halvorsen and Ridgeline at kickoff on January 19.

Notice the mix. T-02 and T-03 each make one part heavier and another lighter. T-04 tailors something out, but says when to bring it back. None of the rows says “as per PMBOK”. Each gives a reason tied to the contract or the building. The dial positions in Figure 2 follow from this log.

Owner's move

• Ask for the tailoring log with the project management plan. If your owner's representative or PM can't produce one, the plan is probably a template.
• Insist on a reason in every row. The reason should point at something real: the contract form, the building type, a regulator, the money at stake.
• Tie each row to a review date that is a real milestone. Tailoring reviewed “as needed” is never reviewed.
• Tailor the contractor's reporting in the contract, not after award. If you want the P6 file, the lookahead or a cash flow forecast, it has to be in the specifications or Supplementary Conditions. On Northgate the baseline is due 30 days after execution under the owner's Supplementary Conditions.
• Feed step 4 back into the organization. At closeout, update the owner's standard so the next project starts from a better default.

Common mistakes

1. Treating tailoring as cutting. Some domains need to be heavier than standard. On Northgate, Finance and Schedule move up, not down.
2. Tailoring silently. A process you skipped without recording why looks like an omission, not a decision, when someone reviews the file later.
3. Tailoring once. The setup that suits pre-construction is wrong for commissioning. Step 4 exists for a reason.
4. Copying the contractor's setup. Halvorsen tailors for its risks: labour, trades and production. The owner tailors for different ones: money, authority, occupancy.
5. Forgetting the organization step. A clever project setup that breaks the owner's approval policy will be overruled at the first change order.

Quick quiz

1. Which statement best describes tailoring in PMBOK 8?

   1. Removing processes to save time
   2. Deliberately adjusting the approach, governance and processes to fit the project and its environment
   3. Using all 40 processes at reduced depth
   4. Letting the contractor choose the project management method

2. Which of these is NOT one of the three things the guide says you tailor?

   1. Life cycle and development approach
   2. Processes
   3. Engagement
   4. The Contract Price

3. Northgate applies its delegation of authority and standard reporting formats. Which step is that?

   1. Step 1, pick a starting approach
   2. Step 2, fit it to the organization
   3. Step 3, fit it to the project
   4. Step 4, keep improving it

4. The owner drops quantitative schedule risk analysis but plans to revisit it if float to Ready-for-Takeover erodes. What makes this good tailoring?

   1. It reduces cost.
   2. It follows PMBOK exactly.
   3. It is recorded with a reason and a trigger for review.
   4. It moves the Risk domain to very light.

5. Approvals on a project routinely take longer than the work they approve. What does this most likely show?

   1. Governance is tailored too heavily for the work.
   2. The project should switch to adaptive.
   3. The contractor is at fault.
   4. Tailoring is not allowed on stipulated price contracts.

Key terms

Tailoring

Deliberately adjusting the project management approach, governance and processes to fit a project and its environment. It can make things lighter or heavier.

Engagement

In tailoring, the choices about who takes part, how decisions are made and how much authority the team has.

Diagnostics

Signs that the current tailoring is not working, used to trigger adjustment.

Standard setup

BRC's term for the organization's default approach after step 2, before project-specific tailoring.

Tailoring log

A short record in the project management plan of each tailoring decision, its reason, who agreed and when it will be reviewed. BRC practice, not a PMI-prescribed artifact.

Delegation of authority

An owner's internal rule setting who can approve what, and up to what amount.

References

1. Project Management Institute. PMBOK® Guide – Eighth Edition and The Standard for Project Management (November 2025, 408 pages; tailoring practices, tools and techniques to context).
2. PMI, via O'Reilly Learning. Tailoring section, table of contents and overview (what to tailor; the four-step tailoring process; tailoring the performance domains; diagnostics).
3. PMExams. PMBOK 8: The Four-Step Tailoring Process in Plain English. Independent study guide, not PMI.
4. PMExams. PMBOK 8 Tailoring for Project Characteristics (complexity, uncertainty, interdependence, financing risk). Independent study guide, not PMI.
5. Ricardo Vargas. My first impressions about the PMBOK Guide 8th Edition (tailoring guidance within each domain).

Verified on November 4, 2026.