Macro internal · TRB

Improvement opportunities — priority ranking

64 TRB references, 38 live items. Rate each for priority and impact — your ratings set the order we scope them in.
Why you're rating. These ratings decide which opportunities go forward first to a detailed scope of work. They set scoping order — they don't commit budget or delivery.
Sanitised list · Estimates are pre-scoping approximations
Opportunities Roadmap Build order The method Foundation programme Where requests went Foundation map Silos Wiki Library Add suggestion
Rating as · change ·
TRB · Macro internal

Improvement opportunities — priority ranking

Macro internal · TRB register · 38 live items
Ordered by Macro's impact assessment (Compliance 35% · Financial 25% · Client 20% · Strategic 15% · Colleague QoL 5%). Sort or filter by any dimension. Open a row for the full discovery record and to change a rating. Team is the in-app view — rate priority and impact 1–5 with the dots.
What this list is The TRB register (28 Aug) with Macro's portfolio impact assessment. Ordering follows Macro's weighted score; the in-app team rating sits alongside it as the people's view. Foundation counts the data an item needs to already exist against the foundation it builds — an item needing four things and building one depends on data nobody has created yet. Hover either number to see which entities. Refs are Macro's TRB numbers, so gaps and exclusions are theirs. Effort and beta estimates, where present, size a first working slice in a multinational — not a company-wide rollout.
0 shown 0 raters
TRB Opportunity Group Score Band £/yr Foundation Effort Team

Saved.
MACRO DATA SPINE · DEV AREA

Library

Foundation map
Everything the improvement programme reads from or produces — data sets, reports, scorecards, pricing, integration flows. Have = exists and we can reach it · Mock = built by us on illustrative data · Hunting = known to exist, source being chased · Missing = nobody has it yet. Amber cells are the unknowns; everything saves automatically.
Who Client→Contract
SupplierPerson
Surrey Council = Client · the engagement = Contract
Where — strict hierarchy Site→Building→Floor→Room
One UUID each · aliases map every source name
Things AssetMeter
Asset = credentials custody, SFG20 cadence, statutory duties · Meter = MPAN / MPRN / SPID
What happens ProjectWork OrderTask
Mobilisation = a Project type · start / delivery / completed dates
Evidence DocumentRules
RAMS = Document type, expires · Rules = checklists & KPI definitions
Type Dataset Report Scorecard Pricing Flow
Status Have Mock Hunting Missing
Clear filters
TypeNameEntitiesNeeded byStatus Lives in today (system)FormatOwnerUpdate rhythm Canonical? (yes / name the master)Sample

Progress

Team suggestions

Raised through "Add suggestion" — awaiting review, not yet in the rated list above.

Add a suggestion

Spotted an opportunity that isn't on the list? Describe it here — it goes into the review pile for the next TRB pass.
Thank you — suggestion added.
Sanitised list — system names generalised · Priority here means scoping order, not commitment ·