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
- Central service teams
Central service teams
A central public service team may maintain common service definitions while individual organizations own their cases. The organization and service references on a case make workload visible without turning a title into a routing rule. People records identify staff and their organizations. The administrator maintains approved service definitions; operators handle applications; reviewers make independent decisions on the revision they receive.
How Land Revenue Management is set up for you
Common definitions
Use service codes, effective dates and policy references to keep the intended service clear when offices share a similar label.
Local ownership
An owner remains named on every case, and an assigned action identifies who must resolve a correction.
Central oversight
Status, requirement outcomes and reviewer decisions can be read by authorized analysts across the service workload.
A central public service team may maintain common service definitions while individual organizations own their cases. The organization and service references on a case make workload visible without turning a title into a routing rule. People records identify staff and their organizations. The administrator maintains approved service definitions; operators handle applications; reviewers make independent decisions on the revision they receive.
Start with one service used by two offices. Confirm each organization's code and staff membership, then enter representative cases with different owners. Have each operator submit an application with requirement lines and documents. Ask the reviewer to return one for correction and approve the other. The decision records should identify which revision was examined and the reason for each outcome.
Use the service workload and case status reports to compare the offices' open work. Review actions past their due dates and runs requiring reconciliation. When a source system supplies case details, test a small set of field mappings with the service owner. A mapping version should be reviewed before it becomes part of routine intake. Expand to additional services only after staff can explain the correction path and find the result for a delivered case.
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.
- Admin
- Maintains user access and coordinates configuration with the responsible service owner.
Set up Land Revenue Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.