Progress Events
The Progress tab on a Work Order lets your team log real-time updates at every stage of the shipment — from pickup through final delivery. Each update is stored as a progress event with a timestamp, structured metadata, and an optional photo.
Opening the Progress Tab
Section titled “Opening the Progress Tab”- Open any Work Order from the Work Orders list.
- Click the Progress tab at the top of the detail page.
You need Update permission on the Work Orders menu to add or delete progress events.
Adding a Progress Event
Section titled “Adding a Progress Event”Click Add progress event to open the event form. Every event requires:
| Field | Required | Description |
|---|---|---|
| Step | Yes | The stage this event belongs to |
| Date | Yes | Date and time the event occurred (in your tenant timezone) |
After choosing a Step, additional fields specific to that stage will appear.
Progress Steps
Section titled “Progress Steps”General
Section titled “General”Use General for any update that doesn’t fit another step — internal notes, status changes, or free-form notifications.
| Field | Required | Description |
|---|---|---|
| Title | Yes | Short title for the event |
| Description | No | Detailed notes |
| Location | No | Where this event occurred |
Pickup
Section titled “Pickup”Records the goods pickup from the shipper’s premises.
| Field | Required | Description |
|---|---|---|
| Fleet (Vehicle) | Yes | Select a vehicle from your Fleet list, or choose “No vehicle” |
| Driver Name | Yes | Full name of the driver |
| Driver Phone | Yes | Contact number for the driver |
| Pickup Address | Yes | Full address where goods were collected |
Warehouse
Section titled “Warehouse”Records arrival or departure at a warehouse or Container Freight Station (CFS).
| Field | Required | Description |
|---|---|---|
| Warehouse Name | Yes | Name of the warehouse or CFS facility |
| Receipt / Ref. No. | No | Warehouse receipt or reference number |
Customs
Section titled “Customs”Records a customs-related milestone — submission, examination, or clearance.
| Field | Required | Description |
|---|---|---|
| Document Type | No | PIB, PEB, BC 2.3, SPPB, BC 1.1, or Other |
| Document Number | Yes | The customs document number |
| Clearance Office (KPPBC) | No | The customs office handling this clearance |
Transit
Section titled “Transit”Records the goods being loaded onto a vessel or aircraft for transport.
| Field | Required | Description |
|---|---|---|
| Vessel / Flight | Yes | Vessel name (e.g. MV Tanto Ceria) or flight number (e.g. GA-304) |
| B/L or AWB No. | No | Bill of Lading or Air Waybill number |
| Container Number | No | Container ID (e.g. TCKU1234567) |
Delivery
Section titled “Delivery”Records the out-for-delivery handover to the last-mile carrier or driver.
| Field | Required | Description |
|---|---|---|
| Fleet (Vehicle) | Yes | Select a vehicle, or choose “No vehicle” |
| Driver / Operator | Yes | Name of the driver or delivery operator |
Proof of Delivery (POD)
Section titled “Proof of Delivery (POD)”Records final delivery confirmation and receipt by the consignee.
| Field | Required | Description |
|---|---|---|
| Received By | Yes | Full name of the person who received the goods |
| POD Reference No. | No | Receipt or signature reference number |
| Goods Condition | No | Good – no damage / Damaged / Partial delivery |
| Delivery Photo | No | Photo evidence of the delivered goods (image file) |
Viewing the Event Timeline
Section titled “Viewing the Event Timeline”All recorded events are listed in reverse chronological order (newest first). Each event card shows:
- Step badge (color-coded by stage)
- Title and description
- Date & time in your tenant timezone
- Metadata (structured fields for that step)
- Delivery photo thumbnail (POD step only)
- Location if recorded
- Recorded by (user name) and when it was saved
Deleting a Progress Event
Section titled “Deleting a Progress Event”Each event card has a delete button (trash icon). Deletion is immediate and cannot be undone.
Only users with Update permission can delete progress events.