Project Intake and Prioritisation: A Practical Scoring Model Teams Can Implement in Weeks

Many organisations do not have a “project management problem”. They have an intake and prioritisation problem. Work enters the system informally, priorities shift weekly, and teams end up overloaded with too many initiatives running at the same time. In that environment, even excellent project managers struggle to deliver predictably because the portfolio itself is unstable and constantly being reshuffled without clear logic or discipline.

Table of Contents

A practical intake and prioritisation model does two things:

It Makes Decisions Visible: Everyone can see why work is approved, delayed, or declined, which removes confusion and reduces internal friction between teams competing for attention and resources.
It Protects Capacity: Fewer projects run at once, which increases throughput, improves focus, and reduces firefighting that comes from spreading teams too thin across competing priorities.

This article outlines a lightweight project intake workflow and a simple scoring model you can implement quickly without heavy tooling or long transformation programs. It is designed for mixed portfolios where projects vary in size, urgency, and stakeholder pressure, and where decisions need to be made consistently without slowing the organisation down.

Why Intake Fails in Real Organisations

Intake processes fail for predictable reasons, and most organisations experience the same patterns regardless of industry or size. If you recognise these issues, it is not a sign of poor management, but rather a lack of structure around how work enters and is evaluated across the organisation.

Requests Arrive Through the Path of Least Resistance

Work gets approved because someone asked in a meeting, sent a message to a senior leader, or raised it informally in passing. Over time, this creates a system where influence matters more than value. The “queue” becomes whoever has the loudest voice rather than the highest-impact initiative aligned to business priorities.

Teams Do Not Trust the System

If people feel the process is slow, unclear, or biased, they will find ways around it. This leads to shadow prioritisation happening outside the official system. A good intake model must be fast, transparent, and consistent so that teams believe it is worth following rather than bypassing.

Everything Is Urgent

When prioritisation criteria are unclear or poorly defined, every project is framed as critical to gain attention. Without a shared scoring model, leaders are forced to rely on storytelling instead of evidence, which creates inconsistent decisions and reinforces the idea that urgency is subjective rather than measurable.

Capacity Is Invisible

Approving projects without understanding who will actually deliver them leads to predictable overload. Teams appear busy but make slow progress because effort is fragmented. Without visibility into capacity, organisations commit to more work than they can realistically execute, resulting in missed deadlines and declining quality.

The Goal of Prioritisation Is Not Perfection

One of the biggest mistakes in prioritisation is aiming for perfect scoring or absolute precision in decision-making. That level of accuracy is not required and often slows the process down. What matters is having a repeatable, structured way to compare initiatives so that trade-offs can be made consistently and quickly.

A good scoring model achieves:

Fairness: Similar projects are treated similarly, reducing bias and internal conflict between teams competing for approval.
Consistency: The same criteria are applied across departments, ensuring decisions align with organisational priorities rather than individual preferences.
Speed: Decisions can be made without weeks of debate, enabling faster movement from idea to execution.
Transparency: Teams understand why decisions were made, which builds trust and reduces resistance to outcomes.

A Lightweight Project Intake Workflow

You can implement a workable intake process using four simple steps that do not require complex systems or long setup periods. The key is to keep entry requirements light at the beginning, then increase detail only after a project has been accepted into the delivery pipeline and resources are committed.

Step 1: Submit a Short Request

A good intake form captures just enough information to evaluate value, urgency, and effort without overwhelming the requester. Aim for a one-page submission that is quick to complete but still structured. Include:

Request title and brief description
Problem statement and objective
Requestor and sponsor
Expected benefits (pick categories such as cost, risk reduction, customer, compliance, capacity)
Deadline drivers (regulatory, customer commitments, operational windows)
Rough effort estimate (small, medium, large is often enough at first)
Known dependencies or constraints

If you require detailed plans at the intake stage, people will either avoid the process entirely or submit low-quality information just to get through it. Keeping it simple improves adoption and overall data quality.

Step 2: Triage Quickly

Not every request deserves full evaluation, and pushing everything through scoring wastes time. A quick triage step ensures only relevant and viable requests move forward. This stage helps filter noise and organise incoming demand before deeper analysis begins. It should remain fast and practical.

Route requests to the right owners
Merge duplicates that describe the same need
Reject items that are clearly out of scope or of low value
Identify “fast path” work that can be handled as a minor change rather than a full project

This step can be done weekly by a small group, often a PMO lead or a cross-functional panel, to maintain speed and avoid bottlenecks forming in the intake process.

Step 3: Score and Compare

For requests that pass triage, apply the scoring model in a structured and collaborative way. The purpose is not to produce a perfect number but to create a fair comparison between competing initiatives. When done properly, scoring replaces subjective debate with structured discussion grounded in agreed criteria.

Step 4: Make Decisions and Communicate Them

A prioritisation system fails completely if decisions are not clearly communicated back to stakeholders. Every request must reach a defined outcome so that expectations are managed, and teams understand where they stand within the broader portfolio of work.

Approved: Moved into the delivery pipeline with an owner and a start window
Parked: Valuable, but deferred due to capacity or sequencing constraints
Declined: Not aligned to strategy or not justified by expected value
Needs More Information: Requestor must clarify missing or unclear details

Clear communication of both the decision and the reasoning behind it is critical. This is where trust in the system is either built or lost.

A Simple Scoring Model That Works Across Project Types

A good scoring model balances value, urgency, and delivery complexity without becoming overly complicated. The goal is practicality, not perfection. The approach below can be implemented quickly and adapted over time as the organisation matures its prioritisation process.

Part 1: Value Score (0 to 20)

Score each value category from 0 to 5, then total them to get an overall value score. Keep categories consistent across the organisation to ensure comparability. This creates a shared language for defining what “valuable work” actually means.

Strategic Alignment (0 to 5): How strongly does this support current objectives?
Customer Impact (0 to 5): Does it protect revenue, improve satisfaction, reduce churn, or improve delivery?
Cost or Efficiency Impact (0 to 5): Will it reduce cost, increase throughput, or improve productivity?
Risk Reduction and Compliance (0 to 5): Does it reduce operational risk, security exposure, or regulatory risk?

You can adjust categories based on your environment, but avoid adding too many. More categories increase complexity without improving decision quality in most cases.

Part 2: Urgency Score (0 to 10)

Urgency is often misused, so it must be clearly defined and consistently applied. Without structure, everything becomes urgent, and the scoring loses meaning. Focus on measurable factors rather than emotional pressure from stakeholders.

Time Criticality (0 to 5): Is there a hard deadline, and what happens if it is missed?
Opportunity Window (0 to 5): Does value depend on a specific timing, such as a market window or operational access?

Encourage requestors to clearly explain the consequences of delay. If the impact of delay is unclear or minimal, the urgency score should remain low to preserve the integrity of the model.

Part 3: Effort and Complexity Adjustment (0 to -10)

Two projects can deliver similar value but carry very different levels of delivery risk. Instead of building a complex scoring system, apply a simple negative adjustment based on complexity. This keeps the model usable while still accounting for execution challenges.

Low Complexity: 0 adjustment
Medium Complexity: Subtract 3
High Complexity: Subtract 7
Very High Complexity: Subtract 10

Complexity should consider factors such as cross-functional coordination, dependency on external vendors, technical uncertainty, and the scale of organisational change required.

Final Score

Final score = Value (0 to 20) + Urgency (0 to 10) + Complexity adjustment (0 to -10). The maximum possible score is 30, and the minimum is 0. This provides a simple range that is easy to understand and communicate across teams and leadership.

The score itself is not the final decision. It is a tool that supports comparison and structured discussion. Leadership still applies judgment, but decisions become easier to justify, defend, and explain when backed by a consistent scoring framework.

How to Prevent the Scoring Model from Being Gamed

If the scoring model turns into a competition where teams try to inflate their numbers, it loses credibility and usefulness. Maintaining discipline around how scores are applied is essential to keeping the system effective over time.

Use Calibration Sessions

Run a short monthly session where a sample of scored requests is reviewed collectively. The goal is to align on what each score actually represents in practice. Over time, this builds consistency and reduces variation between different evaluators.

Require Evidence for High Scores

High-impact claims should be supported by a clear rationale. This does not require detailed financial modelling, but it does require logical justification. Asking for evidence discourages exaggeration and ensures that scoring remains grounded in reality rather than optimism.

Separate Urgency From Importance

Many requests appear urgent simply because they were started late or poorly planned. That does not make them strategically important. Keeping urgency and value as separate dimensions prevents the system from being dominated by short-term pressure.

Where Capacity Fits in Prioritisation

Even the most well-designed scoring model will fail if capacity is ignored. Portfolio overload is one of the main reasons organisations struggle to deliver. When too many projects run simultaneously, throughput drops and quality suffers due to fragmented attention and competing demands.

A simple capacity check can be implemented without advanced tools. For each key function or role, track:

How many active projects they’re currently supporting
The next 4 to 8 weeks of expected workload peaks
Any critical dependencies where one individual becomes a bottleneck

Then apply a strict rule: if a critical role is already overloaded, new projects can only begin by pausing or stopping another initiative. This single constraint often has a bigger impact than refining scoring models further.

Turning Intake Into a Repeatable Delivery Pipeline

Once intake and prioritisation are stable, the next step is ensuring that approved work transitions smoothly into execution. Many organisations fail at this stage, where approved projects sit idle without ownership or clear direction.

Assigning an owner and sponsor immediately
Setting a realistic start window instead of defaulting to immediate execution
Creating a one-page charter before major work begins
Agreeing on reporting cadence and milestones early

This structure ensures that approved initiatives do not drift and that delivery begins with clarity, accountability, and alignment from the outset.

How to Make This Easier on Microsoft 365

Many teams use Microsoft 365 to collaborate on requests, documents, and updates. The key is to avoid fragmenting intake across emails and spreadsheets. A structured approach usually includes a standard intake form, consistent fields for scoring, and a portfolio view that supports regular decision-making.

Some organisations choose to support this with a PPM platform that integrates into the Microsoft ecosystem. For example, a tool such as BrightWork PPM for MS 365 can be used as one option for managing intake, standardising templates, and creating portfolio visibility in a way that reduces manual consolidation.

A Practical Rollout Plan

If you want to implement this quickly, focus on execution rather than over-designing the system. A phased approach allows you to test, adjust, and build trust without slowing the organisation down.

Week 1: Define scoring categories, align on criteria, and create a simple intake form
Week 2: Pilot the process with a small number of requests and run a calibration session
Week 3: Hold the first prioritisation meeting using the scored backlog
Week 4: Communicate decisions, refine the model, and begin basic capacity tracking

The real success factor is not the scoring formula. It is consistency and discipline in applying the model and communicating decisions clearly. Get that right, and the entire portfolio becomes easier to manage and deliver.