Skip to main content

Recipe drafts

Recipe drafts holds three kinds of draft: recipes you saved as a draft from the new recipe form, recipe changes proposed by an AI assistant connected through the Brikly Connector, and recipes the Brikly team built for you when you asked us to set your account up. Drafts never touch your live recipes. They sit in the inbox until you approve, reject, or discard them.

This page is for the operator side of the flow. For the assistant side (proposing drafts from chat), see the Connector example questions.

When you would see a draft​

You will see a pending draft when you choose Save as draft on the new recipe form (see Saving a recipe as a draft). Its detail panel says it was submitted via the recipe editor, and any row you had not picked from the list shows as an ingredient to source.

You will also see a pending draft any time an AI assistant proposes a recipe change on your behalf. Common examples:

  • "Swap dairy milk for oat milk on every drink that uses it." The assistant proposes one draft per affected recipe.
  • "Add a salted caramel variant of our Latte." The assistant proposes a new recipe.
  • "Bump the brownie tray yield from 16 to 14 and update the per-slice yield." The assistant proposes an edit to the brownie recipe.
  • "I want to add a pistachio cardamom bun." The assistant proposes a new recipe and flags the ingredients you do not yet stock (pistachio paste, ground cardamom) as Needs sourcing, for you to add at approval time.

The assistant always proposes. You always approve. There is no path where the assistant changes a live recipe without you.

If you asked us to set your account up, the recipes we build arrive here too. Their detail panel says Set up by the Brikly team with the date, and shows any Notes from the Brikly team about how we built them. You approve them the same way.

Finding the inbox​

There are two entry points, both inside CostingBrik:

  • CostingBrik dashboard - when at least one draft is pending, a card titled N pending drafts appears, with Review drafts through to the inbox.
  • Recipes list page - the header shows a Pending drafts button next to Add recipe.

Both badges are hidden when no drafts are pending, so the inbox stays out of the way until there is something in it.

The inbox lives at /costing/drafts.

Drafts that reference at least one ingredient you do not yet stock show a Needs sourcing chip on their row. A matching filter chip at the top of the inbox narrows the list to those drafts so you can work through your sourcing backlog in one sitting.

Reviewing a draft​

Click any row in the inbox to open the draft detail panel. The panel shows three things:

The diff​

For an Update draft, Before shows the recipe as it was when the draft was proposed and Proposed shows the change. Changed fields are highlighted. Ingredient additions, removals, and quantity changes show line by line.

For a New recipe draft, you see the proposed recipe on its own. There is nothing live to compare it against.

For a Duplicate draft there is no Before column either: you see the proposed copy, and the line tables list only the lines that differ from the recipe it copies.

Cost preview​

Live cost and margin numbers, computed against today's ingredient prices (not the snapshot from when the draft was proposed). You see:

  • Current cost per unit vs Proposed cost per unit, and the Delta between them.
  • Current margin vs Proposed margin (VAT-correct), and the Margin delta in percentage points.

The inbox and the Connector use the same cost engine, so the figures match what the assistant quoted at the moment it quoted them. The inbox works them out again each time you open the draft, so they move if prices have changed since.

A draft for a recipe with no selling price, or whose ingredients are not priced yet, shows no GP figure. If a proposed line cannot be priced (an ingredient with no supplier price, a line archived since the draft was proposed, or a base recipe that needs a finished weight or volume), the preview reads Cost from costed lines and shows a dash for the margin. The line itself carries a chip saying why, such as No price yet, Archived or Needs a finished weight, and hovering over it says what to do.

Rationale​

The AI assistant's free-text explanation of why it proposed the change. This is whatever the assistant wrote when it submitted the draft. Read it before approving. Drafts you saved yourself have no rationale.

Resolve ingredients​

If the draft references ingredients you do not yet stock, the detail panel shows a Resolve ingredients section above the cost preview. Each pending ingredient must be sourced before the draft can be approved.

For each pending ingredient you see:

  • The agent's suggested name and purchase unit (for example, "Pistachio paste" in kg).
  • Any free-text agent notes, clearly labelled Agent notes (not committed to data). These are the assistant's commentary, never written to your data layer. They might include a sourcing hint or rough price expectation, but no number from these notes feeds the cost engine.

You have two options per ingredient:

  • Link to existing ingredient. Opens a picker so you can match the pending name to an ingredient already in your pantry. Useful when the assistant has invented a name that you already track under a slightly different label.
  • Create new ingredient. Opens the usual ingredient creation form, pre-filled with the agent's suggested name and purchase unit. You add the supplier, pack size, and cost yourself. Once created, the ingredient is automatically linked to this draft.

The picker never auto-links: a match you make here is always your own choice. An assistant can also link a pending ingredient to one you already stock when you ask it to in chat. Creating a new ingredient is always done here.

