Production runbook

What to check before, during, and after launch.

A practical owner/admin runbook for production environment checks, test orders, support coverage, backup/restore, incident response, customer data requests, attorney/vendor handoffs, and rollback decisions.

Before launch

Configuration

  • Database and encrypted uploads tested.
  • Stripe live test + webhooks reconciled.
  • Google OAuth and document exports configured.
  • AI keys configured with consent and escalation.
  • NY/NJ content and support SOP reviewed.

During launch

Daily monitoring

  • Paid starts and onboarding failures.
  • Upload malware/OCR/quality status.
  • Staff/paralegal/attorney queue age.
  • Refund/chargeback and referral holds.
  • AI escalations and support tickets.

Incident response

Slow down safely

  • Switch to waitlist-only.
  • Disable payment products if needed.
  • Hold referral payouts.
  • Lock finalization release.
  • Notify affected customers without legal advice.

After launch

Close the loop

  • Export audit timeline.
  • Review state content feedback.
  • Update templates carefully.
  • Reconcile revenue and payouts.
  • Plan next state only after review.

Log production runbook event

No event saved.