TPRS

TPRS
Live demoReportsDownloadsProduct briefHow it worksWhy TPRS
Transition & Transformation Program Reporting Suite

Every program. One source of truth. Answered in five seconds.

PMs update one spreadsheet per project. TPRS calculates health, rolls it up, and publishes a customer-safe, executive-grade report — with a dimension radar, a workstream×dimension matrix, drill-downs, trends, and a named-authorizer gate. No manual dashboards.

▶ View the live demoRead the product briefDownload examples

● Live demo · read onlyTPRS customer dashboard overview

1
spreadsheet per project
0
manual dashboards
3
drill-down levels
100%
self-contained — opens offline

See the reports

Real output from the current engine — not mock-ups. Open the live, read-only demo to click through the tabs, the role switcher, the dimension radar and the Portfolio drill-down, or download the files below.

▶ Open live demoCustomer dashboard — OverviewThe five-second answer: status, trend, a “what changed since last period” strip, the health radar, the workstream×dimension matrix, and the decisions needed. Click to open the live, read-only dashboard.
Customer overview

Plan on a pageEvery milestone on one timeline, grouped by workstream, coloured by status, with critical gates and the current period marked.
Roadmap / plan on a page
Risks — heat map + burndownThe P×I heat map as an entry point, paired with a risk burndown and the full register for prioritisation.
Risk heat map and burndown
Portfolio drill-downProgram → Workstream → Project → milestones, risks, KPIs in context; search, filter and group by status or phase.
Portfolio drill-down
Internal viewDelivery & governance, the budget→EAC waterfall, and the Data Quality tab the customer never sees.
Internal overview

How it works

One spreadsheet per project per period goes in; a customer-safe web report and a PowerPoint come out — and nothing reaches the customer until a named authorizer approves exactly what will publish.

PM fills one .xlsx→
submit to intake→
validate & score→
roll up→
authorizer approves→
publish report + deck
Who does what
Project manager

Reports the facts

Each period, fills one standard .xlsx for their project — status, % complete, milestones, risks & issues, decisions, KPIs (and internal cost/resource if used). No slides, no formatting, no manual roll-up.

PMO / data steward

Runs the intake

Owns the template and the intake location, chases missing submissions, and reopens a period for corrections. Sees a Data-Quality view of what is in, missing or quarantined, and PM-vs-calculated status.

CPM / authorizer

Approves what ships

Previews the exact customer report that would publish, may override a status with a recorded rationale, then approves. This is the single gate before anything becomes customer-visible.

Customer & executives

Read & decide

Open the live, customer-safe report (or the deck) — status, trend, what changed, roadmap, risks and the decisions needed — filtered to their role. Internal-only detail never appears.

How the data gets in, and what comes out
1
Fill the template

Start from the current PM template in the program’s 10_Templates folder (or last period’s accepted workbook). Dropdowns and a built-in Validation tab catch most errors before you submit; a command-line pre-check (validate-file) catches the rest. For a test environment, the seed-demo generator populates a whole instance with realistic synthetic data.
2
Submit to intake

Drop the .xlsx into 01_Intake — a file-system share (self-hosted) or a SharePoint library (Kyndryl Bridge). Customers can submit their own items (dependencies, SLAs, risks) through a separate customer-items template into 02_Customer_Intake.
3
Validate & calculate

On its next scan (scheduled, or run on demand) the engine validates every workbook, accepts clean ones and quarantines the rest with a plain-English error report, then scores BRAG health across Schedule, Delivery, Risk, Readiness and Financial and rolls it up to workstream and program.
4
Authorize

The CPM/authorizer previews exactly what would publish and approves. Only approved material becomes customer-visible; a correction re-opens the period and re-runs the gate.
5
Publish & export

TPRS publishes a self-contained web report and a PowerPoint deck (customer and internal), and writes curated datasets. Export any report to PDF from the browser, download the deck, or pull the CSV datasets into Power BI / Excel.
Imports, exports & flexibility

Imports (in)

  • PM status .xlsx — one per project, per period (the only required input)
  • Customer-items .xlsx — customer-owned dependencies, SLAs and risks
  • Program_Config.xlsx — workstreams, projects, approvers, weights, thresholds and branding
  • seed-demo generator — synthetic data to stand up a test instance

Exports (out)

  • Customer & internal web reports — one self-contained HTML file each, opens offline
  • PowerPoint decks — customer and internal
  • PDF — print/export any report from the browser
  • Datasets (CSV) — facts ready for Power BI / Excel

Flexibility

  • Two deployment models — self-hosted VM + file share, or Kyndryl Bridge + SharePoint
  • Role lenses — Board/CEO, CFO, CIO/Delivery, CTO/Risk from one dataset
  • CPM overrides — adjust a status with a recorded rationale
  • Branding & layout — colours, logo and dashboard sections are configurable and upgrade-safe
  • Scheduled or on-demand — run on a timer, or trigger a run when you need it

Why TPRS

5s

Answers first

Overview leads with status, trend, a dimension radar and the decisions needed — then detail on demand.

⇲

Drill-down, 3 levels

Program → Workstream → Project → its milestones, risks and KPIs, in context.

◐

A view per role

Executive, Delivery, Risk, Financial — one dataset, the right first screen.

🔒

Customer-safe

Internal detail can never reach a customer view — enforced in data, proven by audit.

✓

Authorized

A named CPM previews exactly what would publish, then approves.

▲

Proven

Full automated suite; leak-scan clean; validated on Python 3.11 / 3.13 / 3.14.

TPRS — Transition & Transformation Program Reporting Suite · v2.2.2 · This portal and its examples use synthetic demonstration data; no real customer data is shown.