Review launch readiness and evidence

What you will accomplish

Review one product’s readiness, understand what is complete or blocked, connect missing evidence, and leave formal release decisions with the authorized reviewers.

Before you start

• Open /product-launch and choose the intended launch file.
• Confirm the product name, target market, owner, formula, and connected development record.
• Gather the latest packaging, claims, testing, compliance, label, batch, finished-goods, and post-market records that apply.

Read the stage status

The stage navigator uses Current, Complete, Blocked, Review, and Not started. Open the current or blocked stage to see its evidence and next action. Readiness is calculated per launch file; it is not a combined approval across products.

Use Needs attention for the highest-priority open gap. Use the portfolio filters to narrow the list by readiness, owner, connected record, missing evidence, market, client or program, or integration.

Connect and verify evidence

1. Open the relevant stage.
2. Connect the existing Formuley record that contains the current information.
3. Use manual evidence or an external source only when the interface supports that evidence type and the source can be verified.
4. Review dates, owners, target market, status, and linked files before treating a stage as complete.
5. Revisit downstream stages when a pinned source changes after review or approval.

Ask Formuley can summarize connected evidence and suggest a next action. It does not verify a supplier document, test result, label, batch, claim, or release decision.

Keep approval boundaries clear

A readiness score summarizes the information currently connected to the launch. Client approval does not replace QA or regulatory review. A completed stage does not automatically authorize manufacturing, market release, or a claim. Formal approvals still require the right plan, role, identity check, and evidence.

Check your work

• Every complete stage has current evidence for the correct product and market.
• Blocked and review states have an owner and a clear next action.
• Changes to connected records have been reviewed in every affected later stage.
• Manual or external evidence identifies the real source and date.
• No readiness score or AI summary has been used as the final release decision.
• Post-market issues remain connected to the released product and affected records.

If something does not look right

• If a stage stays blocked, open it and review the specific missing or changed source instead of relying on the portfolio summary.
• If the readiness score appears wrong, confirm evidence is connected to this launch file and not only stored elsewhere in the account.
• If an approval action is unavailable, confirm the plan, role, and any required identity check shown by Formuley.
• If evidence belongs to another product, remove or correct the connection before continuing.
• If a released source changed, complete the required review before using it for new controlled batches.

Next steps

• Create a Product Launch file
• Start a stability study
• Run a US compliance review