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 Revenue Management
- Who it's for
- District service offices
District service offices
A district office needs to know who owns each application, which service was requested and why a case was returned or completed. Cases give staff one working record for a request. The service definition identifies the work, requirement lines and documents hold the supporting material, and reviewer decisions preserve the outcome against the case revision. The Cases Workspace keeps the board, history and pending decisions in the operator's daily view.
How Land Revenue Management is set up for you
At intake
The operator records the applicant reference, selects the organization and service, and assigns an owner. A draft can hold supporting lines while the request is checked.
During review
The reviewer reads requirement outcomes and verified files, then records approval, return or rejection with a reason. The preparer and reviewer remain distinct.
At delivery
The operator records the response reference and checks execution results. An uncertain attempt stays visible until reconciled.
A district office needs to know who owns each application, which service was requested and why a case was returned or completed. Cases give staff one working record for a request. The service definition identifies the work, requirement lines and documents hold the supporting material, and reviewer decisions preserve the outcome against the case revision. The Cases Workspace keeps the board, history and pending decisions in the operator's daily view.
Choose one office and one frequently requested service. Agree its code and policy reference, then prepare an example application with a citizen reference, a requirement line and a supporting file. Assign an operator and independent reviewer. Walk the case from draft through submission, verification and decision, then record a delivery reference. Repeat with a returned requirement so the team sees how a correction and successor revision are handled.
Before expanding, inspect the case list by service and owner. The office should be able to find work still awaiting documents, reviewer decisions and assigned actions. Review the first delivery trace with the people who resolve provider exceptions, so a failed or unknown result has a named owner. This starting scope makes the process observable without changing the meaning of the underlying service policy.
Features to start with
Roles on the team
- Read Only Analyst
- Reads authorized summaries and aggregates across every table plus the four portal pages. No record creation or editing, no schema or administrative capability.
- Land Revenue Administrator
- Maintains approved configuration: record entry on Public Services, read-only on all operational, review and provenance tables, and access to all four app pages. No schema editing, deletion, bulk operations or export grants.
- Land Revenue Operator
- Prepares assigned work: record entry on Cases, Case Requirements, Case Actions and Case Documents, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.
- Land Revenue Reviewer
- Reviews independent assigned work: record entry on Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.
Set up Land Revenue Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.