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
- Configuration and oversight
Configuration and oversight
Keep governing definitions and the case trail understandable.
OverviewActive landowner definitions×
Land Acquisition Tracker · Configuration and oversight
New
Active landowner definitions
Landowners
| Name | Code | Organization | Effective from | Effective to | Policy reference | |
|---|---|---|---|---|---|---|
| Landowner 201 | CDE-515 | ORG-4577 | 12 Oct | 16 Oct | PR-768 | |
| Landowner 991 | CDE-605 | ORG-6801 | 07 Oct | 15 Oct | PR-350 | |
| Landowner 805 | CDE-134 | ORG-9326 | 15 Oct | 21 Oct | PR-289 | |
| Landowner 316 | CDE-205 | ORG-7515 | 16 Oct | 20 Oct | PR-333 | |
| Landowner 502 | CDE-598 | ORG-4090 | 13 Oct | 18 Oct | PR-782 |
6 of 6 records
Landowner 201Landowners · LND-28476
CodeCDE-515
OrganizationORG-4577
Effective from12 Oct
Effective to16 Oct
Policy referencePR-768
What you can do
Keep governing definitions and the case trail understandable.
The administrator maintains landowner definitions with a code, organization, effective dates and policy reference. Source mappings can record how an incoming field relates to a target field, including version and transform rule. People and organizations identify the accountable owner and reviewer. Analysts can inspect parcel status, review outcomes, follow-up dates and state changes without changing operational records.
An active definition belongs to an organization and can carry effective dates and a policy reference. The administrator checks that context before the operator selects it for a parcel. An analyst can then compare the parcel status with its review and state history. A source mapping is reference context for imported values; it does not change the case by itself.
How the work is organized
- Maintain the definition. Check its code, organization and effective period.
- Match the owner. Confirm the selected person belongs to the parcel organization.
- Inspect the trail. Read state changes and reviewer decisions by parcel revision.
What to agree during setup
Agree the code system for landowner definitions and which organization owns each one. Record the effective period before operators choose a definition for a parcel. If source mappings are used, review versions and transformation rules with the team that owns the incoming data. Access decisions should distinguish the administrator, operator, reviewer and analyst roles.
Agree who checks that a definition is active and within its effective period. The administrator can maintain that definition, while the operator selects it for a parcel. Review source mapping versions as setup context before incoming values are used. Rehearse how an analyst finds the policy reference from a selected case.
Check the handoff on an actual case
Open an active definition and confirm that its organization and effective dates fit a new parcel. Check that the selected owner belongs to the intended organization. After the parcel moves through review, inspect state history by revision and compare the reviewer decision with the operation result. A reported status should be explainable from those linked records.
For an audited parcel, compare the recorded state change with its review decision and operation result. Check which definition code and effective dates applied at the time. A current active flag alone cannot explain an earlier decision; the analyst needs the dated definition and source revision alongside the recorded case history.
What your team sees
- Active landowner definitions — Shows the administrator which definitions can be selected.
- Parcel status board — Opens parcels by status for review against the case history.
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- Landowners
- Published service definitions, programmes and entitlements offered by an organization.
- Source mappings
- Reviewed field mappings and transform rules between source payloads and target fields.
- Organizations
- Agencies, departments and service organizations that own public services and cases.
- People
- Staff, officers, reviewers and assigned team members.
- Acquisition parcels
- Requests, applications and cases submitted for a public service.
- State history
- Immutable workflow-written status transition history for each case.
Who uses it
Permissions- Land Acquisition Tracker Administrator
- , Land Acquisition Tracker Operator, Land Acquisition Tracker Reviewer, 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.