News
ORI routing on a budget: when one location serves multiple agencies
By Operations Desk · 4 hours ago
One location, several agencies
A single capture desk often serves schools, employers, and licensing boards. Each program can map to a different Originating Agency Identifier. The budget question is not whether you need more scanners. It is whether your software routes the package to the right ORI without a spreadsheet.
Split queues when purpose codes, fees, or retention rules really differ and operators keep mixing them up. Stay on one workflow when the differences are just labels on the same FDLE/FBI path and your team can select the ORI at intake.
When a single ORI is enough
If 90 percent of volume is one civil ORI and the rest is occasional, train the exception instead of building a second desk. Document the exception. Log the ORI used. That is cheaper than a second software stack.
When volume for a second agency becomes weekly, add it as a first-class option in the same UI—not a sticky note. Multi-ORI routing exists so small shops can stay accurate without hiring a channel specialist.