Menu

The Keelmore Lab

Try the system. See the next action.

Explore an operations workspace, a customer portal and an order-management view. Then follow individual service, retail and client-project records.

Take over a busy morning

One decision.
Three people see the difference.

A customer is waiting, a detail is missing and Alex’s calendar is already busy. Bring one request through the real decisions—then see what changes for the owner, team and customer.

Example system · synthetic records · local to this page

SC
Services du CanalTuesday, 08:45 · example system

One morning / five records

A little clarity.
A lot starts moving.

01 / 08
Give the request an owner.

Café des Pins is waiting. Choose who will coordinate SR-104.

PersonRequestDecisionActionResult
SR-104 / C-104Access detail missing

“The entrance door catches.”

Café des Pins · Noor

Coordinator
Unassigned
Next action
Assign a coordinator

Someone needs to own the reply.

Action inbox

SR-104 · Café des PinsAssign a coordinatorNeeds an owner · this morning
SR-108 · Atelier du NordReview seasonal-inspection quoteSam · today

One change / three connected views

Try the example. Nothing is sent, booked or saved.

The overview remains readable without JavaScript. Enable it to try the actions.

The useful part isn’t the button. It’s the same verified information reaching the next person.

Discuss a handoff in your business ↗

Step inside a business

Different businesses.
Specific problems to solve.

Four interactive demos. Choose a business, see what is difficult today and try the system that connects the next step.

A workshop owner and a new technician review a job sheet beside a door closer.
Example business scenario

Services du Canal / Interactive demo

The door sticks.
The answer shouldn’t.

SR-104 · Café des PinsAccess detail missingCamille → Coordinates requests

Noor is waiting for an answer. The team has the request, but the access detail and available appointment still need checking.

  • CamilleCoordinates requests
  • AlexCarries out the work
  • NoorRuns Café des Pins

The connection — One reference connects the quote, appointment, technician’s instructions and customer view.

↳ A confirmed visit appears in three places, with the same time and scope.

Try this example ↗
Two colleagues compare a cabinet panel with its drawing and finish sample.
Example business scenario

Atelier du Pin / Interactive demo

A revised size.
A clear production decision.

W-024 · SPEC-v2SPEC-v2 · approval neededWorkshop owner → Reviews the scope

A cabinet order changes from 900 to 1,000 mm. The old drawing is still on the workbench, and one panel is missing.

  • Workshop ownerReviews the scope
  • Production leadChecks materials and the current drawing
  • CustomerApproves the revised specification

The connection — W-024 links the revised specification, customer approval, material receipt and quality check before delivery.

↳ Production waits for the approved version and the missing panel; the old specification cannot release the job.

Try this example ↗
A packing team checks a parcel and a paper order together.
Example business scenario

Maison du Canal / Interactive demo

Three ready.
One still owed.

OR-208 · 4 / 3 / 14 requested / 3 available / 1 outstandingCounter team → Checks the customer decision

An order needs four aprons; only three are available. A partial handover must not make the missing item disappear.

  • Counter teamChecks the customer decision
  • Stock leadReserves and prepares

The connection — An agreed split reserves three. Their handover changes stock and the dashboard from the same order.

↳ The fourth item remains visible, with an outstanding customer commitment.

Try this example ↗
Colleagues organize decisions and documents around a working table.
Example business scenario

Bureau Rivière / Interactive demo

The meeting ends.
The decisions move.

PR-031 · BRIEF-v2N-031 → A-031 + A-032Project lead → Confirms the decisions

The seasonal-service brief is in several documents. Two actions need owners and a current source.

  • Project leadConfirms the decisions
  • ContributorsOwn the next actions
  • ReviewerApproves the current brief

The connection — Meeting N-031 links to actions A-031 and A-032, and the shared BRIEF-v2.

↳ A contributor can find the decision behind the task; a shared draft remains distinct from an approved document.

Try this example ↗

Same request / different clarity

Stop reconstructing
the whole story.

SR-104 is still the same door, customer and work. Explore what changes when the information is connected.

Inbox / no shared owner

“The entrance door catches.”

Noor / Café des Pins

Find the access detail

In a separate reply: side entrance, reception bell. The quote still has the old blank field.

Q-104 / v1

Scope attached.
Approval unclear.

Find the next action

A note says “ask Alex.” No person or due date is assigned to that follow-up.

PROC-104 / v0

“Ask the owner.” Again.

