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.
- RTI / FOIA Management
- Data model
The tables behind RTI / FOIA Management
RTI / FOIA Management 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
- Change it
- Add fields and tables in Proto
How the model is organised
Cases and people
Cases link an Applicant in Parties and assigned to in People; People link to Users.
Case history
Case actions, case documents, Decisions and fee receipts each link to Cases.
Specialty requests
Information requests link to Parties; disclosure reviews link to information requests and People.
Every table, by feature
- Cases
Public records applications tracked from submission to closure.
Linked to Parties, People - Parties
Applicants and requesters who file public records requests.
- People
Staff and officers who act on public records requests.
Linked to Users - Users
Users
Linked to Users
- Case documents
Evidence and supporting documents attached to a case.
Linked to Cases, People - Case actions
Attributed actions performed on a case by an officer.
Linked to Cases, People - Cases
Public records applications tracked from submission to closure.
Linked to Parties, People - People
Staff and officers who act on public records requests.
Linked to Users
- Decisions
Reasoned reviewer decisions issued against a case.
Linked to Cases, People - Cases
Public records applications tracked from submission to closure.
Linked to Parties, People - Case documents
Evidence and supporting documents attached to a case.
Linked to Cases, People - Case actions
Attributed actions performed on a case by an officer.
Linked to Cases, People - People
Staff and officers who act on public records requests.
Linked to Users
- Information requests
Specialty information requests tracked against statutory due dates.
Linked to Parties - Parties
Applicants and requesters who file public records requests.
- Disclosure reviews
Line-by-line disclosure review of requested documents.
Linked to Information requests, People
- Disclosure reviews
Line-by-line disclosure review of requested documents.
Linked to Information requests, People - Information requests
Specialty information requests tracked against statutory due dates.
Linked to Parties - People
Staff and officers who act on public records requests.
Linked to Users
- Fee receipts
Fees received and reconciled against a case.
Linked to Cases - Cases
Public records applications tracked from submission to closure.
Linked to Parties, People - Information requests
Specialty information requests tracked against statutory due dates.
Linked to Parties - People
Staff and officers who act on public records requests.
Linked to Users
Keys and references
Use each record’s Id as the stable identifier where present. Case number is the human case reference. Parties may have a reference number; a fee receipt has its own Reference. Preserve those distinctions during import. Resolve references before moving dependent histories. The Users self-reference belongs to the platform identity structure.
Migration order
- Import Users and link People.
- Import Parties.
- Import Cases and information requests with their people and party references.
- Import case documents, case actions, Decisions, fee receipts and disclosure reviews with their parent links.
- Compare case and request states with their dated history before opening the working lists.
Set up RTI / FOIA Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.