1. Basic context
- Company or team name.
- Product or app name.
- Website or public product page.
- Primary contact name and email.
Release Protection Pack
Limited preview intake template
Use this when a team wants a small release-risk preview without private repo review, production access, or a paid commitment. The first pass stays narrow: one release path, one primary platform, and public or shareable evidence only.
Commercial onboarding and readiness checks still apply before any private access, delivery commitment, or paid start.
How to use this
- Keep the first pass narrow: one release path, one primary platform, one critical flow.
- Share links or files that are already public or safe to share.
- Mark anything uncertain as unknown instead of guessing.
2. Release in scope
- Target release window.
- Platform in scope: iOS, Android, web, desktop, or internal app.
- Release candidate, version, or build identifier.
- One-sentence reason this release feels risky.
3. Critical flow to protect
- The most important user flow for this pass.
- What failure would hurt most.
- Who decides go, no-go, or defer.
4. Public or shareable evidence
- Public product link or app-store listing.
- Screenshots or screen recording.
- Redacted build or CI output.
- Public changelog, release notes, or redacted error screenshot.
5. Current unknowns
- Install or update path not fully proven.
- Launch behavior uncertain.
- One integration or API dependency uncertain.
- Offline, slow-network, or rollback behavior unknown.
6. Preview goal
- Sanity-check whether the release risk is real.
- Identify the narrowest useful first validation scope.
- Decide whether a deeper fixed-scope pack is worth discussing after onboarding.
Explicit boundaries
- No private repository review.
- No production access, credentials, or secrets.
- No legal, compliance, or app-store policy advice.
- No unlimited QA coverage or open-ended support.
Copy/paste request template
Use this verbatim if you want the smallest possible starting brief.
Subject: Release Protection Pack limited preview
Team/company:
Product/app:
Public link:
Primary contact:
Contact email:
Release window:
Platform in scope:
Build/version:
Critical flow to protect:
Main risk if it fails:
Release decision owner:
Public/shareable evidence:
-
-
-
Current unknowns:
-
-
What we want from the preview:
Anything explicitly out of scope:Next safe step
Share the public or shareable context first, then decide whether a limited preview is enough or whether a fixed-cost package should wait for commercial onboarding.