Create a guided formulation brief

What you will accomplish

You will ask Ask Formuley for a structured guided brief, review its product architecture, ingredient classes, risk checkpoints, and validation work, then translate the direction into a controlled formula-development plan. The brief does not create a finished manufacturing recipe.

Before you start

Define the product type and the problem the product should solve. Gather the intended user, sensory target, formula structure, key goals, budget direction, exclusions, claims constraints, launch markets, packaging, and testing expectations you already know. Your account shows whether guided briefs are available and how many remain.

Request the guided brief

1. Open Ask Formuley. Start from the in-product AI control for the guided formulation brief.
2. Name the product type. This is the required input, such as moisturizing cream, facial serum, shampoo, body lotion, cleanser, or toner.
3. Describe the formula type when known. State whether the direction is an emulsion, anhydrous system, surfactant system, soap, fragrance, haircare product, sunscreen, or general concept.
4. Add the key goals. Describe performance, sensory, user, or process outcomes without asking for unsupported claims.
5. Add useful constraints. Include skin type, budget direction, and materials or categories that must be avoided when they matter.
6. Ask for a guided brief. Keep the request focused on architecture, development risks, and what must be validated.

Example: "Build a guided brief for a light rinse-off conditioner for fine hair. Prioritize slip without heavy deposition, keep the system silicone-free, and identify the first three bench variables."

Review the structured result

1. Check the input summary. Confirm that the brief understood the intended product and constraints.
2. Review product architecture. Decide whether the proposed high-level structure fits the product and process.
3. Review candidate ingredient classes. Use them as functional categories, not as approval of a specific supplier grade.
4. Review target ranges and process checkpoints. Translate them into testable hypotheses rather than copying them into production instructions.
5. Review likely failure modes. Add any preservation, pH, compatibility, stability, packaging, scale-up, or claims risk that the context was too limited to identify.
6. Review missing information. Fill the packaging, market, viscosity, budget, exclusion, and evidence gaps before building.
7. Review confidence and validation checklist. The brief still needs a qualified person's review even when confidence appears high.

The response may include AI suggestions or guidance from the details you entered. It may leave out product details that were not supplied.

Translate the brief into formulation work

1. Open the Formula Builder from the brief. Its product type and constraints will carry into the new formula. Create a draft with the exact raw materials you have evaluated.
2. Optionally generate an AI draft. If available in your account, review the editable proposal made from your verified raw materials. Generating it does not save a formula or confirm that it is safe, tested, or compliant.
3. Choose supplier-supported materials. Verify identity, composition, use level, pH range, incompatibilities, and processing guidance.
4. Write the manufacturing method. Define phase order, temperature, mixing, hold, cool-down, pH adjustment, and quality checkpoints from verified sources and bench learning.
5. Plan controlled variations. Change one interpretable variable at a time and keep a control.
6. Run formula screening. Use calculators, formula review, and compliance checks to find issues; do not mistake them for validation.
7. Complete physical verification. A qualified formulator must confirm bench behavior, safety strategy, stability, preservation, compatibility, scale-up, and specifications.
8. Route final decisions to qualified owners. Regulatory, QA, claims, and release decisions remain human responsibilities.

Refine without losing the boundary

1. Ask for simpler, safer, cheaper, or balanced test lanes. Keep the request tied to a defined formula or architecture.
2. Ask what evidence is missing. Use the response to strengthen the validation plan.
3. Ask for failure hypotheses. Test each hypothesis rather than accepting the explanation as fact.
4. Do not request exact copy-ready percentages in normal chat. The guided brief intentionally stays above a finished recipe.
5. Record verified conclusions in the formula. Chat history is not the controlled formulation or release record.

Check your work

• The request states a product type, goals, and meaningful constraints.
• The guided brief separates product architecture, ingredient classes, risk checkpoints, missing information, and validation work.
• No suggested material, range, process, claim, or market statement has been accepted without verification.
• The Formula Builder contains the actual selected materials and reviewed method.
• A qualified formulator owns physical validation and qualified reviewers own safety, regulatory, QA, and release decisions.

If something does not look right

• If the brief misunderstands the product, restate the product type and constraints in one focused request.
• If the architecture is too generic, provide the intended structure, sensory target, packaging, and most important failure risk.
• If you cannot request a brief or AI draft, check the allowance, plan, or workspace setting shown in the product.
• If a response supplies unsupported exactness, treat it as unverified and return to supplier evidence and bench work.
• If formula review finds no issue, continue the required tests; a clean screening result is not proof of safety or release readiness.

Next steps

• Build the working formula
• Review all AI boundaries
• Use deformulation for a label-order research reference