The quarter-end surge is a routing problem, not a staffing one

Three weeks from the close date, the queue is forty contracts deep. Order forms waiting on a single redline. An MSA the counterparty rewrote end to end. A stack of DPAs that were routine until one of them was not. Every one blocks revenue until it is signed, and none of them arrived early enough to plan around.

Every quarter ends the same way. Ten, twenty or a hundred contracts need signing at once. The problem is not the annual volume, which finance could have forecast in January. It is the shape of it. The work does not spread across ninety days, it stacks into the last fifteen, and every standard answer to a capacity gap assumes work that arrives evenly.

Why the usual answers do not fit a surge

Hiring takes months. Requisition approval, search, notice period, ramp. A lawyer signed off during the surge starts well after it has passed, and then you carry the cost through Q1, when the queue is at its thinnest. You have staffed to a peak that arrives four times a year and paid for it on every other day.

Contractors cannot absorb a synchronized surge. A contractor adds capacity sequentially, one matter after another, which works well for a backlog that built up over months. A surge is not a backlog. It is fifty matters that all became urgent on the same Tuesday, and one more pair of hands on a queue that needs ten does not move the close date.

Big Law can absorb it, at a price finance will not sign off on routine paper. The leverage model is genuinely built for this. But the hourly rate approved for a bet-the-company matter does not get approved for forty order forms, so the routine paper queues behind the important paper and the close date slips anyway. It is too routine for those rates and too binding for a tool that only flags issues.

What routing the overflow looks like

The alternative is to treat the surge as a routing decision rather than a staffing one. The queue leaves; the team stays the same size. In practice that means four things.

• Your standards are learned upfront, down to where a reviewer must escalate rather than decide, so forty agreements come back holding one line rather than forty individual preferences.

• Matters go out through channels you already use, by CRM, Slack or email, with no onboarding project and no seat licenses to buy first.

• A named licensed lawyer signs off every matter against those positions, and you see every matter, its status and its lawyer.

• The fee is flat and agreed before work starts, so a surge does not become an invoice nobody budgeted for.

Speed matters more during a surge than at any other point in the year. Our average turnaround is roughly four hours, and the gap between a two-week loop and a same-day one is the gap between clearing the last contract before the close date and clearing it after.

Deciding what leaves and what stays

Routing everything is the wrong instinct. The useful test is whether a matter turns on context only your team holds, or on a standard you can write down. One global HR platform keeps equity and employment in-house and routes commercial contracts, procurement and the quarter-end surge out. That line holds up well: work that depends on internal judgment stays, work that depends on consistency travels.

The economics follow from that split. One Fortune 500 client replaced two LSP contractors with routed overflow, cutting annual overflow commercial legal spend from $917K to $213K and average turnaround from 13 days to 20 hours. A commercial contract on your own paper, up to 30 pages, is $750, quoted before work begins.

None of this makes the surge smaller. The paper still lands in waves. What changes is that the queue becomes something you route rather than something you hire against, and that decision takes an afternoon instead of a quarter.