# Internal dashboard requirements worksheet

By Ajju Iglesias. Use fictional or appropriately authorised sample data. Do not include credentials or customer secrets.

## Decision
- Primary user and responsibility:
- Recurring decision and time of use:
- Expected action after reviewing the screen:
- Existing report or saved view evaluated:
- Why a custom view may be necessary:

## Metric definition (repeat for each metric)
- Label and business meaning:
- Record identity / unit counted:
- Included and excluded statuses:
- Date field, time boundary and timezone:
- Active filters:
- Treatment of duplicates and missing fields:
- Source and definition owner:
- Detail records expected to reconcile to this metric:

## Data and state
- Source system and refresh method:
- Acceptable delay for this decision:
- Last-successful-refresh display:
- Stale-data behaviour:
- Empty state vs source unavailable vs incomplete data:
- Recovery owner and contact path:

## Access and actions
- Overview scope for each role:
- Record detail and export permissions:
- Allowed write actions and authoritative destination:
- Concurrent-change handling and confirmation:
- Keyboard use, text alternatives and target devices:

## Sample fixture
Companion file: internal-dashboard-sample.csv
Fictional snapshot: 19 October 2026, 12:00 IST.
Open statuses: new, contacted, qualified.
Due now: open AND next_action_at is present AND next_action_at <= snapshot.
Expected: open 5; due now 4; unassigned due now 1.
Due IDs: R01, R02, R03, R04.
Due ownership: Mira 2; Noor 1; unassigned 1.
Mira filter: R01 and R02, due count 2.
R05 is closed. R06 is due later. These are illustrative requirements, not production results.

## Acceptance evidence
For each case record input, expected result, observed result and evidence location:
- Default totals and matching detail IDs.
- Exact time boundary and user timezone.
- Filter consistency across overview and detail.
- Closed record with an old due timestamp.
- Open record missing a due timestamp.
- Source failure vs empty result.
- Unauthorised details and export requests.
- Concurrent modification before a write action.
- User completes the task with keyboard and intended device.

## Delivery
- First-release scope and deferred features:
- Definition, source and support owners:
- Unresolved questions:
- Review trigger when business rules change: