↑↓ to moveEnter to openAll results →

    Know whether a funded project delivered the value it promised

    Each project carries a benefits register beside its schedule and budget, with a target, a realised value and the KPI that evidences each benefit. Realised values can be accepted period by period through a review, and revenue and EBITDA roll up from project to programme against target.

    Value created over time and the EBITDA bridge from each pillar to current EBITDA
    Value bridge. Cumulative value captured, and how each line builds to current EBITDA.

    What usually goes wrong

    And what changes when it runs on one model.

    01

    Benefits are promised once

    The business case states the value at approval and nobody opens it again.

    02

    Delivery is counted as success

    The project closes on time and on budget, and the benefit is assumed.

    03

    The team has gone

    By the time the value should appear, the people who promised it have moved on.

    04

    Realised value is self-reported

    The number comes from the project that needs it to look good.

    A benefits register on every project

    Each benefit has a type, a target, a realised value, a unit and a target date, and can be linked to the KPI that evidences it. Benefits listed on an approved project charter arrive in the register with the charter recorded as their source.

    • Six types, from commercial to risk reduction
    • Linked KPI from the project or the programme
    • Register total compared with the target uplift
    Benefits register with three benefits, each showing its type, target, realised value, target date, linked KPI and source
    Benefits register. Every project lists the benefits it promised, with a target, what has been realised so far and the KPI that measures it.

    Realised values accepted, period by period

    A review form can record the reviewed benefit values as accepted observations for a reporting period. When the form goes for approval, nothing is recorded until the final approver clears it.

    • One accepted value per benefit and period
    • A later review supersedes; the earlier one is kept
    • Period or cumulative basis stated on each value
    Approvals queue: items waiting, each with its approval steps and Approve or Reject
    Approvals. Everything waiting on a person, with its approval path.

    Benefits checked again when the project closes

    The built-in closure form asks for the outcome, the lessons and the benefits realised against target, and the realised values are written to the register when the project closes. Closure can also require its own forms, handover activities and an approval.

    • Realised against target, benefit by benefit
    • Lessons added to the programme's lessons registry
    • A standalone benefits review form, kept as a record
    A department portfolio page with projects, progress, budget, status and lifecycle
    Department portfolio. Projects by status and by lifecycle stage, closure included.

    Value against target, from project to programme

    Each project carries a target revenue uplift and the revenue captured so far, with EBITDA as revenue less the project's total cost. The value view rolls these up by initiative and pillar, with enabler pillars shown as cost.

    • Target and actual revenue and EBITDA
    • Share of target captured at each level
    • Cumulative value captured, quarter by quarter
    Pillar EBITDA target against actual
    Value creation. EBITDA target against actual by pillar.

    What you get

    Every item runs on the same engines the screens use.

    Benefits register

    Type, target, realised value, unit and target date for every benefit.

    KPI link

    A benefit points at the KPI that evidences it, with that KPI's own readings.

    Accepted observations

    Reviewed values recorded per period, with the history of what was accepted.

    Protected history

    A benefit with accepted observations cannot be deleted from the register.

    Value roll-up

    Revenue and EBITDA against target by project, initiative and pillar.

    Financial access

    The register is shown only to people with financial access to the project.

    Questions

    Who decides that a benefit has been realised?

    A reviewer records the values on a review form. When that form is routed for approval, the values are accepted only when the final approver clears it, and the person who raised the request can never decide it.

    Does a benefit have to be financial?

    No. Each benefit carries its own unit, so it can be an amount of money, a percentage or another measure. The six types are commercial, operational, strategic, compliance, customer and risk reduction.

    What happens to benefits when the project closes?

    The closure form records the benefits realised against target, and those values are written to the register. A standalone benefits review form records planned against realised for a review period.

    Can an accepted value be corrected?

    Yes, through a correction or a later review of the same period. The earlier value stays in the history, marked as withdrawn or superseded, with the later one marked current.

    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.