What does the new employee need?

The sequence for checking scope, stopping for a damaged part and confirming the work exists only in the owner’s notes. Alex cannot find an approved version.

Calendar / separate note09:00 ?

Alex is already booked for J-111.

What Keelmore helps organize

Understand the process → connect the useful records → name responsibilities → document the know-how → test it with the team.

SR-104

Café des Pins

Verified source linked
01 / C-104

Current information

Noor’s reply → side entrance + reception bell → Q-104 and job sheet.

02 / Camille

A responsible person

Review scope this morning. Internal approval and customer acceptance remain separate.

03 / J-104

A checked next step

09:00 is occupied. Request 11:00, then confirm capacity before booking.

Explore the notes. The information exists, but each answer lives in a different place.

Make the handoff yourself ↗

Shape your system

Start with the work
you want to connect.

Choose a business and a few sticking points. Build a starting sketch you can download and bring to a conversation. No contact details, saved answers or live connections.

What is hard to keep track of?

The sketch changes as you choose. You can download it without giving us information.

KM / Working sketch

Service team

  1. Request register

    Original request + customer reference

    ◇ A person verifies the request and customer match.
  2. Dated action queue

    Record → responsible person → due date

    ◇ A person reviews the draft before any message.
  3. Named handoff

    Record → owner → next action

    ◇ The receiving person accepts the responsibility.
  4. Human checkpoint

    Verified source + visible exception

    ◇ Uncertain information pauses the next step.
  5. Visible next action

    Decision → action → status shared

    ◇ The team can see what is still outstanding.

Illustrative starting point, not a diagnosis or an implementation quote. Existing tools, permissions and information quality must be reviewed. Check the Blueprint page for scope and price.

Interactive demo / custom-order workshop

A revised order.
One version everyone can trust.

Atelier du Pin is building a counter cabinet. The size changes, an estimate needs approval and a panel is missing. Follow the dependencies through to a checked delivery.

Atelier du Pin / W-024

Counter cabinet / current specification

900 mm
W-024
On hold
SPEC
v1 / 900 mm
EST-024
v1
Approval
Not yet recorded
Panels required / received
3 / 2
Read the revision history

v1: 900 mm wide. Customer request: increase to 1,000 mm. v2 retains the same finish. The revised estimate follows the drawing; production waits for explicit customer approval.

The workbench still has v1. Replace it before requesting approval.

  • Specification & approvalPending
  • Materials / PO-024Pending
  • ProductionPending
  • Quality / QC-024Pending
  • Delivery / D-024Pending
Who acts next?Workshop owner · replace the old specification

3 panels required / 2 received / 1 outstanding. The shortage stays attached to W-024.

Example workflow. Receiving the third panel closes PO-024’s shortage; it does not approve the customer’s scope or mark production complete.

Built around the work

Three systems.
Something useful in each.

These are working example interfaces, with fictional businesses and records. Try the controls: nothing is sent, booked, purchased or saved.

Operations workspace

Every request keeps its next action.

A neighbourhood service team: coordination, technicians and the owner.

Before
Requests, quotes and appointments are spread across notes and inboxes.
Try it
Assign a request, check its details and move it through quoting, scheduling and follow-up. The register, task and schedule agree.
What is clearer
See responsibility, missing information and open work without reconstructing the story.
Service workspace
Connected records.
Clear next steps.
KM / 01

Neighbourhood service team / operations

Work, in motion.

5 open requests. Every next step has a place.

Example system

Work register

RequestOwnerNext actionStatus
——Assign the request Needs an owner
ATAlex · technicianConfirm a time & capacity Ready to schedule
SRSam · technicianCheck work & complete In progress
ATAlex · technicianStart the planned work Scheduled
CLCamille · coordinationReview customer follow-up Follow-up due

Today / sample Tuesday

  1. Equipment serviceBoutique du Canal · Sam · technician In progress
  2. Site visitBureau Rivière · Alex · technician Scheduled

Recent activity

  1. Sam started equipment serviceSR-111 → J-111 · 09:00
  2. Quote accepted; appointment confirmedQ-113 → J-113 · 14:00
  3. Counter repair checked; follow-up openedJ-116 → F-116
SR-104 / C-104

Entrance door adjustment

Café des Pins

Needs an owner
Next actionAssign the request
Owner
—
Quote
Held for verified details
Job
No appointment committed
Open task
T-104

