Classify strategic vs operational work

Not everything deserves a three-gate review. Project classification splits new work into two classes at the moment of creation: strategic initiatives go through the governance pipeline as proposals, operational work is created directly. The thresholds you configure tell people which side their work belongs on.

Enable classification

1. Open Organization Settings, go to the Governance tab, then the Classification section.

2. Turn on Enable project classification. This adds a Strategic or Operational picker to every new-project flow.

3. Set the Strategic Project Thresholds: a Budget threshold (50,000 by default), a Duration threshold in weeks (12 by default), and whether crossing team boundaries matters (Multi-team required). Projects meeting any of these criteria are recommended as strategic.

4. Optionally rename the two classes under Custom Labels. The defaults are “Strategic Project” and “Operational Project”, but a PMO might prefer “Major Initiative” and “BAU Work”. Your labels appear on the picker, on project badges, and in the type filter on the Projects page.

Changing classification settings requires the governance manage permission, Owner and Admin by default.

What creators see

With classification on, selecting New Project anywhere (the Projects page, quick create, the command palette) opens a New Project Request dialog with two cards:

• The strategic card describes cross-functional, high-budget, org-wide work and shows your thresholds as chips (for example “Budget > $50k”, “Duration > 12w”). Choosing it opens the proposal form, and the work enters the pipeline described in Submit a proposal.
• The operational card describes single-team, business-as-usual work. Choosing it goes straight to the normal project creation dialog, as in Create your first project, and the project is tagged with your operational label.

Note

The thresholds are guidance, not enforcement. The creator makes the call, and the cards exist to make the right call obvious. If your organization has governance enabled but classification switched off, there is no choice at all: every new project starts as a proposal, so the pipeline cannot be bypassed.

After creation

Projects carry their classification from then on. The Projects page gains a type filter using your custom labels, and projects born from approved proposals are classified as strategic automatically, complete with the Governed badge described in From proposal to governed project.

Best practices

1. Set thresholds at the level your governance can actually review. A budget threshold of $5k means every small initiative routes through gates and reviewers drown. A threshold of $500k means only massive initiatives get reviewed and mid-sized work skips governance. Pick the number your PMO has bandwidth for.
2. Rename the labels to your org’s vocabulary. “Strategic Project” / “Operational Project” works for many; some orgs prefer “Major Initiative” / “BAU Work”, “Transformation” / “Run the Business”, or specific portfolio names. The right label reduces conversational friction.
3. Train PMs on when each path applies. Even with thresholds visible, judgment calls happen. Brief project managers once: “if it’s > $50k, > 12 weeks, OR cross-team, file a proposal. Otherwise create directly.” A short rule the team can internalize beats hoping people read the chips.
4. Review thresholds annually. Inflation, scope creep, and changes in PMO capacity all move the right threshold over time. A yearly review keeps them aligned.
5. Use the type filter on the Projects page in portfolio reviews. Reviewing “all Strategic projects” separately from “all Operational” gives the PMO meaningful slices. The filter is one click; the discipline is using it consistently.

Troubleshooting / common pitfalls

• Classification picker doesn’t appear when I create a new project. Two causes: (a) classification isn’t enabled in Org Settings; (b) you’re in an org without governance enabled at all (it’s an Enterprise feature). Verify both.
• Someone routed a $500k project through the Operational path. Classification is guidance, not enforcement. The picker shows the thresholds as chips but doesn’t block the choice. If you need hard enforcement, leave classification off so all projects go through proposals.
• My thresholds look ignored. The chips on the Strategic card display the configured numbers, but the picker doesn’t auto-select based on form values — the user chooses. The number is guidance for the user.
• Custom labels aren’t appearing on existing projects. Labels apply going forward. Pre-existing projects keep whatever classification they had (or none if the feature was off when they were created).
• I can’t find the Classification section. Three causes: (a) Enterprise plan required; (b) your role doesn’t have org.governance.manage (Owner or Admin default); (c) you’re looking at the wrong tab — it’s under Governance, not Configuration.

How this combines with other features

• Classification + Proposal pipeline. Strategic projects route through proposals; operational projects bypass them. The classification is the routing switch. See Understand the proposal pipeline.
• Classification + Project creation gate. Project Creation Gate (a separate setting) controls WHEN an approved proposal spawns its project. Classification controls WHETHER projects pass through proposals at all. Both live in Governance settings; together they form the full intake flow. See From proposal to governed project.
• Classification + Reports. Cross-project Reports filter by classification, so portfolio reviews can roll up “all strategic work” vs “all operational” separately. See Run cross-project reports.
• Classification + Custom Dashboard. A widget filtered to strategic projects gives the PMO a single view of the high-risk portfolio. See Build a custom dashboard.

Coming from another tool

Tool	Mapping
MS Project Online Project Types	Direct concept; same intake routing
ServiceNow Demand Categorization	Similar idea, broader category set
Spreadsheet-based intake routing	Onplana adds first-class UX
Smartsheet	Similar via “project type” custom field
Asana / Jira	No native equivalent; teams use tagging

FAQs

Can someone route strategic work through the operational path? Yes, deliberately so; the picker is a routing aid, not a gate. If you need hard enforcement, leave classification off so every project request goes through a proposal, and let reviewers reject what does not belong.

Do the thresholds reclassify existing projects? No. Classification is chosen at creation time. Changing thresholds only changes the guidance shown to future creators.

This section also mentions a Project Creation Gate. What is that? It controls when an approved proposal spawns its project and is independent of the picker. It is covered in From proposal to governed project.

Can I have more than two classifications? Today the choice is binary (Strategic vs Operational). For finer categorization, use custom fields on the project (e.g. “Portfolio: Transformation / Infrastructure / Growth”).

What happens when I import projects? Are they classified? Imported projects don’t go through the picker. They land without classification unless your import flow sets it explicitly. Use bulk-edit on the Projects page to classify imported sets.

Can I see a count of strategic vs operational projects? Yes. The Projects page’s type filter shows the count next to each type chip; cross-project Reports can group by classification for percentage breakdowns.

Does classification affect billing or feature access? No. Classification is a routing label only; it doesn’t change seat usage, AI tokens, or feature visibility.

Related

• Submit a proposal — the strategic path
• Create your first project — the operational path
• From proposal to governed project — the project-creation gate