Every decision, on the record.
MOSI keeps every version, approval, and comment, and logs who did what and when. When an auditor calls or a records request arrives, you export the full history instead of rebuilding it.
Document Logs in the Admin Portal, scrolled down to the action type filters and the log table. Five action types are checked. The table lists recent actions across six departments: Alana Brooks published the Telework Policy, Priya Nair requested changes to Generative AI Use and approved the Records Retention Schedule for Legal Review, Tom Becker rejected Fleet Vehicle Use, Sam Ortiz submitted the Records Retention Schedule for approval, Jordan Kim published Travel Reimbursement, and Alana Brooks approved the Client Intake Procedure for Division Heads.
The lower half of the review page for the Records Retention Schedule. The Approval History table shows version 5 submitted for approval by Sam Ortiz on September 8 and approved by Legal Review by Priya Nair on September 10. Below it, Version History is in compare mode with versions 5 and 4 checked and the message Ready to compare. Version 5 is Current and In Review at step 2 of 3, version 4 is Published (Internal), version 3 is a Draft, and versions 2 and 1 are Archived.
The Version Comparison page for the Records Retention Schedule, comparing version 4 and version 5, both created by Sam Ortiz. The AI Summary says correspondence retention changed from 3 to 5 years, a 3-year rule for text messages about county business was added, and the provision allowing paper originals to be destroyed once scanned was removed. The Visual Diff shows the stored text of both versions side by side with line numbers: the changed number is highlighted in yellow, the removed line in red, and the added line in green.
Open Records Request in the Admin Portal, scrolled to the export panel. The Records Retention Schedule is selected in the search results. The panel lists what the package holds: 5 versions, 64 timeline events, 23 comments including 3 soft-deleted, 11 approvals, 4 attachments, and a policy status of In Review. The request reference ORR-2026-0431 is being typed, all four package options are checked, and the Queue export (ZIP) button is below.
The Export Inbox in the Admin Portal, with a message that the export of the Records Retention Schedule has been queued. The jobs table lists six exports: one queued, one running, and four ready, each with a ZIP download button. The Records Retention Schedule export, reference ORR-2026-0431 requested by Jordan Kim, is ready.
The Document Aging Report. Stat cards show 14 active documents, 2 approaching threshold, 3 over threshold, and 6 completed in the last 30 days. Status Distribution lists In Review, Changes Requested, and Draft with average and maximum ages in days. The Document Details table, with Export CSV and Export PDF buttons, tints Generative AI Use yellow as approaching its threshold, and tints the Records Retention Schedule and Client Intake Procedure red as review overdue and over threshold.
Every action, in one log. Document Logs lists each submission, approval, change request, rejection, and publication across every department. Filter by date and action type, or search by name, email, or comment.
Nothing gets overwritten. Every version keeps its status, author, and date, below the approval history of the version in review. Check any two versions to compare them.
Compare any two versions. An AI summary describes what changed, and the visual diff shows every added, changed, and deleted line side by side.
Answer a records request from one screen. Select a document, check what the package will hold, and add the request number. The export runs in the background and is recorded in the audit log.
Download the complete package. Finished exports wait in the Export Inbox as a ZIP with a report, the timeline, every version, and a manifest.json that lists a SHA-256 hash for each file.
Find stale documents before an auditor does. The Document Aging Report flags documents that are over or approaching their status threshold, or past their review date. Export it to CSV or PDF.
Click any section to open it
Answering a records request used to mean searching shared drives, inboxes, and scanned signature pages. In MOSI, the history is already kept: every version, comment, and approval, ready to export with a hash for every file.
Capabilities
Find it, compare it, hand it over.
-
Document Logs for every department
Every submission, approval, change request, and publication in one list, with the version, organization, user, and time. Filter by date and action type, or search by name, email, or comment.
-
Every version, kept
Each version records its author, date, workflow step, and what changed. Restore any of them as a new draft without touching the original.
-
Side-by-side comparison
Compare any two versions with added, changed, and deleted text color-coded, plus an AI summary and the comments each version addressed.
-
Open records exports
Pick any policy, including archived ones, and export its versions, timeline, comments, approvals, and attachments as a single ZIP.
-
A manifest in every package
Each export includes a manifest with a SHA-256 hash of every file, so anyone can check that each file matches what was exported.
-
Reports that flag what’s stale
Document Aging, Approval Times, and Expiring Items show what is overdue, over threshold, or about to expire. Export any report to CSV or PDF.
Why it matters
Records that hold up.
-
The audit trail can’t be edited
Alongside Document Logs, an audit event store records the user, action, resource, IP address, and user agent for every action. Those entries can’t be changed or removed.
-
Nothing is hard-deleted
Archiving a policy is a soft delete. Its full history stays intact, it can still be exported, and it can be restored from the Archived Policies page.
-
Deadlines come to you
The owning organization’s creators, reviewers, and admins are notified when a review is due, 30 days before a policy expires, and when it expires.
What does MOSI log?
Document Logs shows every submission, approval, change request, rejection, and publication, with the document, version, organization, user, and time. Separately, an audit event store records the user, action, resource, details, IP address, and user agent for every action in the system.
Can anyone edit or delete the history?
No. Audit events can’t be changed, and nothing is hard-deleted. Restoring an old version creates a new draft, archiving a policy is a soft delete, and deleted comments are kept so they can be included in a records export.
What goes into an open records export?
You choose. A package can include every version with a PDF of each, the full timeline, comments including soft-deleted ones, approvals, attached documents, and the changes between versions. It arrives as a ZIP in your Export Inbox with a manifest listing a SHA-256 hash for every file.
Can we export a policy that has been archived?
Yes. Archived policies keep their full history and appear when you search for a policy to export. They can also be restored, one at a time or several at once, from the Archived Policies page.
Which reports are included?
The Reports Hub includes Document Aging, Approval Times, and Expiring Items. Each runs on demand and exports to CSV or PDF. Expiring Items can look ahead 7, 14, 30, 60, or 90 days.
More of the platform
Get started
See MOSI with your own policies.
Bring a policy you are working on. We will walk it from draft to published record, and show you exactly what your auditors will see.