A person confirms this step. No message or booking is sent.

Fictional business & records · changes stay on this page

Make it fit your business

Start with the way your work moves.

Your request fields, team responsibilities, quote checks and scheduling rules, using the tools that fit your business.

The Business Systems Blueprint develops a plan for one workflow with a 35-minute discovery conversation. A clear implementation requirement can be quoted directly.

Customer portal

A customer knows what happens next.

A workshop customer and the service provider coordinating a maintenance visit.

Before
Scope, documents and proposed times arrive in separate messages. A proposed appointment looks confirmed.
Try it
Review the example quote, accept its scope and share availability. Confirmation stays separate from the customer’s request.
What is clearer
One current scope, visible decisions and a shared next step—without another email search.
Customer portal
Connected records.
Clear next steps.
KM / 02

Workshop maintenance / customer view

Your project, clearly organised.

The scope, the documents and the next decision—in one place.

Example system
01WORKBENCHACCESS ROUTEWORKSHOP / PLAN 01

Access point 01 · keep the entrance clear

P-024 / Atelier du Pin · example customer

Workshop maintenance

Project status
Scope ready for review
Next step
Review your quote
  1. Request
  2. Scope
  3. Schedule
  4. Complete

Project documents

Latest updates

  1. Your scope is ready to reviewInspection and entrance adjustment. Review exclusions before accepting.
  2. Access details linkedGround-level entrance · access point 01

Upcoming visit

Time to be confirmed

The provider checks capacity before confirming the time you propose.

Fictional business & records · changes stay on this page

Make it fit your business

Start with the way your work moves.

Your scope documents, approval steps, customer access and visit-confirmation rules. Connections to existing tools are scoped before implementation.

The Business Systems Blueprint develops a plan for one workflow with a 35-minute discovery conversation. A clear implementation requirement can be quoted directly.

Management dashboard

The figures lead back to the work.

The owner, counter staff and stock lead at a neighbourhood homewares shop.

Before
An order can look finished while one item is still missing. Reserved stock is mistaken for available stock.
Try it
Inspect twelve orders, handle a stock exception and confirm a handover. Quantities, totals and the chart update from those same records.
What is clearer
See which promise needs attention and which stock can actually be committed.
Order management
Connected records.
Clear next steps.
KM / 03

Orders, stock & exceptions / management

A clear view of what is open.

Maison du Canal · neighbourhood shop · sample week

Example system
Orders this week
12
Fully fulfilled
6
Units outstanding
15
Stock exceptions
1

The week, at a glance

Orders grouped by received day · current fulfilment status

FulfilledOpen
01232Mon2Tue3Wed2Thu3Fri
Read the chart data
Order counts · same records as the register
DayFulfilledOpenTotal
Mon202
Tue202
Wed213
Thu022
Fri033

An exception worth seeing

OR-208 / Linen apron
Four promised. Three available.
Check stock
Ordered / fulfilled
4 / 0
Reserved for this order
0
Available stock
3

A partial order needs the customer’s agreement. The remaining quantity stays open; availability alone is not approval.

Stock that can be promised

Available = on hand − reserved. Completed handovers reduce on-hand stock.

Linen apron
On hand
7
Reserved
4
Available
3
Canvas tote
On hand
8
Reserved
2
Available
6
Illustrated card
On hand
20
Reserved
4
Available
16
Fictional business & records · changes stay on this page

Make it fit your business

Start with the way your work moves.

Your order stages, stock rules and management indicators, after checking the quality of the source records.

The Business Systems Blueprint develops a plan for one workflow with a 35-minute discovery conversation. A clear implementation requirement can be quoted directly.

Watch the working examples

Operations workspace

Watch, then try it

The next action follows the request.

Assign the request, verify access, review the quote and confirm capacity. Requested and confirmed appointments stay distinct.

Try the working example ↗

Example systems / in motion

29 seconds · narrated, with captions
From request to reviewed instructionsRecorded from the working examples.
Read the narration transcript

Narrated demonstration with captions. The context identifies each example business.

  1. Chapter 3

    Now the request has an owner. Noor's access instructions are linked to the quote and job sheet. Missing information no longer gets lost between them.

  2. Chapter 4

    The scope is checked before the customer approves it. Nine o'clock is occupied. Eleven is available. Confirmation updates the schedule, Alex's instructions and Noor's portal.

  3. Chapter 5

    Next, the owner's notes become a procedure. A person reviews version one, attaches it to the job, and Alex reads it before recording the work checks.

