Bakery Operations Coordination Board
type visualization
visualization-type board
title Bakery Operations Coordination
created_at 2026-06-28 The FL2 end-to-end coordination board for Bakery Operations — one swimlane per
flight-item-type currently in motion. The types flow differently, so each lane carries
its own columns : the daily
Daily Replenishment Order runs the demand–plan–produce–deliver cycle, a
Wholesale Contract goes from enquiry to a running account, a New Shop Launch is
accepted, prepared, and opened, and a New Product Introduction rolls out via trial
bakes into the range.
In the replenishment lane, once an order is Planned the coordination work on it is
finished; while it is In-Production the order sits with the Bakehouse at FL1, and
FL2 is waiting on it.
title : Bakery Operations Coordination
flightlevel : FL2
lanes :
- name : Daily Replenishment Order
columns :
- name : Demand-In
status-category : to-do
- name : Planning
wip : 3
status-category : in-progress
- name : Planned
status-category : done
- name : In-Production
status-category : waiting
- name : Delivered
status-category : done
- name : Wholesale Contract
columns :
- name : Enquiry
status-category : to-do
- name : Negotiation
status-category : in-progress
- name : Signed
status-category : done
- name : Running
status-category : in-progress
- name : New Shop Launch
agreements :
- "Strategic launches need FL3 sign-off before capacity is committed"
columns :
- name : Accepted
status-category : to-do
- name : In-Prep
status-category : in-progress
- name : Open
status-category : done
- name : New Product Introduction
columns :
- name : Rollout-Planning
status-category : to-do
- name : Trial-Bakes
status-category : in-progress
- name : In-Range
status-category : donetitle: Bakery Operations Coordination
flightlevel: FL2
lanes:
- name: Daily Replenishment Order
columns:
- name: Demand-In
status-category: to-do
- name: Planning
wip: 3
status-category: in-progress
- name: Planned
status-category: done
- name: In-Production
status-category: waiting
- name: Delivered
status-category: done
- name: Wholesale Contract
columns:
- name: Enquiry
status-category: to-do
- name: Negotiation
status-category: in-progress
- name: Signed
status-category: done
- name: Running
status-category: in-progress
- name: New Shop Launch
agreements:
- "Strategic launches need FL3 sign-off before capacity is committed"
columns:
- name: Accepted
status-category: to-do
- name: In-Prep
status-category: in-progress
- name: Open
status-category: done
- name: New Product Introduction
columns:
- name: Rollout-Planning
status-category: to-do
- name: Trial-Bakes
status-category: in-progress
- name: In-Range
status-category: done
Modeling note
Lanes are plain named lanes named after the item type (the board DSL
has no typed item-type binding); each lane’s columns are lane-local columns:. Status
categories read from FL2’s perspective: in the replenishment lane, Planned is done
while In-Production is waiting.
Like what you see? → Start — build your own org folder in ~2 min
Bakery Operations Coordination Board.md
---
type : visualization
visualization-type : board
title : Bakery Operations Coordination
visualization-of : "[[Bakery Operations]]"
created_at : 2026 -06-28
--- The FL2 end-to-end coordination board for [[Bakery Operations]] — one **swimlane per
flight-item-type** currently in motion. The types flow differently, so **each lane carries
its own columns**: the daily
[[Daily Replenishment Order]] runs the demand–plan–produce–deliver cycle, a
[[Wholesale Contract]] goes from enquiry to a running account, a [[New Shop Launch]] is
accepted, prepared, and opened, and a [[New Product Introduction]] rolls out via trial
In the replenishment lane, once an order is `Planned` the coordination work on it is
finished; while it is `In-Production` the order sits with the [[ Bakehouse ]] at FL1, and
```dwsd.board id=bakery-operations-coordination
title: Bakery Operations Coordination
- name: Daily Replenishment Order
status-category: in-progress
- name: Wholesale Contract
status-category: in-progress
status-category: in-progress
- "Strategic launches need FL3 sign-off before capacity is committed"
status-category: in-progress
- name: New Product Introduction
status-category: in-progress
> **Modeling note.** Lanes are plain `named` lanes named after the item type (the board DSL
> has no typed item-type binding); each lane's columns are lane-local `columns:` . Status
> categories read from FL2's perspective: in the replenishment lane, `Planned` is `done`
> while `In-Production` is `waiting` .