Template: UI Screen Audit Sheet

1. Purpose

To provide a comprehensive, auditable record of every UI screen’s progress from draft → validation → approval → handoff, ensuring no gaps in design-to-dev delivery.


2. Workflow Integration

  • Step 1 – Designer Self-Check → Logs screen with ID + marks initial readiness.
  • Step 2 – Peer Review → Peer checks visual consistency, tokens, states.
  • Step 3 – Design Lead Approval → Validates against system + business goals.
  • Step 4 – Pre-Handoff QA → Confirms responsiveness + accessibility.
  • Step 5 – Final Approval & Lock → Marked “Ready for Dev” → linked to JIRA/ClickUp task.

3. Audit Criteria (per column)

Audit CategoryWhat to CheckFails If…
State VariantsDefault, Hover, Active, Disabled, Error, Success includedAny missing or undocumented
ResponsivenessDesktop, Tablet, Mobile covered with proper reflowMobile = “shrunk desktop” only
Consistency ReviewTokens, spacing, typography, grid alignment verifiedManual overrides, random hex codes, inconsistent padding
AccessibilityColor contrast, tap sizes, focus states representedContrast < AA, no keyboard states
Peer FeedbackPeer feedback cycle completed + documentedSkipped or unresolved comments
Final ApprovalDesign Lead reviewed + approvedLead skipped / no sign-off record

4. Table – UI Screen Audit

Screen IDScreen NamePlatformState VariantsResponsivenessConsistency ReviewAccessibilityPeer FeedbackLead ApprovalQA StatusDev Handoff LinkNotes
UI-01Landing PageWeb✅ Default, Hover, Error✅ Desktop/Mobile✅ Tokens + Spacing✅ Contrast AA✅ Done✅ Approved✅ PassedJIRA-123 / [Figma Link]CTA alignment corrected
UI-02Signup FormWeb + App✅ All states✅ All devices✅ Tokens OK⚠ Needs keyboard focus state✅ Peer CheckPendingPendingJIRA-124Missing focus state
UI-03Dashboard HomeDashboard✅ Empty, Loading, Success, Error, Permission✅ Desktop/Tablet/Mobile✅ Grid + spacing validated✅ Passed✅ Peer CheckPendingQA in-progressJIRA-125Needs performance consideration for 1000+ records

5. Failure Handling

  • If any audit item fails, screen moves back to Designer Self-Check stage.
  • Designer must resolve within 1 sprint → otherwise flagged as delivery risk.
  • Audit log tracks history → no silent “fix and move on.”

6. Usage Notes

  • Sheet updated in real time during design → audit process.
  • Final column must always link to JIRA/ClickUp task + Figma frame.
  • Weekly Design QA meeting → review all pending screens.
  • Monthly audit → % of screens passing first attempt vs needing rework.

Outcome: This sheet is no longer “tick-box” — it becomes a living audit + accountability tracker, integrated with sprint boards and dev handoff.