Download captions (VTT)
Customer portal

Watch, then try it

A proposed visit is not yet confirmed.

Scope approval, availability and provider confirmation are distinct decisions. The current document stays beside them.

Try the working example ↗

Example systems / in motion

21 seconds · silent, with on-screen text
From scope review to a confirmed visitRecorded from the working examples.
Read the visual transcript

Silent demonstration with on-screen messages.

  1. Now, the customer’s view.

    Atelier du Pin reviews its scope, documents and next decision in one place. Current information gives the customer a clearer next step.

  2. See the scope. Make the decision.

    Read the work, exclusions and itemized example subtotal before accepting. The decision stays connected to the document.

  3. A proposed visit is not a booking.

    Tuesday morning is requested. The provider still needs to confirm it. A request and a confirmation stay distinct.

  4. Confirmation closes the gap.

    The visit is confirmed. The next step is to prepare workshop access. The customer and team can work from the same status.

Download captions (VTT)
Management dashboard

Watch, then try it

Three handed over.
One still due.

An agreed partial order reserves three aprons. A checked handover changes the stock and outstanding units; the fourth item keeps the order open.

Try the working example ↗

Example systems / in motion

18 seconds · silent, with on-screen text
A partial order keeps its outstanding itemRecorded from the working examples.
Read the visual transcript

Silent demonstration with on-screen messages.

  1. Another business. A stock exception.

    Order OR-208 needs four aprons. Only three are available. Available stock and the customer’s order are shown together.

  2. Agree the partial order first.

    Reserve three, keep the fourth visible. Then check preparation. The exception remains attached to the original order.

  3. A handover updates the shared totals.

    Three items leave stock. One remains due; this order stays open. A partial handover does not hide unfinished work.

Download captions (VTT)
Custom-order workshop

Example systems / in motion

21 seconds · silent, with on-screen text
A revised order moves into productionRecorded from the working examples.
Read the visual transcript

Silent demonstration with on-screen messages.

  1. Link revised specification + estimate v2

    Link revised specification + estimate v2

  2. Record customer approval of v2

    Record customer approval of v2

  3. Check and receive the missing panel

    Check and receive the missing panel

  4. Record production to approved specification

    Record production to approved specification

  5. Verify dimensions and finish

    Verify dimensions and finish

  6. Record the checked delivery

    Record the checked delivery

Download captions (VTT)
Client-service decisions

Example systems / in motion

18 seconds · silent, with on-screen text
A meeting becomes assigned, reviewed workRecorded from the working examples.
Read the visual transcript

Silent demonstration with on-screen messages.

  1. Confirm meeting decisions

    Confirm meeting decisions

  2. Assign both actions

    Assign both actions

  3. Link Brief v2

    Link Brief v2

  4. Mark edits ready for review

    Mark edits ready for review

  5. Approve checked brief

    Approve checked brief

Download captions (VTT)

Example systems / hands on

Change a record.
See what moves with it.

Use the buttons to move the sample work forward. Everything stays in this page; nothing is sent or saved.

Service business

From first request to the next visit.

Dispatch, technicians and the owner.

Before
The enquiry is in an inbox; the quote and job notes live elsewhere. Nobody is sure who follows up.
The system
Link the customer, quote and job. Give each next action an owner and pause work when a detail is missing.
What becomes clearer
The team can see who owns the request, what blocks it and what still needs attention.
KM / Service operationsExample system
  1. Enquiry
  2. Customer
  3. Quote
  4. Schedule
  5. Completion
  6. Follow-up

SR-104 ↳ Café des Pins · example

Entrance door catches

Email → request register

Owner
Unassigned
Status
New request
Site access
Missing · quote paused
Appointment
Not confirmed

Next actionAssign someone to review the request.

Work queue

0

Assign the request to create its review task.

CustomerC-104After review
QuoteQ-104Blocked
JobJ-104Not scheduled
Linked customer and service history

C-104 keeps the original request, site-access note and approved scope together. Scope: inspect and adjust the latch; replacement parts need separate approval.

Service history: no completed job recorded yet.

Try assigning the request. Watch the owner and task queue change.

The path through this example

Enquiry → customer → quote → job → follow-up

The team can see who owns the request, what blocks it and what still needs attention.

Retail & orders

An order keeps its outstanding items.

Counter staff, stock and preparation teams.

