What's live and what's coming

• Org-scoped multi-tenancy with five role tiers — Owner/Admin, Contributor, Specialist, Limited, External/Portal
• Invite flow via email, accepted through Supabase Auth
• Temporary delegation of Owner/Admin approval authority to a Contributor for a defined window

• Client, Order/Quote Line Item, Delivery Type, Project Overview, Programme
• Deliverable, WBS & Project Plan, Change Log, Change Request/CAB workflow
• RAID Log, RACI Matrix (scales from minimal-default to full multi-role by project complexity)
• SLA/OLA Tracker — Initiation SLA, Vendor SLA, Project Delivery SLA, and internal OLAs, tracked distinctly
• Escalation Matrix — Strategic client flag plus dynamic status-based triggers
• Budget Tracker, Lessons Learnt, Stakeholder Register, Communication Plan

• Project-level RAG rollup — timeline, budget, scope, risk, client satisfaction, resources
• PM-level portfolio rollup — strictly own-portfolio for a PM, full comparative view for Owner/Admin
• Company-wide dashboard — org-wide RAG tallies, Owner/Admin only
• Project Governance Report by PM — RAID log maintenance, RACI completeness, SLA/OLA compliance, escalation handling, WBS adherence, budget adherence, client communication cadence

• High-impact RAID item open beyond 5 business days
• SLA/OLA due-date reminder (3 days out) and immediate breach alert
• Order unlinked to a project beyond 2 business days
• As-sold rollup diverging from the signed quote total
• Weekly reminder to each PM to update their tracker
• Automatic PIR/client-rating request the moment a project closes

• One-click weekly status email — RAID, RACI, recent changes, SLA status, delivery-vs-plan
• Full send audit trail, feeding the client-communication-cadence governance metric

The internal reporting mechanism is settled — plain CSV, not a formatted multi-tab workbook.

• CSV export on dashboards and reports
• Filtered exports matching whatever view you're currently looking at

Advisory load visibility at assignment time — the PMO Manager still makes the actual call, this just makes overload visible before it happens.

• PMO-Manager-configured capacity fields — Standard-project max and Complex-project max, combined per PM
• Load surfaced at assignment time, not enforced automatically
• Feeds the Resources dimension of the RAG rollup

For multi-site and multi-deliverable projects — tracked independently of Standard/Complex classification.

• Configurable bucket pipeline (site survey, landlord approval, customer readiness, build, activation)
• Per-bucket OLA with dwell-time alerting when a site sits in a bucket too long
• Ops/exec rollup of site counts across every active multi-site project

• Vendor, technology type, PO sent date, expected and actual handover date
• Vendor SLA scorecards per vendor and per technology type
• Delay fault attribution — vendor-caused, client-caused, or internal-caused

• A dedicated commercial-dependency log, separate from the delivery RAID log
• Deliverable Builder generating deliverables directly from quote line items
• Two-directional quote/deliverable vetting — scope creep and missed scope, both flagged automatically

A maintained database of site and contractual constraints, checked before an undeliverable solution is ever sold.

• Constraint categories modelled as configurable data — mall exclusivity, single-trench policy, and more
• Checked at two touchpoints — order/brief capture, and internal scoping once site specifics are known
• Future link forward from the Lessons Learnt repository, surfacing prior site/vendor history automatically

The same governance engine, reconfigured for other delivery-constraint industries — once the telecom beachhead is proven.

• Gate names, constraint categories, and RACI role labels as configuration, not hard-coded logic
• Construction, managed IT services, event production, and similar delivery-constraint businesses