↑↓ to moveEnter to openAll results →

    See overload in the month it happens, not in an annual average

    Capacity is modelled per person per month against the demand every project places on each role, so a single key person on three critical paths is visible before a date slips because of them.

    People capacity heatmap: load per team per month
    People capacity. Average load by team, month by month.

    What usually goes wrong

    And what changes when it runs on one model.

    01

    Capacity is an annual number

    A team at 80% a year can be at 160% in March.

    02

    Key people are invisible

    One architect on three critical paths is a risk nobody tracks.

    03

    Demand is never written down

    Projects ask for people in meetings, not in the plan.

    04

    Gaps surface as slips

    The first sign of a missing role is a missed date.

    Which roles each project still needs

    Every project shows the roles it needs, the people assigned and how short it is at its worst week.

    • Needed against assigned, by role
    • The worst week named
    • People shared with other projects shown
    Staffing coverage for a project with roles needed against assigned and the worst week
    Staffing coverage. How short a project is, and when.

    What a delay does to people

    When a date moves, the engine extends the assignments that depend on it, so the knock-on effect on people is part of the answer.

    • Assignments extended by the delay
    • Named people affected
    • Before anyone commits to the change
    Delay simulator with the resource impact on two people
    Resource impact. Who a delay affects, and for how long.

    What you get

    Every item runs on the same engines the screens use.

    Heatmap

    Load per team, role or stream, month by month.

    Demand

    Role demand per project, proposed and approved.

    Key-person risk

    Single points of failure on the critical path named.

    Cost to fill

    Each gap priced from the role model.

    Assignments

    People on activities, with their share of time.

    Windows

    Six months to three years, or a custom range.

    Polaris in people and capacity

    The advisors and agents that work in this part of the platform. All agents

    People advisor

    Advises

    Capacity gaps, overloaded people and key-person risk on the critical path.

    Reads
    Assignments, demand, capacity
    Produces
    Hiring and reallocation moves

    Demand proposer

    Proposes

    Proposes the roles and effort a project will need from its plan.

    Reads
    The project plan
    Produces
    Role demand to approve

    Questions

    Do we need timesheets for this?

    No. Capacity comes from assignments and role demand on the plan. Actual time can be added if you track it.

    Can project managers request people?

    Yes. Demand is proposed per project and approved before it counts against capacity.

    See it on your own programme.

    Send us a slice of your portfolio and we load it before the session, from strategy down to task.