RaveFocus launch handoff

Post-creation handoff

This is the exact next sequence after the Microsoft Lists and Planner Premium pieces are manually created. Follow it in order so forms, flows, auth, and verification do not get switched on before the system is ready.

not ready for worker launch current launch state
6 handoff steps
15 worker Lists to verify
7 Premium plans to confirm
9 flows to build
3 protected routes prepared
Launch guard: do not invite workers until this handoff and the production go-live sequence both pass verification.

Rules

Handoff steps

1
admin

confirm sharepoint lists

waiting for manual list creation

Do next

Create all worker-facing and support Microsoft Lists, then run the live form verifier and sync the captured IDs into the Microsoft ID capture sheet.

Command or action

npm.cmd run verify:sharepoint-forms; npm.cmd run sync:sharepoint-ids; npm.cmd run build:microsoft-id-reconciliation

Pass condition

all 15 worker-facing Lists are found, synced, and NewForm URLs open

Stop if

Any worker-facing List is missing or any NewForm URL fails.

Evidence

  • outputs/sharepoint-first-unblock-action-sheet.html
  • outputs/sharepoint-first-unblock-action-sheet.csv
  • outputs/sharepoint-go-live-checklist.html
  • outputs/sharepoint-live-form-verification.csv
  • outputs/sharepoint-id-sync-report.html
  • outputs/microsoft-id-capture-filled.csv
  • outputs/sharepoint-manual-import-index.html
2
admin / Jupiter

confirm planner premium portfolio

manual premium ID capture pending

Do next

Confirm the Planner Plan 3 portfolio, seven Premium plans, relevant custom fields, process notes, and captured Premium IDs/URLs exist.

Command or action

manual Planner Plan 3 review; npm.cmd run postsetup:planner-premium-report

Pass condition

7 Premium plans, 15 field pool entries, and 7/7 Premium IDs are confirmed

Stop if

Premium plans are missing, field choices are wrong, or the website dispatch IDs were replaced.

Evidence

  • outputs/planner-premium-owner-action-sheet.html
  • outputs/planner-premium-owner-action-sheet.csv
  • outputs/planner-premium-go-live-checklist.html
  • outputs/planner-premium-post-setup-pipeline.html
  • outputs/planner-premium-setup-index.html
  • outputs/planner-premium-dispatch-crosswalk.html
  • outputs/planner-premium-field-plan.csv
3
admin

switch forms live

mapped; SharePoint Lists not live

Do next

Only after SharePoint form verification passes, switch the website from draft-safe mode to live SharePoint form mode.

Command or action

npm.cmd run forms:live

Pass condition

15 worker forms point to live SharePoint List forms after redeploy

Stop if

Live form verification has not passed or a List is missing.

Evidence

  • launch/set-sharepoint-lists-live.ps1
  • assets/data/worker-integration-contract.json
  • outputs/worker-integration-contract.html
4
admin

build power automate flows

manual flow ID capture pending

Do next

Build the mapped Power Automate flows against the now-existing Lists and Planner dispatch layer.

Command or action

manual Power Automate build; npm.cmd run postsetup:power-automate-report

Pass condition

9 flows exist, use the expected trigger Lists, and write proof-safe updates only

Stop if

A trigger List does not exist, a flow would expose sensitive records, or Planner target mapping is unclear.

Evidence

  • outputs/power-automate-owner-action-sheet.html
  • outputs/power-automate-owner-action-sheet.csv
  • outputs/power-automate-post-setup-pipeline.html
  • outputs/power-automate-flow-build-sheet.html
  • outputs/power-automate-flow-plan.csv
  • assets/data/power-automate-flow-manifest.json
5
admin

apply auth

prepared; not enforced

Do next

Configure Microsoft Entra roles, then apply the protected Static Web Apps config.

Command or action

powershell -NoProfile -ExecutionPolicy Bypass -File launch\set-static-web-app-auth-mode.ps1 -Mode apply

Pass condition

authenticated users can reach worker areas and only admin can reach admin/output proof pages

Stop if

Roles are not assigned, admin cannot verify access, or workers have access to restricted outputs.

Evidence

  • outputs/auth-owner-action-sheet.html
  • outputs/auth-owner-action-sheet.csv
  • outputs/auth-go-live-checklist.html
  • outputs/azure-static-web-app-auth-readiness.html
  • launch/staticwebapp.authenticated.config.json
6
admin

final go-live preflight

not ready for worker launch

Do next

Run the final preflight after Lists, Premium, flows, form mode, and auth are ready.

Command or action

npm.cmd run preflight:final

Pass condition

final preflight reports ready for final go-live review

Stop if

Any preflight gate is blocked, forms-live is not allowed, or the live site still reports not ready for worker launch.

Evidence

  • outputs/final-go-live-preflight.html
  • outputs/final-go-live-preflight.csv
  • outputs/production-go-live-sequence.html
  • scripts/verify-site.mjs
  • scripts/verify-rendered-layout.mjs
  • scripts/verify-live-site.mjs