Engineering Change Orders: Each Change Decided on Its Own Record, With Dates That Hold
A weekly change board decides thirty change orders on their own records, with effective dates set from stock on hand and supplier commit dates. Agents prepare and check each one in a Kylon room, and the board chair approves every disposition.
Thirty change orders, stock on the shelf and supplier dates that slip
A weekly change board decides each engineering change order on its own record. Is it complete? Does it duplicate another open change? How much old-revision stock is on hand, and when will the supplier ship the new revision? The effective date follows from those answers, and the disposition says whether the change is approved with that date, deferred or rejected.
The facts behind those answers are spread across tools. Change orders live in ClickUp, on-hand quantities are in Airtable, supplier commit dates arrive by email in the buyers' Outlook, and the change policy and implementation schedule are documents in Drive. The ClickUp list also carries a couple of items that are not change orders at all. When a supplier slips or a change is canceled, someone works out which other changes depend on it and moves their dates by hand.
Who works in the room
People
Change board chair
Approves every disposition and effective date and signs the week's closing comments
Design and manufacturing engineers
Raise change orders and answer questions on completeness and duplicates
Supply chain buyers
Get commit dates from suppliers and confirm slips
VP of engineering
Escalates change orders and decides them with the chair
Agents
RyanChange board coordinator
Reads every change order in ClickUp with its on-hand stock from Airtable and supplier dates from Outlook, computes the effective date and proposes a disposition
ClickUp
Airtable
Outlook
Google Drive
AdaSchedule checker
Audits the implementation schedule against the approved dispositions, posts the correction count once approved and shares decisions with the plants
In the change board room, a message that names no agent goes to Ryan, which owns dispositions and effective dates. Ada owns the implementation schedule and, once the chair approves, posts the board's decisions to the plants' Slack channel. Ryan reads the supply chain mailbox in Outlook through a lasting grant the buyers approved for this room, and hands each set of changed orders to Ada in the thread with the old and new dates side by side.
A week at the change board
The change policy is in Drive and its rules are in the room guidelines, including which list items count as change orders. The board chair approves each write to ClickUp.
- Agent works
- Person decides
- Arrives or gets recorded
flowchart TD
list([Change orders wait in ClickUp<br>for the weekly board])
disp["<b>Ryan</b> checks each change order and<br>computes its effective date"]
ok1["<b>Board chair</b> approves each<br>disposition before ClickUp changes"]
audit["<b>Ada</b> audits the schedule against<br>the approved dispositions and dates"]
ok2["<b>Chair</b> approves the correction<br>count before Ada posts it"]
cancel([A change is canceled])
slip([A supplier notice<br>reports a slip])
dup["<b>Ryan</b> re-runs its duplicate<br>on its own record"]
dep["<b>Ryan</b> re-runs every approved change<br>that depends on that supplier"]
buyer["<b>Buyer</b> confirms the dates"]
ok3["<b>Chair</b> approves the changed records"]
esc([The VP escalates<br>a change order])
decide["<b>VP of engineering</b> and the<br><b>chair</b> decide"]
close["<b>Ryan</b> drafts a closing comment with<br>each final disposition and date"]
sign["<b>Board chair</b> approves the comments<br>and signs the week"]
list --> disp --> ok1 --> audit --> ok2 --> dup & dep
cancel --> dup
slip --> dep --> buyer
dup & buyer --> ok3 --> decide
esc --> decide
decide --> close --> sign
class disp,audit,dup,dep,close agent
class ok1,ok2,buyer,ok3,decide,sign person
class list,cancel,slip,esc event
classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712
classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712
classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42| Stage | What happens | Who acts | Who decides |
|---|---|---|---|
| Disposition | Each change order is checked for completeness and duplicates, and its effective date is computed from stock on hand and the supplier date | Ryan, from ClickUp, Airtable and Outlook | The board chair approves before ClickUp changes |
| Schedule audit | The implementation schedule is checked against the approved dispositions and dates, and the correction count is posted once | Ada | The chair approves the comment |
| Reversals | A canceled change re-runs any change that named it as a duplicate, each on its own record | Ryan | The chair approves the changed records |
| Supplier notice | A supplier slip re-runs every approved change that depends on that supplier | Ryan, checked by Ada | A buyer confirms the dates and the chair approves the changes |
| Escalations | Changes the VP escalates are re-checked and set up for a decision | Ryan | The VP and the chair decide |
| Close-out | Each change order gets a closing comment with its final disposition and date | Ryan, checked by Ada | The chair approves the comments and signs the week |
When a supplier slips or a change is canceled
A supplier's notice says its castings will ship three weeks late. Ryan finds every approved change order that depends on that supplier and re-runs each one against the notice. The notice moves them to deferred with one exception it names, and Ryan states that exception in the thread so the chair can see it was applied on purpose. Ada then checks the schedule lines for those changes and proposes the corrections.
A cancellation is quieter and easier to get wrong. When a change is canceled, another change that was marked as its duplicate is no longer a duplicate of anything. Ryan re-runs it on its own record as if the canceled change had never been named, rather than letting the duplicate status carry over. The two list items that are not change orders stay untouched through every step, and every agent turn that wrote to ClickUp keeps a run history the chair can open later.
What the checks catch
- A disposition copied from the neighboring change order instead of decided on its own record
- A list item that is not a change order, swept into the board's decisions
- A change still marked as a duplicate of a change that has since been canceled
- An approved change left on its old effective date after its supplier slipped
- A schedule corrections comment posted twice, or with a count different from the one approved
What stays with people
- Approving every disposition and effective date before ClickUp changes
- Deciding escalated change orders, which stay with the VP and the board chair
- Confirming revised supplier dates with the supplier before anyone relies on them
- Signing the week's closing comments
Integrations in this workflow
Kylon is not a PLM system and it does not replace one. It works across the tools engineering and supply chain already use and keeps the coordination between them in one room.
- Airtable
- ClickUp
- Google Drive
- Outlook
Slack
- ClickUp holds the change orders with disposition, effective date and closing comments
- Airtable holds on-hand quantities of each affected part by revision
- Outlook is where supplier commit dates and supplier notices arrive
- Google Drive keeps the change policy, the implementation schedule and the escalation memo
- Slack is where the plants and buyers outside the room see approved decisions and ask questions
Where to start
Try one product line for one week. Connect the ClickUp list that holds its change orders, and give the room guidelines one rule: every change order is decided on its own record, and the board chair approves every disposition before it is written.
“Each change order is decided on its own record, even when its neighbor looks the same.”
Set it up with your agent
Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.
Set up our engineering change board desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect ClickUp, Airtable, Outlook, Google Drive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the board chair, the design and manufacturing engineers, the supply chain buyers and the VP of engineering. Help me invite them to this Room. 3. Build an ECO Board App with columns Submitted, Board review, Approved and Deferred, one record per change order. Pull in the open change orders from ClickUp and flag any items that are not change orders. 4. For each change order, check completeness, check for duplicates, read on-hand stock from Airtable and read the supplier commit date from Outlook. Compute an effective date and propose a disposition. Show me the ones that fail or conflict. 5. Draft every disposition, effective date and closing comment. Hold all ClickUp writes until the board chair approves each one. For supplier slips, have a buyer confirm the revised date first. For escalations, hold for the VP and the chair together. 6. Write our rules and who approves what into this Room's guideline, including that every change order is decided on its own record. 7. After one clean week, offer to turn the weekly board run into an Automation. Before you start, ask me for our rules one at a time.
Your first company harness. Where humans and agents run your business together.
More Use Cases
View allEquipment Calibration: Every Instrument Cleared or Quarantined on Its Own Record
Each instrument gets its status from its own class, due date and certificate. Agents work Airtable, SharePoint and the lab mail in one Kylon room, plan outside lab visits and handle voided calibrations, and the quality manager approves every status.
Lot Recall Traceback: Each Shipment Traced and Notified, From First Notice to Close
Shipment dispositions, notice batches, the coordinator's notification log and every customer acknowledgment run through one Kylon room. Agents trace each shipment across Airtable and Salesforce, and nothing reaches a customer until a person sends it.