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.
- Beneficiary Tracking
- Data Model
The tables behind Beneficiary Tracking
Beneficiary Tracking ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 14
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Service Registration
Service applications connects each request to Organizations, People and public services. Number, citizen reference and Revision identify the working case and revision context.
Requirements and Evidence
Application requirements uses Parent to reference service applications. Evidence documents uses Source for the application and verified by for People.
Independent Review
Review decisions retains Source, source revision and Reviewer with Decision, Reason and evidence reference.
Service Delivery
Operation runs uses Source for the application. Operation steps uses Run for its parent execution run. Execution attempts refers to the application through Source and retains operation key for execution correlation.
Follow-up and Corrections
Follow up actions connects Source to the application and assigned to to People. State history retains Source, Actor and source revision for recorded state changes.
Service Configuration
Public services and People reference Organizations. Source mappings references public services through Definition. Users carries account fields and its User reference to Users.
Every table, by feature
- Service Registration5
- Requirements and Evidence4
- Independent Review5
- Service Delivery5
- Follow-up and Corrections8
- Service Configuration5
- Service applications
Requests, applications and cases submitted for a public service.
Linked to Organizations, People, Public services - Organizations
Agencies, departments and service organizations that own public services and cases.
- People
Staff, officers, reviewers and assigned team members.
Linked to Organizations - Public services
Published service definitions, programmes and entitlements offered by an organization.
Linked to Organizations - State history
Immutable workflow-written status transition history for each case.
Linked to Service applications, People
- Application requirements
Observation-level requirement, document and line detail captured against a service application.
Linked to Service applications - Evidence documents
Uploaded and verified supporting documents and source evidence.
Linked to Service applications, People - Service applications
Requests, applications and cases submitted for a public service.
Linked to Organizations, People, Public services - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations
- Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Service applications, People - Service applications
Requests, applications and cases submitted for a public service.
Linked to Organizations, People, Public services - Application requirements
Observation-level requirement, document and line detail captured against a service application.
Linked to Service applications - Evidence documents
Uploaded and verified supporting documents and source evidence.
Linked to Service applications, People - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations
- Service applications
Requests, applications and cases submitted for a public service.
Linked to Organizations, People, Public services - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Service applications, People - Operation runs
Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Linked to Service applications - Operation steps
Ordered steps inside an operation run with input, output and external receipt state.
Linked to Operation runs - Execution attempts
Each recorded attempt to execute an approved action for a service application.
Linked to Service applications
- Follow up actions
Assigned outstanding actions, corrections and outstanding requests for a case.
Linked to Service applications, People - Service applications
Requests, applications and cases submitted for a public service.
Linked to Organizations, People, Public services - State history
Immutable workflow-written status transition history for each case.
Linked to Service applications, People - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Service applications, People - Operation runs
Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Linked to Service applications - Operation steps
Ordered steps inside an operation run with input, output and external receipt state.
Linked to Operation runs - Evidence documents
Uploaded and verified supporting documents and source evidence.
Linked to Service applications, People - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations
- Public services
Published service definitions, programmes and entitlements offered by an organization.
Linked to Organizations - Organizations
Agencies, departments and service organizations that own public services and cases.
- People
Staff, officers, reviewers and assigned team members.
Linked to Organizations - Users
Users
Linked to Users - Source mappings
Reviewed field mappings and transform rules between source payloads and target fields.
Linked to Public services
Keys and references
Preserve existing identifiers when importing related data. Application requirements.source record id is required alongside Parent; the beneficiary’s citizen reference is a text value on the application and requirement records. It is separate from a staff reference to People. Service applications.Definition points to public services, while service code is a text value that needs an agreed mapping.
Trace operation steps to operation runs through Run. Match execution attempts to the application and its operation using Source and operation key. Review decisions and state history retain source revision so staff can identify the revision behind a decision or state change. Preserve that revision context when migrating corrected cases.
Migration order
- Organizations. Establish the agency identifiers and service ownership before importing dependent records.
- People and Users. Load staff and account information, then configure the identity mapping and access scope used for assigned work.
- public services and source mappings. Establish service definitions, policy references and reviewed field transformations.
- service applications. Import applications with their Organization, Owner and Definition references intact.
- application requirements and evidence documents. Resolve Parent, Source and verified by references before handing cases to review.
- review decisions and follow up actions. Preserve reviewed revisions, assignees and the original decision or resolution information.
- operation runs, operation steps, execution attempts and state history. Preserve observed execution and state history through a controlled migration; do not generate past success or approval records from current status labels.
Set up Beneficiary Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.