BRÈCHE
Confidential launch review worksheet
Guide: /guides/confidential-project-launch
Updated: 2026-09-25

Review the client's own public release while keeping client work out of studio references. This is a planning record, not a guarantee of anonymity.
Fill this in locally. Nothing is sent to BRÈCHE.
Do not include passwords, API keys, wallet recovery phrases or private customer data.

1. Information boundary
Name the facts that must remain private, using neutral references rather than copying sensitive data into this worksheet.
Your notes:


2. People and approval
Identify who may receive each category of information and who approves the client's own public release.
Your notes:


3. Public surfaces
List copy, metadata, social previews, images, document properties, downloads and public repositories. Record reviewer, version and result for each.
Your notes:


4. Public build
Record checks of client assets, configuration exposure and source maps within the agreed scope. List unresolved findings without reproducing secrets.
Your notes:


5. Provider responsibilities
Name domain, hosting, payment and collaboration providers, their account owner and the provider requirements still to verify.
Your notes:


6. No client references
Confirm that no client names, links, screenshots, credits, results or anonymised case studies appear in studio publications or reference materials. BRÈCHE does not share past projects with prospects.
Your notes:


7. Launch decision
List each open disclosure issue, its owner and whether it blocks publication. Record what was actually reviewed.
Your notes:


8. After handover
Assign ongoing checks for new files, metadata, integrations and announcements. Identify who can approve changes to the boundary.
Your notes: