Built for public agency records programs
Every file classified to your schedule.
Every retention decision cited.
Upload a single document or ten years of a shared drive. Records Classification reads each file, assigns it to a series in your own retention schedule, applies the retention period that series carries, and flags anything sensitive along the way. Every call names the schedule item it stands on, and nothing is destroyed until a records officer approves it.
- Your schedule, not a generic one
- Bulk or single file
- Nothing destroyed automatically
- Every call cited
What it changes for your office
Records keep accumulating. The schedule only works if someone applies it.
Most agencies have a retention schedule that is followed carefully for paper and loosely for everything else. Shared drives, email exports, and departmental folders hold years of records nobody has had time to classify. Records Classification applies the schedule you already have to the files you already hold.
For the records officer
Instead of asking each department to classify its own folders, you receive a classified inventory with every file assigned to a series and every uncertain call routed to you. Your review time goes to the decisions that need judgment, and the routine ones arrive already done and already cited.
For department staff
Staff no longer have to learn the schedule to comply with it. They upload a folder, or the system reads the share they already use, and each file is classified for them. When a file is ambiguous, the question goes to the records officer rather than back to the person who saved it.
For counsel and the privacy officer
Litigation holds, sensitive data, and disposition all run through one record. A hold stops disposition across every matching file the moment it is placed, and a file holding personal information is flagged before it is shared, moved, or released.
The product
Autessa Records Classification, what your team works in.
Schedule Library
Your retention schedule, encoded once. Each series carries its description, its retention period, its trigger event (end of fiscal year, separation, case closure), and its disposition. When the state archive revises the general schedule or your agency adopts a supplement, a records officer updates the series and every new classification uses the revision from that moment forward. Earlier decisions stay explained against the version that was in force when they were made.
File Review
Each file opens beside its classification: the series assigned, the language in the document that placed it there, the retention period and trigger, and any sensitive data found. When the system cannot decide between two series, it says so and shows both, rather than guessing. A records officer confirms or corrects the call in one step, and the correction is kept with its reason.
Holds and Disposition
Nothing is destroyed on its own. When files reach the end of their retention period, they are gathered into a disposition batch for a records officer to approve, with the series, dates, and counts that a destruction certificate requires. A litigation or public records hold placed by counsel removes every matching file from disposition until counsel lifts it, and the hold is part of the record.
Inventory and Reporting
A live inventory of what your agency holds, by department, by series, and by where the files sit. It shows how much has been classified, how much is past retention, and how much sensitive data lives in places it should not. The same inventory answers the annual report to the state archive and the question every new public records request starts with: what do we have, and where is it.
In practice
The details that decide whether a classification holds up.
Three of them, handled the way a records program already handles them: which schedule applies, what happens when the answer is unclear, and what happens to the file itself.
On the schedule
Your schedule is the only authority it uses
Records Classification does not bring its own idea of how long a record should be kept. It classifies against the general schedule and supplements your agency has adopted, and every classification names the series and version it relied on.
On uncertainty
An unclear file goes to a person
When a file could belong to more than one series, or when the content does not clearly match any of them, the system routes it to a records officer with the candidates it considered. It does not pick the longer period to be safe or the shorter one to save space.
On the files
Classification never moves or changes a file
Classifying a file records a decision about it. The file stays where it is, as it is, until a records officer approves a transfer or a disposition, and that approval is recorded with the officer's name and the date.
Below: a file the system would not decide on its own, with the two series it considered.
Defensibility
When a disposition is questioned, the answer already exists.
Records programs are judged on what they can show. When a requester asks for a file that no longer exists, or an auditor asks how the agency decided what to keep, the question is not whether the decision was right in the abstract. It is whether the agency followed its own schedule and can prove it.
Records Classification keeps that proof as it works. Every classification records the file, the series, the schedule version, the actor (the system or a named records officer), and the time. Every hold records who placed it and why. Every disposition records the batch, the approval, and the certificate. The log is append-only, so what you produce years later is what was recorded at the time.
One file, every decision accounted for, from upload to destruction.
The same record across a whole disposition batch, ready for the destruction log.
See it classify your own files.
Bring a folder your agency has never had time to classify, along with your retention schedule. We will run Records Classification on it and walk your records officer through every call it made and every file it routed back.
FAQ
Questions we are glad to answer.
Does it use our retention schedule or a generic one?+
Yours. We encode the general schedule your agency follows and any supplements it has adopted. Every classification names the series and the version of the schedule it relied on.
Will it delete anything on its own?+
No. Files that reach the end of their retention period are gathered into a batch for a records officer to approve. Nothing is transferred or destroyed without that approval, and files under a hold are excluded automatically.
What happens when it is not sure?+
It routes the file to a records officer with the series it considered and the reasons for each. Your agency can also set rules that always route certain kinds of files to a person.
Can it read files where they already are?+
Yes. Files can be uploaded directly, or the system can read the shared drives and document libraries your agency already uses. Classification records a decision about each file without moving or changing it.
Where does our data go?+
Records Classification runs in your own Autessa Private Cloud, an environment your agency controls, with keys your agency holds. Your files are not used to train models for anyone else.