The question: What minimum shared information lets operations, finance and suppliers coordinate without flooding the team?
Start with five shared records: safety sign-off, launch gate, equipment delivery, budget decision and grant evidence. Protect the first four; use one optional place for the highest-ranked remaining dependency. Share changes and decisions at the interfaces, with linked detail kept in the owning team's records.
This is a proposed information design for the fictional 12-week, £240,000 two-hub launch. Five is an authored attention budget, not a measured optimum. The fixtures supply priorities and dependencies; they do not supply current progress, owners, deadlines, evidence files or approved authority limits.
Fictional what-if workspace. Changes stay in this tab and reset on reload; no record is saved and no external system is changed.
The minimum information contract
One brief entry per dependency
Use the same six fields across operations and finance. Give suppliers the delivery and acceptance fields needed for their own interface, with internal finance detail restricted. Every entry has one accountable owner and links back to its source; it is not a second set of operational books.
1 · Outcome and scope
Stable record name; North, South or both hubs; the outcome at risk.
2 · Accountable owner
One named internal owner, plus the counterpart who must respond. Roles below are proposals; no person has accepted them.
3 · Status and time
Ready / at risk / blocked / unknown; agreed date, latest forecast, last verified time and next update. Missing information stays unknown.
4 · Dependency
What is needed from whom, and what cannot proceed without it.
5 · Decision and authority
Next action or decision, decision deadline, accountable authority and any spend limit. A recorded request is not approval.
6 · Evidence link
Receipt, delivery confirmation or assurance evidence, with source and version. A green label alone is not proof.
Proposed cadence: owners update changed forecasts before a 10-minute daily launch check; unchanged detail stays quiet. Urgent safety, launch-date, spend-authority or evidence-deadline exceptions go directly to the affected owner and counterpart. Review routine items in a weekly digest. These timings are assumptions to test with the team.
1 · Bound the shared view
Choose what earns a place
Protect four interface records: safety sign-off, launch gate, equipment delivery and budget decision. This is an authored dependency rule, not a property of the supplied scores.
Rank remaining records by the supplied priority score. Fill the remaining places from highest to lowest. A tie uses original fixture order. Scores are ordinal selection aids, not money, risk probabilities or benefits.
Override visibly: reserve one optional place for your chosen record, then fill the rest by rank. The preview names the displaced record. An override cannot remove a protected record.
Keep an exception route outside the cap. Displacement removes routine board attention, not accountability, source records or safety gates.
selected = 4 protected records + optional places
optional places = capacity − 4
optional selection = chosen override (if any) + highest scores that still fit
5 of 8records in the shared view
3remain with their owning teams
4protected interface records
Shared view
Priority bars show supplied scores on a 0–18 display scale. Every operational status is unknown; selection is not readiness.
Displaced from routine attention
Standing assurance boundary
The fixture says the pilot must wait for the assurance owner. Board capacity, ranking and overrides cannot approve safety or release the launch. Each hub still needs evidence of its own readiness.
2 · Keep the difficult interfaces visible
Two cross-function conflicts
These are inferred coordination risks from the supplied dependencies, not evidence that the fictional teams are already in dispute. They remain visible even when an associated optional record is displaced.
Operations + suppliers ↔ finance
Recover delivery, or preserve spend authority?
An equipment delay can shift training and bookings. Expediting may change spend authority, so an operational need is not permission to order.
Minimum shared resolution: supplier-confirmed forecast and recovery options → operations' impact on training and bookings → additional cost and budget authority decision → recorded commitment only after authorisation.
Proposed accountable roles: delivery owner and finance authority. Amounts, named owners, limits and due dates are not supplied. Sources: Equipment delivery [R2]; Budget decision [R4].
Finance ↔ operations
Evidence completeness, or time spent delivering?
Finance needs receipts from operations. Without an agreed handoff, operational completion can still leave grant evidence incomplete; repeated chasing adds noise.
Minimum shared resolution: finance specifies required receipt and deadline → operations links the source once → finance acknowledges acceptance or identifies a precise gap. Keep only the gap and next handoff on the board.
Proposed accountable roles: evidence owner and operational receipt custodian. Grant rules, deadlines and any funding consequence are unknown; no loss of funding is inferred. Source: Grant evidence [R5].
3 · Test whether a change deserves attention
Simulate the next handoff
Choose an authored test event. A consequential dependency change reaches the affected functions even if its record is displaced. Routine detail stays with its owner even when the board has room for it.
Simulation receipt
Correction: change the event or note and simulate again. Clearing or resetting removes this result. Refreshing the page restores the default workspace. No notification, approval, booking, purchase or source-record update occurs.
Routing and disclosure rules
Dependency, authority or required-evidence change: send one concise handoff to the accountable owner and affected counterpart. Avoid broadcast updates to all six staff.
A displaced record can still raise a material exception. The view cap limits routine attention; it is not a filter on critical information.
Routine change with no dependency impact: keep it in the owner's digest. Selection alone never makes it an alert.
Supplier-facing information: delivery specification, relevant hub, agreed and forecast date, acceptance criteria, named contact and authorised order/change reference. Finance's internal budget discussion, grant receipts and other suppliers' detail remain internal.
This page demonstrates proposed routing, not real access control or a connection to any system. Actual recipients and permissions must be agreed before use.
Evidence, limits and acceptance
Eight fixtures, no invented progress
Source: benchmark v1.0.0, question 04, taskFixtures.sharedRecords. The table preserves all supplied records and scores. References R1–R8 are local row identifiers, not external evidence links.
Complete source fixture
Ref
Record
Function
Score
Dependency context · verbatim
Interpretation: supplier coordination is represented through Equipment delivery and Budget decision. There is no supplier-owned row in the fixture; adding a new supplier score or pretending to know a supplier commitment would exceed the evidence. Safety is labelled operations in the source, so it is not used as a second invented cross-function dispute.
Limits: an ordinal score cannot demonstrate that this is the optimal set. The four protected records, five-record default, role suggestions, routing examples and cadence are authored design choices. There are no observed update volumes, stale-data measurements, permissions, response times or before/after performance results. Keeping all eight may be reasonable if measured coordination needs justify it.
Observed author checks: 80 local DOM assertions passed, including all 21 valid capacity/override combinations, invalid-input rejection, displaced-record exception routing, routine artwork filtering, plain-text rendering of an HTML-like note, reset and fresh-load defaults. These checks do not establish visual quality, assistive-technology usability or operational benefit; browser QA is handled separately by the coordinating agent.
Acceptance: selection rules and displaced records. The visible rules, complete source table, applied-view summary and displaced list explain every inclusion and exclusion. Override comparison is against the same-capacity automatic selection.
Acceptance: visible override and two conflicts. The override remains beside the capacity control; the delivery/spend and receipts/delivery conflicts remain on the page in every simulated view.
Try the checks: at capacity 5, force Demand survey to displace Grant evidence. At capacity 4, a forced optional record is rejected without replacing the last valid view. A missing-receipt event still routes to finance and operations when Grant evidence is displaced. At capacity 8, artwork still stays in the routine digest.