No agency ever decided to run five case management systems. They accumulated them.

The FOIA tool came out of the records office, funded in a year when the backlog got attention. The complaint system was purchased by EEO, or by the Inspector General, on a separate line item. The docket application belongs to the commission and was appropriated directly to it. Correspondence tracking is a SharePoint site somebody in the front office built and has quietly maintained ever since. The legal office runs its matters out of a combination of network folders, a shared calendar, and one attorney’s memory.

Every one of those decisions was reasonable when it was made. They were made by different offices, on different budgets, in different years, and nobody ever had the authority or the occasion to compare them side by side. That is not a failure of planning. It is what happens when case management gets funded functionally instead of enterprise-wide.

The problem is that the caseload does not respect those boundaries. A complaint becomes a legal matter. A FOIA request becomes litigation. A congressional inquiry turns into a records request that turns into a privilege review. The work moves across the org chart even though the systems do not.

Where the cost actually sits

Most conversations about consolidation start with license spend, which is the least interesting number in the equation and usually the smallest. The costs that matter are the ones that never appear on a single line item.

• Security and authorization overhead, multiplied. Five systems means five authorizations to operate, five annual assessments, five sets of POA&M items, five vendor security questionnaires, five sets of patch notifications your security team has to triage. That is recurring cost, paid in your scarcest staff, every single year. Ask your ISSO how many hours go into continuous monitoring across the portfolio and you will get a number that dwarfs the licensing.
• Identity sprawl. Five systems means five account stores. Offboarding a departing employee depends on five different people remembering to act. Access reviews depend on five different exports that nobody reconciles. This is the kind of gap that surfaces as an audit finding long after the person has left.
• Five retention configurations for one retention schedule. Your records officer is working from a single disposition schedule. It has been implemented five different ways by five different vendors, and it is consistently defensible in none of them. When a records request or a litigation hold spans systems, someone has to prove what was kept, what was disposed of, and under what authority.
• The handoffs, which is where work actually disappears. This is the expensive one and the least visible. Every transition between systems is a human being rekeying data into a new form and hoping the statutory clock carries over correctly. Nothing audits that seam. Nothing alerts when it does not happen. When a request or a matter falls through, it almost never falls through inside a system. It falls through between two of them.
• No enterprise view of anything. Leadership cannot answer the question that arrives from the Hill, from a reporter, or from the agency head: what does this individual currently have open with us? Answering it means five queries, five exports, and a spreadsheet somebody assembles by hand over two days.

What consolidation costs, honestly

Consolidation is not free, and any vendor who tells you otherwise is selling you the easy version of a hard project.

The real expense is migration, not licensing. Historical case conversion, legacy data cleanup, decisions about what to migrate versus what to archive in place, and a period of parallel operation while both the old and the new system are running. Budget for that period specifically. It is where consolidation projects go over.

There is also a political cost that IT plans routinely underestimate. An office that gives up its own system experiences it as a loss of autonomy, and that reaction is legitimate, not merely resistance to change. The FOIA officer who has spent six years configuring a workflow that finally works is being asked to trust that the new environment will let her do the same thing. If the project does not answer that concern early and concretely, it will stall in the middle regardless of how good the technology is.

When not to consolidate

A few situations where the sprawl is the right answer, or at least the tolerable one.

• Statutory independence. An Office of Inspector General with independent authority may have real reasons to maintain separate infrastructure, particularly for matters involving agency leadership. That is a governance question, not a technology question, and the answer may legitimately be no.
• Recent investment. An office that completed an implementation eighteen months ago should not tear it out. Consolidation opportunities arrive at renewal and at end of life. Wait for the window rather than forcing one.
• Genuine functional gaps. If the consolidating platform cannot do a function as well as the dedicated tool does, forcing the fit is worse than the sprawl. A docket system that is merely adequate for a quasi-judicial proceeding is not an upgrade. Ask for the demonstration on your actual workflow, not on a generic one, and be willing to walk away from any single module.

Saying that plainly matters, because the alternative is a consolidation program that overpromises and then loses credibility with the first office it disappoints.

Consolidation is not uniformity

Here is the assumption that kills most of these conversations before they start.

Offices resist consolidation because they hear it as standardization. They picture everyone getting the same intake form, the same workflow, the same fields, with the FOIA shop forced to work the way the docket office works. If that were the trade, resisting it would be the correct instinct.

That is not the trade. The right model separates the layers.

What consolidates is the foundation: one audit trail, one identity source, one retention and disposition engine, one security boundary and one authorization package, one search index across the enterprise, one reporting layer.

What stays separate is everything the offices actually care about: their own workflows, their own intake forms, their own clocks and deadline rules, their own queues, their own correspondence templates, their own metrics. Add to that the separation that some of this work legally requires, including ethical walls and need-to-know segregation, so that an EEO matter, an IG investigation, and a general counsel matter can live in the same platform without living in the same field of view.

Done this way, the FOIA office keeps its twenty-day clock, its exemption codes, and its queue structure. The legal office keeps its matter numbering, its privilege review, and its hold notices. The commission keeps its docket rules and its filing deadlines. What they gain is that the handoffs between them stop being retyping exercises, and the agency finally has one place to look.

That distinction, one platform with configuration-level separation rather than one system with one process, is the entire argument. It is also the reason a purpose-built consolidation platform is a different proposition than buying five modules from the same vendor and calling it a suite.

A short exercise

Before your next budget cycle, count three things.

Count your systems. Every application in the agency where a case, a request, a complaint, a matter, or a filing is tracked, including the SharePoint sites and the Access databases. The number is almost always higher than the CIO’s inventory shows.

Count your authorizations. How many separate security packages, assessments, and continuous monitoring obligations does that list generate every year?

Count your handoffs. How many transitions in your workflows involve a person opening one system, reading a record, and typing it into another?

Any agency that runs that exercise honestly already knows whether this article is about them.

 

Let’s Talk

If you recognize your agency in the list above, we would welcome the conversation. ArkCase is a FedRAMP Authorized, open source case management platform built to run FOIA and public records, legal and matter management, complaints, correspondence, docketing, and e-filing on a single foundation, with the configuration separation each of those offices needs. Reach out for a discussion or a demonstration against your own workflows.

Schedule a meeting with the Armedia team.