Service configuration

The Land Revenue Administrator maintains the service definition used when an operator opens an application. Each service belongs to an organization and has a code, effective dates and a policy reference. People records identify staff and their organization. This structure lets the team distinguish a request for one service from another without inferring it from a free-text case title. For an office receiving land-related service requests, the definition can identify the service being requested while the case holds the individual application.

An organization can keep its own location, time zone and currency. Staff are linked to that organization. The administrator should check that the service is active and that its effective dates cover the intended intake period. A wrong definition at intake will follow the case into review and reporting, so this choice deserves a deliberate check before submission.

• Organization ownership. A service belongs to an organization; cases and people also point to an organization.
• Service identity. A name and code identify the definition selected for a case.
• Staff assignment. People records supply the owner and reviewer references used as work moves forward.

Decide which organization owns each service and who may maintain its definition. Agree how service codes relate to the references citizens already use. Record the policy reference that the team will consult during review. Agree when a definition becomes effective and who checks that an older definition remains understandable for earlier cases. Assign operators and reviewers as separate people so an independent decision has a clear owner.

If a source system provides service details, agree its field mapping before import. A mapping names the source field, target field, type and transform rule. Review a real sample rather than assuming that two similarly named codes have the same meaning. Keep the mapping version and effective date with the definition.

Suppose a district office receives an application concerning a land-related public service. The administrator first checks that the office is active and that the service definition has the expected code and policy reference. The operator selects that definition when opening the case and assigns an owner in the same office. The reviewer sees the service and organization before deciding the case. If the application later needs correction, the team can still tell which service definition the original revision used.

Ask the administrator to demonstrate a service whose effective period has ended, then show how the operator identifies the intended current service. Ask the reviewer to explain which policy reference governs the decision. These checks keep configuration choices from becoming unexplained case outcomes.

• Active service definitions — Services available for an organization’s current case intake.
• Cases awaiting intake — Draft applications with their organization, service and owner.

• Case intake and submission shows where the definition enters the case.