Until every pending ingredient has been linked or created, Approve and apply stays disabled and the cost preview shows a partial cost with a "Margin pending until sourcing complete" note. The partial cost reflects the lines you have already sourced, so you can watch the cost build as you work through the list.

If you link an ingredient and later delete that ingredient from CostingBrik before approving, the draft notices and flips the pending entry back to unresolved. No approval will ever commit a recipe that points at a deleted ingredient.

The four actions​

Approve and apply​

Applies the proposed change to the live recipe. For an edit, this updates the existing recipe in place. For a new recipe or duplicate, this creates a fresh recipe in your catalogue.

If the draft had pending ingredients that you resolved (either by linking to existing ingredients or creating new ones), the approved recipe references those resolved ingredients directly. No "pending" placeholders survive into the live recipe.

The draft is marked approved with your user ID and the time of approval, and kept on record. The record captures, for each previously pending ingredient, which resolution method you used (link vs create) and the resulting ingredient ID. The inbox lists pending drafts only, so approved, rejected and discarded drafts do not show there; an assistant connected through the Brikly Connector can list them.

Edit, then approve​

Opens the recipe editor with the draft filled in, so you can make further changes before applying. Useful when the assistant's proposal is close but not quite right - for example, the quantities look about right but you want to adjust the yield first.

The editor opens with the agent's changes, the ingredients you linked, and every setting the agent left alone (takeaway VAT, finished yield, serving size, sites and labour from the live recipe). Each ingredient line is costed as it opens. A draft for a new recipe or a duplicate opens a new recipe form.

  • The draft stays in the inbox until you save. Saving the recipe closes the draft as approved. If you leave the editor without saving, the draft is still there.
  • Greyed out until every ingredient is sourced. While any ingredient is still pending sourcing, the button is greyed out with "Source every ingredient first."
  • Rows to check. A line Brikly could not fill in, such as an ingredient that has since been archived, opens as a named row with its amount. The save asks you to pick it from the list or remove the row.
  • Base recipes by weight or volume. A base recipe line can be measured in grams only if the base recipe has a finished weight, or a weight for every ingredient. The same goes for ml and volume. Otherwise use portions or batches, or set a finished weight or volume on the base recipe first.

For a new or duplicated recipe, saving the editor as a draft again (the chevron next to Add recipe) keeps the draft pending with your changes, rather than adding a second draft. A draft that edits an existing recipe opens in the recipe's edit form, which has no Save as draft.

If the recipe saves but the draft cannot be closed, Brikly says the draft is still in Recipe drafts. Discard it there (or, as a member, ask an owner or admin to) so it is not applied a second time.

Reject​

Marks the draft as rejected with an optional reason. Use this when you have considered the proposal and decided not to apply it. Rejected drafts are kept on record.

Discard​

Marks the draft as discarded with an optional reason. Use this when the draft is not worth keeping in history (the assistant misunderstood, or you accidentally asked twice).

The semantic difference is small: rejected means "considered, no"; discarded means "not worth keeping in history". Both leave the live recipe untouched.

Approving several drafts at once​

When an assistant proposes a batch of changes, for example one draft per drink after "swap dairy milk for oat milk on every drink", you do not have to open each one.

  1. Tick the box on each draft card you want to apply, or click Select all ready (it shows how many) to tick every visible draft that is pending, not stale, and not waiting on sourcing.
  2. A bar appears at the bottom of the inbox showing how many drafts are selected. Click Approve N and confirm.
  3. Each selected draft is applied to its live recipe in turn, one at a time, exactly as if you had clicked Approve and apply on it. A draft that fails does not undo the ones applied before it.

Drafts that cannot be applied are skipped and stay in the inbox, and the rest of the batch still applies. The card shows a short reason:

On the cardWhat it meansWhat to do
Skipped: staleThe live recipe changed after the draft was proposedOpen the draft and use Edit, then approve, or discard it
Skipped: needs sourcingAt least one ingredient is still pending sourcingOpen the draft and resolve the ingredients first
Skipped: needs checkingOne of the draft's ingredients, base recipes or packaging items is no longer available, for example a base recipe that has since been archivedOpen the draft to check it
Skipped: already reviewedSomeone approved, rejected, or discarded it in the meantimeNothing to do
Skipped: recipe archived or deletedThe recipe the draft edits was archived or deletedDiscard the draft
Skipped: could not be appliedThe save refused it, for example because approving would leave a base recipe without the finished weight or volume other recipes use it byThe card shows why. Fix the recipe, then approve again

A recipe has at most one pending draft at a time. If an assistant proposes another change to a recipe that already has one, the older draft is closed as superseded and leaves the inbox.