Before
A paper order promises four items, but only three are on the shelf. Staff need a shared answer before preparing it.
The system
Check stock, record the split-order decision and connect preparation to the customer update.
What becomes clearer
Available, reserved and outstanding quantities stay distinct. A partial handover does not close the order.
KM / Orders & inventoryExample system
  1. Order
  2. Stock
  3. Preparation
  4. Fulfilment
  5. Customer update

OR-208 ↳ Comptoir du Quartier · example

Four linen aprons

Counter order → order register

Owner
Order desk
Status
Order received
Requested / available
4 requested · 3 in stock
Outstanding
1 apron short

Next actionCheck stock for the four requested aprons.

Work queue

1
  1. T-208Check stock for the four requested aprons.Order desk · Before fulfilment
Stock itemLIN-043 available
PreparationPK-208Waiting
FulfilmentFL-208Not handed over
Order lines and the stock decision

LIN-04 · linen apron · 4 ordered, 3 on hand. The fourth unit stays on the order. A split fulfilment requires the customer’s agreement before preparation.

The stock exception stays visible beside the order.

Check stock for the four requested aprons.

The path through this example

Order → stock → preparation → fulfilment → update

Available, reserved and outstanding quantities stay distinct. A partial handover does not close the order.

Client services

The meeting becomes work people can follow.

Project leads, contributors and reviewers.

Before
Decisions sit in notes, tasks lack owners and several versions of the brief circulate.
The system
Connect decisions to assigned actions and one current document. Keep the review separate from the edit.
What becomes clearer
People can find the current brief, the reason for a task and the person needed for the next decision.
KM / Client project workspaceExample system
  1. Notes
  2. Decisions
  3. Actions
  4. Documents
  5. Project status

PR-031 ↳ Bureau Rivière · example

Seasonal service launch

Meeting notes → decision record

Owner
Project lead
Status
Notes captured
Decision
Needs confirmation
Current document
Not linked yet

Next actionConfirm the decisions from the meeting.

Work queue

0

Confirm the decisions to create two actions.

MeetingN-031Notes retained
ActionsA-031 / 0322 to complete
DocumentBRIEF-v2Not linked
Meeting notes beside the current brief

Meeting note: confirm the opening hours before the service launch. Decision: keep the agreed scope. Brief v2 must contain the checked hours and the approved service description.

An edited document does not close an approval task.

Confirm the decisions from the meeting.

The path through this example

Notes → decisions → actions → documents → status

People can find the current brief, the reason for a task and the person needed for the next decision.

Follow the six-stage Keel Line

The Keel Line / one workflow, end to end

Keep the thread.
Through every handoff.

Follow a hypothetical maintenance enquiry. The line connects the work; a person still decides what happens next.

Example system · service business.

KM / 104 · One connected recordExample system
Email / original request“The entrance door catches.”SR-104
  1. C-104Customer record

    Request + site-access note

  2. Q-104Quote workspace

    Verified scope · awaiting approval

  3. J-104Calendar handoff

    Held until acceptance + capacity check

The same reference follows the work. Approval controls the handoff.

SERVICE REQUEST
Human judgment stays in the loop.

Nothing moves forward on a guess.

A practical first stepBusiness Systems Blueprint ↗

Enquiry

A request needs a place to land.

A maintenance request arrives by email.

Where it gets stuck
It can stay in one inbox, invisible to the rest of the team.
What could improve
Capture it once, keep the original and assign a review.
The human decision
A person confirms who owns the next action.

Automate the capture

Review

Missing detail is a signal. Not an invitation to guess.

The team checks the location, type of work and urgency.

Where it gets stuck
“A door needs attention” is not enough to promise a repair.
What could improve
Flag the gap, assign a review and keep the quote paused until the answer is checked.
The human decision
A person checks the reply and decides whether the job fits.

Assist the preparation

Quote

A draft is useful. An approval is essential.

Verified details become a proposed scope and price.

Where it gets stuck
A copied estimate can carry the wrong assumptions into a new job.
What could improve
Prepare a draft from verified facts and approved pricing rules. Make its status explicit.
The human decision
Scope, exclusions, price and wording are approved before sending.

Keep the decision human

Schedule

A possible time is not a confirmed appointment.

An accepted quote moves toward a date in the calendar.

