Example Ops Dashboard

Workflow

1. Identify the operator role, the key decisions they need to make, and the time window.
2. Build a single-file HTML artifact with a persistent navigation rail, KPI row, primary chart area, and action table.
3. Use real-looking labels and numbers instead of placeholders.
4. Check that the layout works at laptop width and that tables remain readable.
5. Return index.html as the primary artifact.

Quality Checks

• The dashboard is useful for scanning and repeated work.
• The main action table has status, owner, priority, and next step columns.
• Text stays inside compact controls and cards.
• No external network assets are required.