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.

A practical intake and prioritisation model does two things:

• It makes decisions visible – everyone can see why work is approved, delayed, or declined.
• It protects capacity – fewer projects run at once, which increases throughput and reduces firefighting.

This article outlines a lightweight project intake workflow and a simple scoring model you can implement quickly. It is designed for mixed portfolios where projects vary in size, urgency, and stakeholder pressure.

Why intake fails in real organisations

Intake processes fail for predictable reasons. If you recognise these patterns, you are not alone.

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. The “queue” becomes whoever has the loudest voice rather than the highest value.

Teams do not trust the system

If people feel the process is slow or opaque, they will bypass it. A good intake model is fast, transparent, and consistent.

Everything is urgent

When prioritisation criteria are unclear, every project is framed as a crisis. Without a shared scoring model, leaders are forced to decide based on narrative rather than evidence.

Capacity is invisible

Approving projects without considering who will deliver them creates a predictable outcome: everyone is busy, progress is slow, and deadlines slip.

The goal of prioritisation is not perfection

One of the biggest mistakes in prioritisation is aiming for perfect scoring. You do not need that. What you need is a repeatable way to compare initiatives and make trade-offs in a consistent manner.

A good scoring model achieves:

• Fairness – similar projects are treated similarly.
• Consistency – the same criteria are applied across departments.
• Speed – decisions can be made without weeks of debate.
• Transparency – teams understand why decisions were made.

A lightweight project intake workflow

You can implement a workable intake process using four simple steps. The key is to keep the entry requirements light, then increase detail only after a project is accepted into the delivery pipeline.

Step 1 – Submit a short request

A good intake form captures just enough information to evaluate value, urgency, and effort. Aim for one page. 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 or fill it with low-quality guesses.

Step 2 – Triage quickly

Not every request should go through full scoring. A quick triage step helps:

• route requests to the right owners
• merge duplicates
• reject items that are clearly out of scope
• identify “fast path” work that can be handled as 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 triage panel.

Step 3 – Score and compare

For requests that pass triage, apply the scoring model. Scoring should be done collaboratively so the output is trusted. The aim is not to game the score, but to establish a clear comparison.

Step 4 – Make decisions and communicate them

A prioritisation system fails if decisions are not clearly communicated. Every request should end with one of these outcomes:

• Approved – moved into the delivery pipeline with an owner and a start window
• Parked – valuable, but deferred due to capacity or sequencing
• Declined – not aligned to strategy or not justified by value
• Needs more information – requestor must clarify key details

Communicate decisions and the reason clearly. This is where trust is built.

A simple scoring model that works across project types

A good model balances value, urgency, and delivery complexity. Below is a practical approach that can be implemented in weeks, not months.

Part 1 – Value score (0 to 20)

Score each value category from 0 to 5, then total them. Keep the categories consistent across the organisation.

• 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 resist adding too many. Four categories is usually enough at the start.

Part 2 – Urgency score (0 to 10)

Urgency is often abused, so define it clearly. Score these:

• 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 people to be explicit about the consequence of delay. If the consequence is vague, the urgency score should be low.

Part 3 – Effort and complexity adjustment (0 to -10)

Two projects can have the same value but very different delivery risk. Instead of over-complicating the model, apply a simple adjustment that reflects complexity. For example:

• Low complexity – 0 adjustment
• Medium complexity – subtract 3
• High complexity – subtract 7
• Very high complexity – subtract 10

Complexity can be based on factors such as cross-functional dependencies, vendor reliance, technical uncertainty, or change management impact.

Final score

Final score = Value (0 to 20) + Urgency (0 to 10) + Complexity adjustment (0 to -10). The maximum is 30, and the minimum is 0.

The number is not a verdict. It is a comparison tool. Leadership still makes decisions, but now decisions are easier to explain and defend.

How to prevent the scoring model being gamed

If the scoring model becomes a competition, it loses value. These practices help maintain integrity.

Use calibration sessions

Run a short monthly session where you review a few scored requests and agree what a “5” really looks like for each category. Calibration improves consistency quickly.

Require evidence for high scores

If someone claims a major cost saving or risk reduction, ask for the basis. This does not need detailed financial modelling. It does require a clear rationale.

Separate urgency from importance

Many requests are urgent because they were started late. That does not automatically make them strategically important. Keep those categories separate to avoid constant emergency prioritisation.

Where capacity fits in prioritisation

Even the best scoring model fails if capacity is not considered. Portfolio overload is one of the biggest drivers of late delivery. If too many projects run at once, throughput decreases and quality drops.

A simple capacity check can be implemented without complex resource management systems. For each functional group or key role, track:

• how many active projects they are supporting
• the next 4 to 8 weeks of major workload peaks
• any single points of failure where one person is a bottleneck

Then add a rule: if a critical role is overloaded, new projects can only start by stopping or pausing another initiative. This single rule often improves delivery outcomes more than any scoring model.

Turning intake into a repeatable delivery pipeline

Once intake and prioritisation are working, the next step is to make the transition from “approved request” to “active project” consistent. That typically requires:

• assigning an owner and sponsor immediately
• setting a start window rather than an immediate start date
• creating a one-page charter before significant work begins
• agreeing reporting cadence and key milestones early

This reduces the common problem where projects are approved but float without ownership and structure.

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, here is a realistic approach:

• Week 1 – define categories, agree scoring criteria, and create a one-page intake form
• Week 2 – pilot triage and scoring with a small set of requests, run calibration session
• Week 3 – run the first prioritisation decision meeting using the scored list
• Week 4 – publish decisions, refine the model, and begin tracking capacity at a simple level

The main success factor is not the scoring arithmetic. It is the discipline of using the model consistently and communicating decisions clearly. If you do that, you will reduce overload, improve trust, and create a portfolio that is much easier to deliver.