Where it gets stuck
Availability, customer acceptance and team capacity can get separated.
What could improve
Bring the agreed details into the calendar handoff, without another round of copying.
The human decision
A person confirms the appointment with the customer and team.

Connect the handoff

Delivery

The work is done when it has actually been checked.

The team performs the agreed work and records what happened.

Where it gets stuck
A completed task box can hide a missing item or an unresolved exception.
What could improve
Keep the agreed checklist, notes and exceptions together for review.
The human decision
A person verifies the delivered work. The job sheet must match the work actually delivered.

Verify the real result

Follow-up

Leave a next action. Not a loose end.

An unanswered quote or a finished job needs the right follow-up.

Where it gets stuck
Reminders can be forgotten—or keep going after the situation changes.
What could improve
Surface the due action and prepare a message. Stop reminders when the status changes.
The human decision
A person decides whether to send, wait, close the request or ask for feedback.

Make the next step visible

Explore the six service-workflow checkpoints
Try a different starting point

Choose a stage. With a keyboard, use the arrow keys within the stage list.

Stage 01 / 06 · Receive

Give the enquiry a place to land.

Automation may help

Record the request once and prepare an acknowledgement. Keep the original even if an email fails.

Human checkpoint

A named team member reviews the request and decides who should take it on.

With details supplied

The request describes a sticking exterior door and a preferred contact method. Next: check service fit.

When details are missing

“A door needs attention.” No location or useful description. Next: ask for those details; keep the request open.

Stage 02 / 06 · Qualify

Check the fit before making a promise.

Automation may help

Group the supplied details and flag missing fields. A prepared question points to the missing information.

Human checkpoint

Confirm the service area, type of work and urgency. Decide whether more information or a site visit is needed.

With details supplied

For this example, a person confirms the job fits the service. Next: prepare a scoped quote for review.

When details are missing

Fit is unknown. Prepare a request for the location and a description. Quoting waits for a person to review the reply.

Stage 03 / 06 · Quote

A prepared quote is not an approved quote.

Automation may help

Prepare a draft from verified facts and approved pricing rules. Keep its status visible.

Human checkpoint

Approve scope, exclusions, price and wording before anything is sent to the customer.

With details supplied

The owner reviews the draft. Only an approved quote can be sent. Next: wait for customer acceptance.

When details are missing

On hold. No price is guessed and no quote is sent while the job details remain unverified.

Stage 04 / 06 · Schedule

A possible time is not a booking.

Automation may help

Suggest available times using the agreed calendar and prepare the handoff notes.

Human checkpoint

Confirm customer acceptance, team capacity and the appointment before committing the time.

With details supplied

If the quote and appointment are accepted, record the confirmed time and responsible person. No booking happens in this example.

When details are missing

On hold. An incomplete request cannot become a confirmed appointment. Keep the next action with its owner.

Stage 05 / 06 · Deliver

Verify the work before closing it.

Automation may help

Bring the checklist and work notes together for review. Flag unresolved items.

Human checkpoint

Check the actual work against the agreed scope. A status change alone does not confirm delivery.

With details supplied

A person checks the completed maintenance and records exceptions before closing the job. This is an illustrative decision, not a real service record.

When details are missing

The request is still on hold. No work is assumed to have happened and nothing is marked complete.

Stage 06 / 06 · Follow up

Leave a next action, not a loose end.

Automation may help

Surface an unanswered quote or a due check-in, with a draft message for review. Stop reminders when the state changes.

Human checkpoint

Decide whether a message is appropriate. Confirm actual delivery before closing the work or asking for feedback.

With details supplied

The next action depends on the real status: follow up on a quote, check an appointment or review completed work. Nothing is marked complete automatically.

When details are missing

Review the unanswered request for details. Choose a reasonable follow-up or close it deliberately; do not keep sending reminders.

The exceptions matter.

A duplicate arrives

Hypothetical control: retain the original request identifier and link the repeat attempt. Test that retrying creates no second message or appointment. A provider’s behaviour must be checked.

A copied draft adds an unapproved promise

Hypothetical exception: the draft promises a replacement part absent from the approved quote. Hold the draft, compare it with the source and ask the responsible person. Never send it automatically.

The workflow should not be automated yet

Hypothetical decision: the team cannot agree who approves a quote. Start with a named approver and a shared checklist. Automating an unresolved responsibility would reproduce the problem.

Explore freely: this example does not send messages, book appointments or save your choices.

Bring it back to your business

Which handoff needs
a clearer next step?