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.
- Vehicle Registration (RTO)
- Data model and import order
The tables behind Vehicle Registration (RTO)
Vehicle Registration (RTO) ships with 10 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
- 10
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Case Intake:
Cases, Parties, case actions. Each case names its applicant party and the officer it is assigned to.
Document Verification:
Case documents record each document against a case with the verifying officer.
Decisions and Appeals:
Decisions record the outcome, reason, authority reference and reviewer against a case.
Vehicle Registry:
Vehicles hold VIN, plate, class, expiry and the owner party.
Fitness Inspections:
Fitness inspections record the vehicle, inspector, date, result and certificate.
Fee Receipts:
Fee receipts record amount, reference, date and status against a case.
Access:
People link each officer to a platform user in Users.
Every table, by feature
- Case Intake4
- Document Verification4
- Decisions and Appeals4
- Vehicle Registry3
- Fitness Inspections3
- Fee Receipts3
- Shared and settings1
- Cases
Registration, permit and enforcement cases with lifecycle status and assigned officer.
Linked to Parties, People - Parties
Applicants, owners and registered entities that submit registration cases.
- Case actions
Attributed officer actions recorded against a case.
Linked to Cases, People - People
Staff and officers of the registration authority whose authenticated identity is used for attributed actions.
Linked to Users
- Case documents
Evidence documents received against a case and the officer who verified them.
Linked to Cases, People - Case actions
Attributed officer actions recorded against a case.
Linked to Cases, People - Cases
Registration, permit and enforcement cases with lifecycle status and assigned officer.
Linked to Parties, People - People
Staff and officers of the registration authority whose authenticated identity is used for attributed actions.
Linked to Users
- Decisions
Reasoned reviewer decisions with authority reference for a case.
Linked to Cases, People - Cases
Registration, permit and enforcement cases with lifecycle status and assigned officer.
Linked to Parties, People - Case documents
Evidence documents received against a case and the officer who verified them.
Linked to Cases, People - Case actions
Attributed officer actions recorded against a case.
Linked to Cases, People
- Vehicles
Registered vehicle registry with VIN, plate, owner and registration expiry.
Linked to Parties - Parties
Applicants, owners and registered entities that submit registration cases.
- Cases
Registration, permit and enforcement cases with lifecycle status and assigned officer.
Linked to Parties, People
- Fitness inspections
Fitness inspection results and certificates for registered vehicles.
Linked to Vehicles, People - Vehicles
Registered vehicle registry with VIN, plate, owner and registration expiry.
Linked to Parties - People
Staff and officers of the registration authority whose authenticated identity is used for attributed actions.
Linked to Users
- Fee receipts
Fee receipts captured against a case with confirmation status.
Linked to Cases - Cases
Registration, permit and enforcement cases with lifecycle status and assigned officer.
Linked to Parties, People - Parties
Applicants, owners and registered entities that submit registration cases.
Keys and references
Every case keeps a stable case number, every party a reference number, and every vehicle its VIN and plate. Import cases by case number and vehicles by VIN, never by owner name. Resolve duplicate VI ns and plates in legacy data before import. Keep payment references on fee receipts so payments can be traced.
The system holds 10 tables and 14 relationships.
Migration order
- Load Users and People, linking each officer to a platform user.
- Load Parties with reference numbers.
- Load Vehicles with VIN, plate, class, expiry and owner.
- Load open Cases, then case documents and case actions.
- Load recent fitness inspections, fee receipts and Decisions for open cases.
- Reconcile vehicle counts, open cases and pending fees with the source before taking new applications.
Set up Vehicle Registration (RTO) your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.