Humans
The person, the role and the decision.
DAFFY / EXAMPLE THREAD
Open the thread A shift needs cover. The supervisor sees the roster and makes the call.
THE WORKFLOW LIBRARY
One event.
The work around it.
Follow seven everyday SOPs across teams and workspaces. See the source, the proposed action and the decision that stays with a person.
02 / FROM INSTRUCTION TO ACTION
From your SOP.
To work done.
Daffy carries the instruction into action, then tracks the result. An approval authorises the work; confirmation tells you what actually happened.
- 01
Data arrives
An event, request or scheduled check brings the relevant record into view.
Camera 02 flags an observation. - 02
Daffy applies your SOP
She connects the evidence, standing instructions and affected work.
Batch B-2291 and PO-8841 are linked. - 03
Resolve the authority
She acts within agreed permissions and requests approval where your SOP requires it.
The quality supervisor reviews the hold. - 04
Execute the action
Daffy updates the system, assigns the task or triggers the permitted action.
The approved hold updates the batch record. - 05
Confirm the result
The returned status distinguishes completed actions from work still pending.
Dispatch sees the hold and keeps the batch back.
ONE EVENT. THE WORK AROUND IT.
Watch the handoffs.
Keep the decision in view.
Choose an example to trace the signal, evidence, approval and follow-up across workspaces.
ILLUSTRATIVE WORKFLOW / 01
One inspection. A connected response.
THE HUMAN GATE / Quality supervisor
Try the interactive workflow The supervisor decides whether to hold the batch. A separate quality release is still required before held material can move.
This walkthrough illustrates sequence, not processing speed or live execution.
- 01
- 02
- 03
- 04Inventory & Stores
Carry the decision into stock
Record the approved hold against the affected batch.
- 05Dispatch & Loading
Update the shipment context
Keep the affected material pending; show the dispatch team why.
- 06Customer Support Desk
Prepare the next conversation
Give the account owner the context for a customer update.
ILLUSTRATIVE WORKFLOW / 02
A machine event becomes planned work.
THE HUMAN GATE / Production manager
Try the interactive workflow The production manager approves the proposed service window. Site permits and equipment isolation remain separate operational checks.
This walkthrough illustrates sequence, not processing speed or live execution.
- 01IoT, Sensors & Machines
Receive the machine event
Associate the configured threshold with its tool or asset.
- 02Maintenance & Asset Health
Read the service history
Bring the running history and previous work into the task.
- 03Production Floor
Check the operating plan
Identify a proposed window around the current production run.
- 04Maintenance & Asset Health
Approve the service window
Put the proposed work in front of the production manager.
- 05Inventory & Stores
Check the supporting materials
Link the parts and consumables needed for the agreed work.
- 06
ILLUSTRATIVE WORKFLOW / 03
An absence reaches the people it affects.
THE HUMAN GATE / Shift supervisor
Try the interactive workflow The supervisor checks availability and approves cover. The original attendance exception remains open for the employee’s explanation.
This walkthrough illustrates sequence, not processing speed or live execution.
- 01
- 02
- 03
- 04
- 05DAFFY Chat & Authority
Notify the responsible teams
Carry the approved assignment to both supervisors.
- 06Payroll & Statutory
Preserve the original exception
Keep the attendance record available for later review.
ILLUSTRATIVE WORKFLOW / 04
An inbox message becomes owned work.
THE HUMAN GATE / Project lead
Try the interactive workflow The project lead controls scope acceptance and assignment. Professional review and client delivery have their own approval gates.
This walkthrough illustrates sequence, not processing speed or live execution.
- 01
- 02
- 03
- 04
- 05Client Portal
Prepare the acknowledgement
Keep the client communication linked to the accepted instruction.
- 06Billing & Collections
Retain the commercial context
Connect the agreed scope to the later billing record.
ILLUSTRATIVE WORKFLOW / 05
The shipment knows what quality knows.
THE HUMAN GATE / Dispatch lead
Try the interactive workflow Approving a staging plan does not release a batch on quality hold. That decision stays with the quality owner.
This walkthrough illustrates sequence, not processing speed or live execution.
- 01
- 02
- 03Quality & Inspection
Check the open decisions
Make unresolved quality reviews visible before staging.
- 04Dispatch & Loading
Approve a safe staging plan
Keep held material pending and prepare the cleared stock.
- 05
- 06Customer Support Desk
Prepare an accurate update
Give the customer owner the same order and exception record.
ILLUSTRATIVE WORKFLOW / 06
The payment conversation has its evidence.
THE HUMAN GATE / Finance lead
Try the interactive workflow The finance lead approves a clarification draft. This action does not authorise a payment, refund or change to bank details.
This walkthrough illustrates sequence, not processing speed or live execution.
- 01
- 02
- 03Finance & Accounts
Check the outstanding item
Make the missing evidence and responsible owner visible.
- 04
- 05DAFFY Chat & Authority
Use the agreed channel
Carry the approved response into the communication workflow.
- 06Command Centre
Keep the decision recorded
Leave an accessible history for the next person handling the invoice.
ILLUSTRATIVE WORKFLOW / 07
The follow-up starts with the whole story.
THE HUMAN GATE / Sales lead
Try the interactive workflow The sales lead approves the owner assignment. External outreach and commercial commitments follow the organisation’s separate rules.
This walkthrough illustrates sequence, not processing speed or live execution.
- 01
- 02
- 03
- 04
- 05
- 06
BEYOND THE COMPANY BOUNDARY
The work continues.
So does the context.
An order does not stop at your organisation chart. Neither should the workflow.
Coordinate the next step with customers, suppliers and logistics partners through agreed channels. Share the information needed for the handoff, without opening up your internal operation.
Try the customer-update threadEXAMPLE / A CUSTOMER ASKS ABOUT AN ORDER
- INSIDE YOUR COMPANY
Daffy checks the dispatch record.
The order status and unresolved item stay linked to the request.
- AT THE APPROVAL GATE
The account owner reviews the reply.
Your team controls the information authorised for the customer.
- THROUGH THE AGREED CHANNEL
Daffy sends the authorised update.
The service record retains the reply and its delivery outcome.
A handoff is not blanket access. Each company keeps its own data and authority boundaries. This website demonstrates the approval, not a live message delivery.
THE PHYSICAL WORLD, IN THE CONVERSATION
Humans. Machines.
Robots. Spaces.
Each brings a different kind of context. Daffy connects it to the instruction, the responsible person and the next step.
Machines
A signal with operating context.
DAFFY / EXAMPLE THREAD
Open the thread A tool event connects its history, service owner and the production plan.
Robots
An execution endpoint, with controls.
DAFFY / DEVELOPING CONCEPT
Open the thread A developing concept: approved tasks, local device checks and completion feedback.
Spaces
The location becomes part of the record.
DAFFY / EXAMPLE THREAD
Open the thread A receiving bay, a delivery and its missing reference belong in the same thread.
FROM SOP TO A WORKING SCOPE
Start small.
Connect what comes next.
Agree the first useful outcome, then add workspaces and handoffs as the operating process grows.
Map
Choose the recurring process, the trigger and the exception it must handle.
Connect
Agree the source records, systems, data boundary and permissions.
Rehearse
Run representative cases, missing data, rejected approvals and recovery steps.
Operate
Confirm acceptance, monitor the work and agree the next useful connection.
BEFORE THE FIRST WORKFLOW
The questions
behind the decision.
Does unlimited mean everything is already built?
The 50 catalogue workspaces are starting points. Your teams can shape additional workspaces and workflows around their operating needs. The scope, effort and availability of each capability are agreed for your deployment.
Do we have to replace our current systems?
Start by identifying which systems own your records. The first workflow can connect to those sources, with permitted reads, writes and failure handling defined during scoping.
Does everything need a prompt?
A workflow can start from an event, scheduled check or request. The conversation helps a person inspect the context and make the decisions assigned to them.
Where does human approval belong?
Set a named owner at the points that create commitments, release work or handle exceptions. Reading context, preparing a draft and authorising its execution are separate permissions.
What can I try on this website?
The desks, threads, approval states and workflow examples use authored scenarios. The planner prepares a brief. No live enterprise systems or models are connected, and the enquiry form opens an email draft.
How is the first implementation scoped?
Bring one SOP and representative examples, including exceptions. Agree the required records, approval owners, deployment boundary and acceptance checks before moving to a connected rollout.
START WITH ONE WORKFLOW
Bring the SOP.
Let’s map the first step.
The trigger, the people, the systems and the decisions that matter.