Bulk approve uses the same permissions as Approve and apply, so viewers do not see the checkboxes. There is no bulk approve over the Connector. Assistants can propose many drafts, but approving them always happens here.

Who can do what​

Permissions follow the standard CostingBrik role mapping:

RoleView inboxApprove and apply (edit)Approve and apply (new recipe)RejectDiscard
OwnerYesYesYesYesYes
AdminYesYesYesYesYes
MemberYesYesYesNoNo
ViewerYes (read-only)NoNoNoNo

Members can approve drafts, and use Edit, then approve, because applying a draft is equivalent to editing or creating a recipe, which members are already allowed to do. Rejecting and discarding require admin or owner because they move a draft into a closed state.

Viewers see the inbox but no action buttons are rendered for them.

Stale drafts​

A draft that changes an existing recipe becomes stale when the live recipe has changed since the assistant proposed the draft, in a field the draft also sets. An assistant's proposal always sets the recipe's name, type, portions, selling price, VAT and ingredient lines, so a change to any of those makes it stale. Changing the sites the recipe is sold at, or its takeaway VAT, does not.

For example: the assistant proposes raising the latte's milk quantity to 240 ml. Before you review the draft, another team member updates the latte's milk to 220 ml, or changes its selling price. Either change makes the draft stale.

When an Update draft is stale, the detail panel shows a banner listing the fields that diverged, and Approve and apply is not offered. You have three options:

  • Re-review the diff. The cost preview updates against today's live recipe, so you may decide the proposal is no longer interesting.
  • Edit, then approve. Opens the draft against the live recipe, so you can use the agent's proposal as a starting point and reconcile it with the changes made since.
  • Discard. If the live update has already done what the agent suggested, the draft is no longer useful. Members cannot discard: ask an owner or admin.

Brikly never silently overwrites operator changes with a stale draft. Approval is blocked until you resolve the staleness one way or another.

Drafts that evolve mid-conversation​

A draft can be refined in place by the AI assistant without changing its inbox row. If you and the assistant work through a new product idea over several messages, the assistant updates the same draft each time rather than filing a new one. You see one item in the inbox throughout the conversation, with its cost preview, summary, and pending ingredients all reflecting the latest version.

Structural identity is locked: an assistant can change the spec, summary, or rationale of a pending draft, but it cannot change which recipe the draft targets or whether it is an edit, create, or duplicate. Those changes always file a new draft.

If you have already resolved a pending ingredient and the assistant later tweaks the spec in a way that keeps that ingredient unchanged (same name, same purchase unit, same position in the recipe), your resolution survives. If the assistant promotes that line to a different ingredient, swaps it for a different pending ingredient, or removes it, the resolution is dropped and you can re-source.

When a recipe is archived​

Archiving a recipe closes its pending drafts as superseded, so they leave the inbox and stop counting towards the cap below. Restoring the recipe does not bring them back. Approving a draft whose recipe has been archived or deleted is refused with "The recipe this draft changes has been archived or deleted. Discard the draft."

Pending-draft cap​

Each tenant can have up to 50 pending drafts at any one time, counting every pending draft: the ones you saved, the ones an assistant proposed and the ones the Brikly team built for you. If an AI assistant tries to propose a 51st draft while 50 are already pending, the propose tool returns an error and the assistant tells you to clear some drafts from the inbox before proposing more. Save as draft on the recipe form says the same and asks you to approve or discard some first.

The cap is per tenant, not per location or per user. It exists to stop a runaway assistant loop from filling the inbox faster than you can review.

What happens after a draft is approved​

The draft is marked approved, the underlying recipe is updated (or created), and:

  • Every recipe that uses it as a base recipe is re-costed, and if its lines changed, its allergens are worked out again.
  • Brikly keeps the approved draft on record: who applied it, when, and what was proposed.

Anything the assistant's proposal does not mention keeps its current value: packaging (including takeaway-only items), labour, takeaway VAT, finished weight, serving size, the sites it is sold at, variation, category and recipe type. A proposal that lists packaging replaces the packaging. A duplicated recipe does not take the original's variation.

What an approved draft does not do​

  • It does not push a live recipe to a saved what-if scenario. Those are separate.
  • It does not notify your team. Approvals are silent.
  • It does not undo itself if you change your mind. To undo a change to the recipe's costing, roll the recipe back to the version before it in Version history, or edit the recipe directly.

Drafts proposed by mistake​

If you see a draft in the inbox that you did not ask the assistant to propose, the safe action is Discard (members: ask an owner or admin). It does not touch your live data.

If a draft looks like a hallucination (proposes an ingredient you do not stock, or a recipe you never asked about), discard it and let us know. The assistant should never propose something with no operator request behind it.