These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Waste Management / Scrap
- Features
- Field Evidence
Field Evidence
Record who performed the work, what happened and the quantity and unit used on site.
OverviewField Work Log×
Waste Management / Scrap · Field Evidence
New
Field Work Log
Work logs
| Work log ID | Work order | Person | Recorded at | Description | Quantity | |
|---|---|---|---|---|---|---|
| WLI-350 | WO-9290 | 15 Oct | Log 1 | 380 | ||
| WLI-985 | WO-8469 | 05 Oct | Log 2 | 710 | ||
| WLI-542 | WO-6649 | 13 Oct | Log 3 | 710 | ||
| WLI-454 | WO-1531 | 04 Oct | Log 4 | 70 | ||
| WLI-669 | WO-9614 | 07 Oct | Log 5 | 310 |
6 of 6 records
WLI-350Work logs · WL-16315
Work orderWO-9290
Recorded at15 Oct
DescriptionLog 1
Quantity380
UnitUNT-932
What you can do
Capture the activity against the selected order
A field log explains the actual work behind a waste operation. Operations Officer records the description, quantity and unit against the selected work order. The person link and recorded date give Operations Reviewer a way to follow the entry back to the operator and the operating context.
Keep the quantity’s unit with the observation. A mass recorded in kilograms and a count of containers describe different things, even when their numerical values happen to match. Reports should preserve that distinction when the team compares field activity across orders or sites.
The authorized work action resolves the acting user through the people record. This makes attribution part of the work path rather than a name typed into a description. A corrective action also appends an attributed work log to the same order, allowing the team to distinguish the original observation from the later correction.
How the work is organized
- Selected work. Operations Officer starts from the assigned order and records the activity that actually occurred. The description should make the entry understandable to someone reviewing the work later.
- Measured context. Quantity and unit travel together. Operations Manager agrees the operating vocabulary so the reviewer can compare like quantities without guessing what a number represents.
- Repeat protection. Workflow actions use their operation identity when writing work logs. A repeated command must follow its guarded repeat path rather than append another account of the same activity.
What to agree during setup
Agree how operators describe a collection, transfer preparation or corrective visit. Keep descriptions factual enough for Operations Reviewer to understand the action. Choose unit labels the team can use consistently, including the difference between material mass and container count.
If a weighing device supplies a measurement, arrange that connection or the agreed entry procedure during setup. Confirm who checks the recorded quantity before the evidence is submitted. Do not make the operator guess how a device reading should map into the work log. The responsible person should also know how to report a mistaken entry without rewriting previously submitted evidence.
Check the handoff on an actual case
Use an authorized offcut collection order and record a sample quantity of 240 kilograms. Operations Reviewer should be able to identify the operator, recorded date and parent order from that entry. Add a separate activity described as moving two containers, using the agreed count unit, and confirm that the report does not add those numbers to the material mass.
Repeat the original authorized command in the rehearsal and inspect the resulting log history. The repeat must not create another quantity for the same action. Next, raise an exception explaining an incorrect observation and follow its corrective work log. Both the original event and the correction should remain understandable under the same order.
What your team sees
- Field Work Log — Recorded activity with its operator, quantity and unit.
- My Work Orders — The assigned parent work to use before recording an observation.
- Exception Queue — Issues that need a reasoned correction or evidence follow-up.
Follow the work through
Use authorize and execute work for capture and resolve an exception for corrective evidence.
What it keeps track of
Data model- Work logs
- Field work log entries recorded against a work order.
- Work orders
- Authorized waste collection, processing and disposal work orders.
- People
- Staff and operators who perform and review waste operations work.
- Users
- Users
- Exceptions
- Operational exceptions raised against work orders and their resolution.
Who uses it
Permissions- Operations Officer
- Records assigned activity.
- Operations Manager
- Handles authorized work and corrective requests.
- Operations Reviewer
- Inspects evidence.
- Finance Officer
- Reads the work context when checking charges.
Set up Waste Management / Scrap your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.