Bannershut

Pilot Launch Checklist

A controlled launch checklist for onboarding the first 2-3 Bannershut pilot organizations without direct website editing access.

Pilot onboarding

Launch gate

Complete these checks for each pilot before marking the organization active for production use.

Phase 10

Confirm organization name, slug, plan, billing mode, and primary admin

Create or verify admin, content manager, contributor, and viewer roles

Map only the launch zones needed for the first pilot week

Upload one media asset and publish one approved content item

Install the widget on the pilot website and verify public delivery

Confirm audit logs, backup freshness, and Kuma monitors during launch

Keep the first launch deliberately small: one website, a few zones, one approval workflow, and one week of monitoring.

Capture the organization, admin contact, website platform, billing mode, and launch date.

Configure stable zone keys such as homepage_hero, announcement_bar, emergency_alert, and footer_notice.

Invite the initial admin, content manager, contributor, and viewer accounts needed for acceptance.

Create, submit, approve, publish, and archive at least one content item with the pilot team.

Verify the public API, zones index, widget embed, and hosted page if one is used.

Monitor usage for one week before expanding scope or adding larger features.

Record the final result in the Phase 10 pilot launch document after each organization completes the flow.

2-3 pilots

Admin sign-in succeeds.

Contributor submission and approval flow succeeds.

Widget renders the correct zone on the pilot website.

Viewer role cannot mutate protected areas.

No cross-organization data appears.

Kuma and backup checks remain healthy for the pilot window.