Workflow Template
Material delivery and damage check Workflow
Captures site/yard material deliveries, checks condition against the delivery docket, and manages supplier issue resolution (replacement, credit, or dispute) through to closure.
This workflow is designed for construction, trades, and yard-based businesses that receive regular material deliveries from suppliers and need a consistent way to check condition against the delivery docket. It automates the intake of delivery details, branches the process based on whether items arrived correct or with an issue, and manages supplier claim resolution through replacement, credit, or dispute until the delivery record is closed. The result is a clear, timestamped record of every delivery's condition and resolution status, without relying on scattered emails or paper dockets.
Business Outcomes
- Faster identification of damaged, short, or incorrect deliveries at the point of receipt
- Reduced back-and-forth with suppliers through a structured claim and resolution record
- Improved visibility into open supplier issues via status tracking on each delivery record
- Clearer accountability for purchasing and operations tasks tied to unresolved claims
- Fewer delivery disputes falling through the cracks with defined follow-up tasks and due dates
Workflow Steps
Steps
- 1Create Delivery Recordcreate record
Registers the submitted delivery details as a new delivery record.
- 2Set Status to Receivedupdate record
Marks the delivery as Received upon intake.
- 3Route on Delivery Condition
Branches based on whether the delivery arrived all correct or with an issue.
condition: "All correct"→Set Status to Acceptedcondition: "Short delivered"→Set Status to Supplier Issuecondition: "Damaged"→Set Status to Supplier Issuecondition: "Wrong items"→Set Status to Supplier IssueDefault→Set Status to Supplier Issue - 4Set Status to Acceptedupdate record
Marks the delivery as Accepted since it arrived all correct.
- 5Set Status to Supplier Issueupdate record
Marks the delivery as Supplier Issue due to a short, damaged, or wrong delivery.
- 6Notify Receiver Issue Loggedsend email
Emails the receiver to confirm the delivery issue has been logged.
- 7Purchasing: Log Supplier Claimcreate task
Assigns purchasing a task to record the claim lodged with the supplier and its resolution.
- 8Save Claim Details to Recordupdate record
Persists the supplier claim, resolution, and replacement date to the delivery record.
- 9Route on Resolution
Branches based on the resolution recorded by purchasing.
resolution: "Replacement coming"→Set Status to Awaiting Replacementresolution: "Credit issued"→Set Status to Creditedresolution: "Rejected by supplier"→Set Status to DisputedDefault→Set Status to Disputed - 10Set Status to Awaiting Replacementupdate record
Marks the delivery as Awaiting Replacement while the supplier sends replacement items.
- 11Receiver: Check Replacement Deliverycreate task
Assigns the receiver a task with no due date to confirm whether the replacement delivery arrived correct.
- 12Save Replacement Check Resultupdate record
Persists the replacement check result to the delivery record.
- 13Route on Replacement Check
Branches based on whether the replacement arrived correct or is still wrong.
replacement_check: "Correct"→Set Status to Resolvedreplacement_check: "Still wrong"→Return to Purchasing for Further ActionDefault→Return to Purchasing for Further Action - 14Return to Purchasing for Further Actionrestart from step
Closes this iteration and restarts the claim process from the purchasing task since the replacement was still wrong.
- 15Set Status to Resolvedupdate record
Marks the delivery as Resolved once the replacement arrived correct.
- 16Set Status to Creditedupdate record
Marks the delivery as Credited since the supplier issued a credit.
- 17Set Status to Disputedupdate record
Marks the delivery as Disputed since the supplier rejected the claim.
- 18Operations Manager: Record Dispute Outcomecreate task
Assigns the operations manager a task due in 3 days to record the outcome of the disputed claim.
- 19Save Dispute Outcome to Recordupdate record
Persists the operations manager's dispute outcome notes to the delivery record.
Fields
- Receiver Name*
- Receiver Email*
- Job Reference*
- Site Address*
- Supplier*
- Purchase Order Number*
- +11 more fields
Forms
Material Delivery Intake
11 fields
Data Views
Deliveries
supplier, purchase_order_number, delivery_date, condition +2 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
FAQs
Why should we automate material delivery checks instead of handling them manually?
Manual delivery checks often rely on someone remembering to email a supplier or chase a replacement, which can cause issues to sit unresolved for weeks. This workflow captures condition details and photos at the point of delivery, then automatically routes the record into a supplier issue process with assigned tasks and statuses. That structure makes it easier to see which deliveries need attention and reduces the chance of a claim being forgotten.
What is the return on investment of using this workflow for site deliveries?
The workflow reduces time spent tracking down delivery paperwork, chasing suppliers, and manually updating spreadsheets, since each delivery record carries its own status and timeline automatically. Purchasing and operations staff receive assigned tasks instead of ad hoc requests, which helps resolve claims faster and supports better supplier accountability. Over time, this can help reduce the cost and disruption of unresolved delivery issues on active jobs.
How does this compare to tracking deliveries through email and spreadsheets?
Email and spreadsheet tracking typically fragments information across inboxes and files, making it hard to see the current status of a disputed delivery at a glance. This workflow keeps every delivery as a single record with a reference number, status, and full timeline, so anyone checking progress can see exactly where a claim stands. Receivers and purchasing staff interact through assigned tasks and forms rather than searching through email threads.
Who is involved in checking and resolving a delivery issue?
The receiver submits the initial delivery details and photos through a request form, and later confirms whether a replacement delivery arrived correct through a task. Purchasing logs the supplier claim and its resolution, and the operations manager records the outcome of any disputed claims within a 3-day task due date. Each of these tasks is assigned within the workspace and tracked against the delivery record.
What happens if a delivery arrives with a shortage, damage, or wrong items?
The workflow routes the record to a Supplier Issue status and emails the receiver to confirm the issue has been logged. Purchasing is then assigned a task to record the claim lodged with the supplier along with the resolution and any replacement delivery date, and these details are saved to the delivery record. From there, the record moves into replacement, credit, or dispute handling depending on the resolution recorded.
What happens if a replacement delivery is still wrong?
If the receiver's replacement check confirms the items are still wrong, the workflow closes that iteration and restarts the claim process from the purchasing task. This means the supplier claim is logged again with updated resolution details rather than leaving the record stuck in an incorrect status. The record's timeline keeps a history of each iteration as it happens.
How is a disputed supplier claim handled?
When a supplier rejects a claim, the delivery record status is set to Disputed and the operations manager is assigned a task, due in 3 days, to record the outcome. Once completed, the dispute outcome notes are saved directly to the delivery record. This keeps disputed claims visible and time-bound rather than left open-ended.
Can this workflow be customised for our own delivery process?
Yes, the steps can be adjusted by describing the change in plain English or by editing the steps directly in the workflow editor, and earlier versions are kept. This makes it possible to adapt task assignments, statuses, or routing conditions as your delivery and supplier claim process evolves. A workspace can start using the template within minutes and refine it over time without a development project.
What information does the delivery record keep for our own reference?
Each delivery record keeps a reference number, current status, and a timeline of what happened, including the claim details, resolution, replacement date, and dispute outcome entered by staff. This gives a documented history of each delivery's condition and how any issue was resolved. Each business should confirm what records it needs to retain to meet its own obligations.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
