APQC Process Classification Framework (PCF): How to Use It

By Linh Ngo · Updated Oct 12, 2026

The APQC Process Classification Framework (PCF) is a free, industry-neutral catalog of the business processes a company performs, from setting strategy to closing the books. It gives every process a standard name and number, so you can build a process inventory, compare yourself with other companies, and avoid arguing over vocabulary.

What is the APQC Process Classification Framework?

APQC describes the cross-industry PCF as a taxonomy of cross-functional business processes intended to allow objective comparison of performance within and among organizations. It was built by APQC, a nonprofit, together with its member companies, as an open standard that works regardless of industry, size, or location.

Notice what it is not. It isn't a methodology, a maturity model, or a notation. It doesn't tell you how to improve a process or how to draw one. It's closer to a library's classification system: a shared list of what exists, organized so that anyone can find the right shelf. That's why it pairs so well with business process management, which supplies the discipline of managing and improving whatever you've catalogued.

The history matters for credibility. APQC's own document says the PCF was originally envisioned as a common language for benchmarking, with an initial design involving APQC and more than 80 organizations. It dates to 1992 and has been updated repeatedly since. This guide works from cross-industry version 7.4, dated August 2024. APQC published version 8.0 in February 2026, so check which release your team adopts.

Key Facts

• The PCF has been in use since 1992. APQC says the cross-industry framework has seen more than 30 years of use by thousands of organizations (APQC PCF 7.4).
• Version 7.4 (August 2024) organizes operating and management processes into 13 enterprise-level categories, with more than 1,000 processes and associated activities (APQC PCF 7.4).
• The hierarchy has five levels: category, process group, process, activity, and task (APQC).
• The PCF is free to download, and APQC grants a perpetual, worldwide, royalty-free license to use, copy, and modify it, provided you include APQC's attribution statement (APQC PCF 7.4).
• APQC lists 19 industry-specific versions alongside the cross-industry one, from Aerospace and Defense to Utilities (APQC).

The 13 categories

APQC splits the PCF into two groups. Categories 1.0 through 6.0 are operating processes, the work that creates and delivers value to customers. Categories 7.0 through 13.0 are management and support services, the work that keeps the organization running. Here are the names from version 7.4:

You may see older material that says the PCF has 12 categories. APQC's 7.4 document lists 13, so check the count against the release you use. Category names have shifted between releases too (an earlier APQC explainer calls category 4.0 "Deliver Physical Products"), which is a good reason to always note the version you're using.

One practical point: not every category applies to every company. A software firm may have little to put under 4.0, and a manufacturer will have a great deal. The PCF is a menu, not a mandate.

The five levels, explained

Each category breaks down into finer detail. APQC defines the levels like this:

The numbering is called the hierarchy ID. A two-digit ID such as 1.1 marks a process group, three digits a process, four digits an activity. Each element also carries a separate five-digit reference number. That number is what makes benchmarking work: you can rename a process to match your own vocabulary but keep the reference number, so it still maps back to the PCF.

There's one trap. APQC is explicit that the numbering doesn't imply order. You don't have to start with activity 1.1.1.1 just because it comes first. The PCF lists what exists, not the sequence in which it happens. If you need sequence, you need a flow diagram, which is what business process mapping and BPMN are for.

Cross-industry vs. industry-specific versions

APQC offers two kinds of PCF. The cross-industry version is the most generic and can be applied to any organization. Industry-specific versions are tailored to the unique needs of particular sectors. The versions APQC lists are:

• Aerospace and Defense, Airline, Automotive, Banking, Broadcasting
• City Government, Consumer Electronics, Consumer Products, Corrosion
• Downstream Petroleum, Upstream Petroleum, Education
• Health Insurance Payor, Healthcare Provider, Insurance
• Life Sciences, Retail, Telecommunications, Utilities

APQC's advice is to look at the relevant industry version as well as the cross-industry one, since an industry-specific framework is often a better fit, though not always. Release numbers also differ by industry. A banking or utilities PCF, for example, may sit on a different version than the cross-industry 7.4, so check each file's version before you mix them.

The version number itself carries meaning. APQC explains that the first number is the major release, the second the minor release, and the third a bug-fix count. So 7.3.1 to 7.4.0 is a small step within the same generation, not a rewrite.

PCF vs. other process frameworks

People often confuse the PCF with tools that do different jobs. The comparison below separates them by purpose.

The simplest way to hold this in your head: the PCF answers "what processes do we have, and what should we call them?" BPMN and SIPOC answer "how does this one process work?" The value chain answers "where do we make money?" And domain frameworks like SCOR for supply chain or ITIL for IT service management go deep on a single function, often with their own metrics and practices. The PCF stays wide and shallow on purpose, which is exactly why it's a good index to all of them. A SCOR-style supply chain model would naturally hang off category 4.0, and ITIL-style service management off category 8.0.

How to use the PCF step by step

Most teams get value from the PCF in four situations: building a process inventory, assigning ownership, benchmarking, and structuring a process repository. This sequence works for all of them.

1. Define why you're using it. Pick one purpose: an enterprise process inventory, a benchmarking exercise, or a clean structure for your documentation. Mixed goals produce messy scope.
2. Download the right version. Take the cross-industry PCF or the closest industry version from APQC and note the version number you adopt.
3. Prune to your business. Walk the 13 categories with function leaders and mark which process groups you actually perform. Delete the rest in your working copy.
4. Stop at the right depth. Levels 2 and 3 are usually enough for an inventory. Go to activities (level 4) only for processes you plan to improve, measure, or automate. Tasks are usually local and vary by company.
5. Rename without losing the link. Use your own terms, but keep APQC's reference numbers so your list still maps back for benchmarking.
6. Assign an owner to every level 3 process. One accountable person per process. Where no one owns a process, that's your first finding.
7. Attach measures. Link each process to a few process KPIs. Use the same definitions across teams so comparisons are fair.
8. Link out to detail. For each process you'll improve, attach its documentation and a flow map, and assess its maturity.
9. Review on a schedule. Revisit the inventory yearly. New products, acquisitions, and tools change what you do.

Process inventory template

Copy this table and fill it in for each process you carry forward. The columns are a suggested layout, not an APQC format.

A quick rule for the "Level reached" column: if you can't name an owner and a measure at level 3, don't descend to level 4 yet. Detail without ownership just becomes shelfware.

PCF examples by business function

These are illustrative scenarios showing how a function might use the framework, not case studies.

If your goal after cataloguing is consistency, the next step is process standardization, which works much better once everyone is naming processes the same way.

Do's and don'ts

Do:

• Record the PCF version you used, and keep the reference numbers.
• Customize the names and prune categories that don't apply.
• Stop at level 3 for most processes and go deeper only where it pays off.
• Assign one owner per process and one set of measures.
• Include APQC's attribution statement if you publish or share a derivative.

Don't:

• Treat the numbering as a sequence of steps.
• Adopt every process "because it's in the PCF." It's a menu, not a checklist.
• Mix versions or industry variants without checking they line up.
• Confuse a taxonomy with an improvement method. Cataloguing a process doesn't make it better.
• Spend months on levels 4 and 5 before anyone owns the level 3 processes.

Conclusion

The PCF is useful because it's boring in the right way. It gives you a common vocabulary, a numbered structure, and a free starting point, so you don't spend a quarter debating what to call "order to cash." Use it as the index for your process landscape, keep the version and reference numbers, and prune hard. Then reach for mapping, KPIs, and maturity tools to improve the processes you've now named.

Related reading

• Business process management
• Business process mapping
• Process KPIs
• Process maturity levels
• Benchmarking
• SCOR model
• ITIL framework