↑↓ to moveEnter to openAll results →

    Own the number, and be able to defend it every month

    The transformation office reports a number it did not produce, from teams that do not live in its tool. Lodestar computes status from dates and approved evidence, scores how far each report can be trusted, and lets workstream leads update the plan by replying to an email.

    Delivery signals: each project on schedule, on budget and on scope, beside a summary of risks, actions, issues and decisions
    Delivery signals. Schedule, budget and scope for every project, with the RAID summary beside it.

    How it works

    For the transformation office that owns the number and has to report it every month.

    Green has to be earned

    Status comes from dates, approvals and evidence. A workstream cannot type itself green, and a green that runs ahead of its evidence is flagged.

    • Ten typed detectors: stagnation, burn mismatch, ghost projects, ignored risks
    • A data-trust score per project, computed the same way every time
    • Evidence cadence enforced for every KPI and every gate
    Progress proof: activities approved, pending, rejected and missing evidence
    Progress proof. Which completions are backed by approved evidence, and which are not.

    No re-entry for the plan to move

    A workstream lead sends the update they already write, as a PDF, Word, Excel or PowerPoint file or as plain text. The agent extracts the changes and a person approves them, with the same permissions and audit as the manual route.

    • Progress, dates, risks and resource gaps extracted from the document
    • Every change reviewed by a person before it lands
    • An audit entry for every applied change
    Approvals queue: items waiting, escalated and overdue, each with its approval steps
    Approvals. Everything waiting on a person, in one queue, with its approval path.

    The monthly pack stops being a project

    One calculation feeds every forum and every format, so the executive deck, the board pack and the live dashboard cannot disagree.

    • PDF, PowerPoint, Word and dashboards from the same model
    • Decisions taken in the forum link back to the plan item they move
    • Overdue actions chased and escalated automatically
    Executive PMO dashboard: projects by status, budget utilisation and status radar
    Executive dashboard. The same numbers the board pack is built from.

    The transformation office toolkit

    Every item below runs on the same engines the screens use, so the numbers never diverge.

    Computed status

    RAG derived from dates, approvals and evidence, never typed by hand.

    Data-trust scoring

    Exposes projects that are green on the outside and red on the inside.

    Update extraction

    Agents turn the update document into plan changes, for a person to approve.

    Predictive delay

    Finish dates projected from the performance trend, weeks before the miss.

    Report Studio

    Board, steering and executive packs in four formats from one calculation.

    Audit trail

    Every applied change recorded with its approver.

    Runs on Evidence gatesData-trust scoringAnomaly engineUpdate extractionReport Studio

    A number the CFO can challenge and you can substantiate.

    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.