Skip to main content

Release Signoff Checklist

Approval before broader sharing

Use this page as a lightweight approval sheet before sharing a build broadly. It is meant to make release confidence explicit, not ceremonial.

Signoff rule

  • All Priority 0 items pass
  • No blocker bugs are open

Build information​

  • Version:
  • Build type: iOS TestFlight / Android APK / web / other
  • Date tested:
  • Tester:
  • Device / OS:
  • Account used:

Priority 0 checks​

Mobile access and capture

These checks confirm the core loop is at least functional enough to share safely.

  • [ ] app launches without crash
  • [ ] valid login works
  • [ ] Home, Capture, Context, Impact, and Profile open on mobile
  • [ ] text insight can be created and saved
  • [ ] offline insight can be created while disconnected
  • [ ] pending count increases while offline
  • [ ] pending item syncs after reconnecting
  • [ ] logout works
Admin verification

The release is not healthy if the admin side cannot validate or surface the captured data.

  • [ ] admin control plane login works
  • [ ] admin insights page loads and shows expected data

Priority 1 checks​

Mobile confidence checks

These are important quality checks that usually determine whether the build feels ready rather than merely functional.

  • [ ] onboarding works on a fresh install
  • [ ] voice capture works or fails gracefully into a recoverable draft
  • [ ] photo attachment works or fails without blocking save
  • [ ] event or session context can be selected and used during capture
  • [ ] insight detail and edit work
  • [ ] profile sync state is understandable
  • [ ] impact dashboard loads without obvious broken states
  • [ ] executive or admin-only visibility is correct for the tested role
  • [ ] app lock works if that area changed
Admin confidence checks

These protect the reporting and operational side of the platform before wider sharing.

  • [ ] admin dashboard loads without broken states
  • [ ] events page loads without broken states
  • [ ] settings page loads without broken states

Quick notes​

  • Known issues noticed:
  • Areas not tested:
  • Platform gaps not covered:
  • Role-based gaps not covered:

Final decision​

  • Approved to share broadly
  • Approved with known issues
  • Not approved

Reason:

Risk

If you find a problem during signoff

  • log it with `Bug Report Template`
  • review `Bug Reporting Guide` for evidence expectations
  • use `QA Tester Guide` if you need the deeper regression path