Stakeholder requirements: align reporting needs with DD needs

Description

Bring key stakeholders in (including Rob) to confirm reporting requirements and ensure Compass replaces supplementary reporting with a single version of truth.

User story

As the product team, we want to validate reporting requirements with key stakeholders, so we build the right views and reduce duplicate reporting elsewhere.

Acceptance criteria

• Sessions held with:
  • Rob R (DD)
  • Divisional reporting users (pilot: at least 1–2 divisions)
• Documented outputs:
  • Top reporting questions to answer
  • Required fields for export/reporting
  • Required breakdowns (division/directorate/portfolio/delivery type)
  • External reporting constraints (format, frequency, redactions)
• Decisions logged:
  • Which reports are MVP vs later
  • Access model preference (Issue 2 Option A vs B)

Tasks

• Identify attendees and schedule sessions.
• Prepare structured question set + example report mock-ups.
• Document findings and convert deltas into backlog items.

Start with the stakeholder list and acceptance criteria in this issue, then prepare the question set and example report mock-ups for the requested sessions. Done means sessions are held, reporting needs and constraints are documented, MVP and access-model decisions are logged, and resulting deltas become backlog items.