The case file is the unit of work
Documents, participants, tasks, decisions, and the audit trail all live on one case file — and everything reports up from it.
Case Manager is the Feith Platform application for the case files a federal agency handles on its own terms. You set the case type, the fields, the workflow, and who can see it — and every case gets the same documents, audit trail, and secure close-out underneath.
The work that lands in a case file is the work that doesn't fit a standard ticket, record, or form. It carries a subject, a set of stakeholders, a body of documents, a decision history, and an outcome. Inside a federal agency that might be an IG investigation, an EEO complaint, a grant award, a clearance adjudication, a procurement protest, a congressional inquiry, an audit response, or an inspection finding. Your agency owns the rules.
Most of these workflows look nothing like each other on paper. An IG investigation runs for months behind tight access controls and ends in a final report. A grant award runs against a deadline, pulls in experts from outside the office, and ends in a signed funding decision. An HR case touches Privacy Act records, runs through union review, and ends in a personnel action.
What they share is the shape: every one is a case file with documents, notes, participants, tasks, decisions, and an audit history. Case Manager is the application for that shape, configured per case type by the agency that runs the work.
Documents, participants, tasks, decisions, and the audit trail all live on one case file — and everything reports up from it.
The case type, fields, workflow steps, approval gates, and access controls are all set by the office that runs the work, and changed when the work changes.
The case types differ; the engine underneath does not — one platform to administer, one to learn.
The security envelope, records vault, audit ledger, AI surface, and integration layer all come from the Feith Platform, not rebuilt per case type.
A representative selection delivered on Case Manager across the federal customer roster. The list is illustrative; the engine's configurability keeps the catalog open-ended.
Investigator-led files for misconduct, fraud, waste, and abuse. Witness statements, evidence chain of custody, final report.
Personnel files for adverse actions, EEO complaints, grievances, and accommodations, with Privacy Act protections enforced on the case envelope.
Award packages from solicitation to closeout. Recipient correspondence, scoring artifacts, signed funding decisions.
Response files for IG, GAO, OIG, and internal audit findings. Evidence collection, response drafting, corrective-action tracking.
Response files for physical security, OPSEC, and personnel security events. Chronology, mitigation actions, after-action artifacts.
Inspection files for command, facility, and program accreditation cycles. Findings, evidence packages, certification artifacts.
Contracting files for award protests, contract disputes, and acquisition reviews. Source-selection references, decision memoranda.
Member-driven inquiry files. Constituent correspondence, internal tasking, cleared response drafting, delivery tracking.
Disciplinary and removal files. Union notifications, hearing artifacts, appeal record.
Workplace-conduct files. Witness interviews, finding artifacts, management referral.
Personnel background files. Source materials, adjudication notes, final determination.
Regulatory files for agency-administered programs. Subject correspondence, evidence, finding and disposition.
Every case file looks the same on the outside; the configuration varies by case type. That shared anatomy is what makes the engine portable across case types.
The anatomy sets the boundary between what the agency configures and what the platform provides. The agency configures the case type, the field panel, the workflow, the deliverables, and the participant roles. The platform provides the documents surface, permissions enforcement, the audit ledger, the storage envelope, records integration, and the AI surface. Adopting Case Manager for a new case type means making configuration decisions inside a stable anatomy.
The case type and the fields vary; these four phases carry every case file from open to close.
Cases enter from across the agency. The Collect phase handles intake.
Cases run because people work them. The Collaborate phase handles the people work.
Cases produce data. The Report phase makes it visible.
Cases close on a deliverable. The Deliver phase produces and delivers it.
Most case tools market configurability, then bill the actual configuration as consulting hours. Feith puts the full build (fields, workflow, security, and forms) in your team's hands. Our own engineers use the same tools when you want us to build it, and everything they configure stays editable by you.
Pick the closest pre-configured case-type template (IG, HR, grants, audit, security incident), or start from blank.
A drag-and-drop field designer. Add fields, set types, mark required, set validation rules. No code.
A visual workflow designer. Place the steps, set approvers, set escalation rules, set notifications, all built into Case Manager itself.
Save the configuration and the case type is open to its user group. Permissions, audit, documents, reports, and the Deliver phase are inherited from the platform, with no extra setup.
An agency IT lead and a process owner can stand up a new case type in days. The workflow designer is part of Case Manager itself, so the configuration skills your team builds on one case type carry straight to the next. For agency-specific processes that aren't case files, Workflow iQ is the sibling no-code engine on the same platform.
Every case closed at disposition lands in the same vault that holds the agency's federal records. Retention under the records schedule applies automatically.
See RMA iQEvery action on every case file is recorded in the platform audit ledger: same ledger, same retention, same query surface as records.
Document classification, field extraction, redaction suggestions, and case-file summarization are available on every case file through the platform AI surface.
See AI in FeithCase Manager pulls documents and triggers from the same layer that serves RMA iQ and the workbench applications: M365, SharePoint, network drives, mainframes, line-of-business systems, mail servers.
See Integrations & CaptureFedRAMP Moderate authorization, DoDM 8180.01 compliance, FISMA High at IL7 (TS/SCI), DISA JITC testing (legacy 5015.02). Case Manager inherits the envelope, with no re-certification per case type.
CAC, PKI, agency IdP integration, ABAC and RBAC, classifications and supplemental markings. Case Manager enforces your existing access model on every case file.
A case file in the field touches the agency's email, document repository, line-of-business system, identity provider, scanning operation, and records system. Case Manager is built to live in that traffic.
| Source system | Role in case work | Example |
|---|---|---|
| Email and messaging | Case intake, stakeholder notification, document arrival | Microsoft 365, mail servers, SMS carriers |
| Document repositories | Document ingestion, evidence collection | SharePoint, Documentum, OpenText, Alfresco, FeithDrive, network drives |
| Line-of-business systems | Case triggers, decision data, deliverable routing | Salesforce, ServiceNow, Oracle E-Business, SAP, PeopleSoft |
| Identity and access | Authentication, role and attribute resolution, classification | Agency IdPs, CAC and PKI, supplemental markings |
| Scanning and capture | Physical document intake | High-speed scanning, OCR capture, manual upload |
| Records and disposition | Closed-case retention and disposition | RMA iQ, NARA transfer, retention schedules |
Integration depth scales with the case type. An IG investigation needs strong mailbox integration and tight identity binding; a grants case needs line-of-business and repository integration; a security incident needs LOB triggers and after-action document ingestion. Case Manager handles each shape through the same integration layer.
The horizontal case-management market is broad, and each commercial offering is credible in its category. But the federal case problem has a few specific shapes that horizontal tools handle thinly. Here are four.
A closed case dispositions straight into the agency's federal records vault, retention and audit intact. A horizontal case tool needs a separate records system stood up alongside it, if it has one at all.
Classification banners, supplemental markings, and ABAC enforcement are built into the case-file shell, on premises up to Top Secret compartmentalized environments.
Adopt Case Manager for IG cases and you have it for HR, grants, and audits too — the configuration model is the same across every case type, so the work you do once carries.
Hardened in partnership with the Intelligence Community and run by a Facility Security Cleared vendor with most staff cleared Secret or higher — not a commercial SaaS you adopt on faith.
Every Feith application sits on the same substrate; they differ by the work they're built for. Case Manager handles the agency-configured case files. Its siblings handle the regulated workflows, the records core, and the document surface.
The federal records management application. Closed Case Manager files disposition here.
Explore RMA iQFOIA and Privacy Act request processing on a statute-defined workflow.
Explore FOIA WorkbenchADR, MDR, and SDR declassification workflows under EO 13526.
Explore Declassification iQFeithDrive and File Cabinets for shared document work.
Explore Document ManagementA demo is built against a case type your office runs. Bring a case-file shape and a workflow, and the Feith team will configure the case type live and walk the lifecycle from open to close.
Prefer to read first?
We'll reach out shortly to set up a demo built on a case type your office runs.