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.
- Land Acquisition Tracker
- Features
- Transfer and execution
Transfer and execution
Keep the documented transfer linked to the approved parcel revision.
OverviewRuns needing reconciliation×
Land Acquisition Tracker · Transfer and execution
New
Runs needing reconciliation
Operation runs
| Source | Name | Operation key | Source revision | Status | Failure reason | |
|---|---|---|---|---|---|---|
| AP-85268 | Run 395 | OK-966 | 340 | Reconciliation required | Cut to length | |
| AP-77912 | Run 328 | OK-202 | 750 | Reconciliation required | Weld frame | |
| AP-76108 | Run 896 | OK-133 | 800 | Reconciliation required | Drill and tap | |
| AP-68786 | Run 210 | OK-976 | 130 | Reconciliation required | Deburr | |
| AP-60810 | Run 127 | OK-811 | 160 | Reconciliation required | Assemble |
6 of 6 records
Run 395Operation runs · OR-17917
Reconciliation requiredSourceAP-85268
Operation keyOK-966
Source revision340
Failure reasonCut to length
What you can do
Keep the documented transfer linked to the approved parcel revision.
After a parcel is decided, the operation run holds an operation key, source revision, input hash and result reference. Ordered operation steps can retain input and output references, external receipt details and receipt evidence. Execution attempts show whether an action was queued, running, succeeded, failed or left unknown. The parcel workspace shows the operation run and step trace next to the case it affects.
The source revision on the run should match the approved review decision. The operation key connects an attempt to its result, while the step receipt explains what the external destination returned. A failed or unknown attempt is still part of the case history. The operator needs to resolve that state before treating the parcel as delivered.
How the work is organized
- Match the decision. Read the approved source revision before taking an action.
- Trace the attempt. Keep the operation key and outcome alongside the source parcel.
- Check the receipt. Inspect the recorded step result before marking delivery complete.
What to agree during setup
Agree which external source supplies a transfer receipt and how its reference enters the step record. Define who reconciles an uncertain attempt and what evidence is required before calling a transfer delivered. The result reference and receipt should identify the same transaction that the approved source revision authorized.
Agree who receives a failed attempt and how the provider reference is checked. A repeated request should be compared with the earlier operation key and result before another transfer is attempted. Rehearse a succeeded attempt and an uncertain one so the team knows which evidence supports delivery.
Check the handoff on an actual case
Take an approved parcel whose transfer action succeeds. The run links back to the parcel and its source revision; the step carries the external receipt identifier and evidence. Check the attempt status and provider reference before marking the parcel Delivered. If an attempt fails or the run needs reconciliation, keep its failure reason visible and assign follow-up rather than repeating the action without checking the operation key.
The receiving person should see the result reference, attempt outcome and any receipt on the same parcel. If a step has an external receipt but the attempt is Unknown, reconcile the two records before changing the parcel status. A later correction must retain the earlier run and receipt so the original transfer can still be explained.
What your team sees
- Runs needing reconciliation — Shows operation keys and reasons for unresolved results.
- Failed execution attempts — Shows attempts whose failure reason needs investigation.
Follow the work through
See the related process and the data model for the linked records behind this handoff.
What it keeps track of
Data model- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
- Operation steps
- Ordered steps inside an operation run with input, output and external receipt state.
- Execution attempts
- Each recorded attempt to execute an approved action for a service application.
- Acquisition parcels
- Requests, applications and cases submitted for a public service.
Who uses it
Permissions- Land Acquisition Tracker Operator
- , Land Acquisition Tracker Administrator, Read Only Analyst.
Set up Land Acquisition Tracker your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.