When to Hire a Firm Administrator, and What They Should Own

There is a version of the small firm partner's week that nobody puts in a marketing brochure. Monday morning is spent chasing an unsigned engagement letter and re-sending a bank detail confirmation. Tuesday afternoon disappears into a renewal notice for a research subscription nobody remembers approving. Wednesday is the day the billing run was supposed to happen, except a client called with a genuine emergency, so billing slides to Friday, and then to the following Tuesday, and eventually into the next month. None of this is legal work. All of it is being done by someone charging several hundred dollars an hour.

Firms rarely decide to hire an administrator. They arrive at it, usually after a bad quarter, a missed renewal, or a reconciliation that took three evenings to sort out. By the time the decision gets made, the firm has already paid for the delay several times over in partner hours that were never billed and never should have been spent that way. The hire itself is not complicated. What trips firms up is the handover, because operations and compliance are tangled together in a law firm in a way they simply are not in most other businesses.

This is a practical walk through the decision. The concrete signals that the moment has arrived, what the administrator should own from the first week, what should never leave attorney hands regardless of how capable the person is, and how to structure the handover so the firm gains capacity without quietly loosening its grip on trust money, conflicts, and deadlines.

The administrator is a different animal from a legal assistant

A legal assistant supports matters. An administrator runs the firm around the matters. That distinction sounds academic until you look at what each one actually touches during a normal week. The assistant works inside a case file, formatting, filing, scheduling, chasing signatures, keeping a specific matter moving. The administrator works across every file at once and never really touches the legal substance of any of them. Their domain is the billing cycle, the vendor stack, the compliance calendar, staff onboarding and offboarding, insurance, the lease, the bank relationship, and the operational health of the systems everyone else depends on.

That is why promoting your best legal assistant into the role, which is the most common way small firms fill it, works about half the time. Being excellent at moving a matter forward is not the same skill as running a monthly close, negotiating a renewal, or holding a partner accountable to a billing deadline. Some assistants have both. Many do not, and asking someone to do both jobs at once usually means the matter work wins, because matter work has clients attached to it and operational work only has the firm. If you promote from within, take the case work off the person completely. A half administrator produces neither outcome.

Signal one: partners are doing work nobody would pay for

The first and most reliable signal is not a feeling of being busy. It is a count. Take two ordinary weeks, not the week of a trial and not a holiday week, and write down every task a partner personally handled that no client would ever agree to pay for. Bank portal logins. Software password resets for a new hire. Chasing an insurance certificate. Comparing two phone system quotes. Rebooking a conference room. Reconciling a credit card statement. Most partners are genuinely shocked by the total, because each individual task feels like five minutes and none of them ever get recorded anywhere.

Then convert it. If a partner is spending six or eight hours a week on that list, the firm is not saving money by avoiding an administrator's salary, it is paying for the same work at the most expensive rate available and getting a worse result. The comparison that matters is not salary against zero. It is salary against the fully loaded cost of partner hours that were consumed and never billed, plus the revenue from the matters that were never taken on because there was no room in the week. When the count comes back high two weeks running, the question has already answered itself.

Signal two: billing has started slipping and nobody notices for weeks

The second signal is quieter and more dangerous. Billing in a small firm is nobody's actual job until it becomes a crisis. It sits with whichever partner is least busy that month, which means it moves every month, which means it slips. The tell is not that an invoice went out late. The tell is that nobody in the firm can say with confidence, on any given Tuesday, how much unbilled time is currently sitting in the system and how old the oldest piece of it is. If that number is unknown, it is almost certainly worse than anyone assumes, because unbilled time ages badly and clients dispute old entries far more readily than recent ones.

An administrator turns billing from an event into a cycle. The mechanics get much easier when the software is doing the assembly rather than a person. One-click invoicing in Casely turns every unbilled hour on a matter into a single itemised draft, so the administrator's job becomes reviewing and chasing rather than compiling from scratch, and hourly, flat-fee, contingency and blended arrangements all sit natively alongside each other instead of living in separate spreadsheets. For firms with institutional clients, LEDES 1998B export means the administrator can push a compliant file without an attorney reformatting anything by hand. The bottleneck stops being assembly and becomes attorney review, which is exactly where it should sit.

Signal three: nobody owns the vendors, so the vendors own you

Count the recurring charges hitting the firm's account. Research subscriptions, e-filing accounts, the phone system, the document scanner service contract, professional indemnity cover, the shredding company, the accountant, the domain registrar, two or three tools somebody trialled and never cancelled. In most small firms nobody has a complete list. Renewals get discovered in the bank feed rather than anticipated, which means every negotiation happens after the auto-renewal has already gone through, at which point there is no leverage and no alternative quote.

The cost of this is not only money. It is risk. An expired e-filing credential discovered on the afternoon of a deadline is a compliance problem, not a procurement problem. Professional indemnity cover that lapses because the reminder went to a departed partner's inbox is a genuinely serious problem in most regulated jurisdictions. An administrator's first deliverable in this area is unglamorous and enormously valuable, a single register of every vendor, contract term, renewal date, notice period, cost, and the person inside the firm who actually depends on it. Everything else about vendor management is downstream of having that list exist at all.

What the administrator should own from week one

Resist the urge to hand over everything at once. The first ninety days should transfer a specific, bounded set of responsibilities, and each one should be something the firm can see working or failing clearly. The billing cycle is first, meaning the administrator owns the calendar, the pre-bill assembly, the chase on attorney review, the send, and the receivables follow up. Vendor and contract management is second, starting with building the register. Staff onboarding and offboarding is third, covering system access, equipment, keys, and the checklist that gets run when someone leaves. Facilities, insurance renewals, and the firm's own document filing round out the set.

Notice what is on that list and what is not. Everything there is operational, repeatable, and measurable. The administrator can be given real authority over all of it without any of it touching a client's legal position. Intake routing is a reasonable fourth addition once the first three are stable, meaning the administrator ensures every enquiry is logged, conflict checked, and assigned to an attorney within a defined window. Contact labels in Casely make that tractable, since roles and referral sources are tagged at the contact level rather than living in someone's memory, and the administrator can see where work is actually coming from without asking a partner.

What should never leave attorney hands

The administrator can prepare almost anything. What they should not do is approve the things that carry professional responsibility. Trust account disbursement approval stays with an attorney. Conflict clearance decisions stay with an attorney. Decisions about who sits behind an ethical wall stay with an attorney. Anything that constitutes legal advice to a client, including the tempting grey area of telling a client what a deadline means for their case, stays with an attorney. These are not trust issues about the individual you hired. They are structural, and they should be written down before the person's first day rather than negotiated case by case afterwards.

Jurisdictions differ on how hard some of these lines are, and this is worth checking rather than assuming. In many US states, rules modelled on ABA Model Rule 5.3 make the supervising lawyer responsible for a nonlawyer assistant's conduct, and several state bars have their own requirements about who may be a signatory on a client trust account. In England and Wales, SRA-regulated firms operate with named compliance officers for legal practice and for finance and administration, which formalises some of this in a way that has no direct US equivalent. Canadian and Australian law societies each set their own trust handling and supervision rules. Confirm your own regulator's position before writing the job description, not after.

Handing over trust without handing over control

Trust accounting is where most firms hesitate, and they are right to. The instinct is to keep the administrator entirely away from the client account, but that instinct produces the worst of both worlds, because the partner keeps doing reconciliation badly at eleven at night while the person hired to bring rigour to firm operations is not allowed near the one area that most needs it. The better model separates preparation from authorisation. The administrator prepares the reconciliation, gathers the supporting records, flags every unmatched item, and presents it. An attorney reviews and approves. Both actions leave a record.

That model only works if the system enforces it rather than relying on everyone remembering the rule. In Casely, any disbursement that exceeds a matter's actual trust balance is blocked at the database transaction level, not surfaced as a warning dialog that a tired person clicks through at the end of a long day. Ledgers are isolated per matter, so one client's funds cannot quietly cover another's shortfall. Corrections are voided and remain visible rather than deleted, which means an administrator can fix a genuine error without any possibility of erasing the history a regulator or an auditor would want to see. Delegation is safe when the guardrail is structural. It is not safe when the guardrail is a person's memory.

Access is the part firms get lazy about

The day the administrator starts, someone will be tempted to give them full system access because it is faster than thinking about it. That decision is understandable and it is a mistake. An administrator needs to see billing, time entries, matter status, deadlines, and contact records across the whole firm. They almost certainly do not need to read privileged case correspondence, and in a firm running any kind of ethical wall they must not be able to reach walled matters at all. Blanket access also makes offboarding messier later and makes it harder to answer a client question about who could see what.

The distinction that matters is whether the restriction is real or cosmetic. A great many systems hide restricted matters from a menu while leaving them reachable through global search, a calendar entry, a shared document link, or a report export. Casely enforces ethical walls at the server and data-access layer, so a walled user genuinely cannot reach a restricted matter by any path, including search, the calendar, or a forwarded link. Document encryption uses a per-firm key, and every document carries a comment field recording what changed and why, which means an administrator handling document logistics leaves a legible trail rather than an ambiguous one. Give the role wide operational access and narrow substantive access, and revisit it once at the ninety day mark.

Deadlines and conflicts are the two things you cannot afford to fumble

Two operational areas deserve special handling during a handover because both are malpractice adjacent. Deadlines are the first. An administrator can absolutely own the mechanics, meaning ensuring every deadline is entered, that nothing sits only in an attorney's own calendar, that the diary is reviewed weekly, and that the review actually happens when the attorney who normally does it is in a hearing. What they should not own is the legal determination of what the deadline is. Attaching deadlines to the matter, with next-date auto-tracking, keeps the record in one place rather than scattered across individual calendars, which is what makes the weekly review possible at all.

Conflicts are the second. The administrator running the intake process will be the first person to touch most new enquiries, and a conflict check performed at that moment is far more useful than one performed a week later after work has already started. The search itself should cover the full contact and matter history, every role a party has played, including closed matters, because the conflict that causes trouble is almost never the one on an active file. The administrator runs the search and documents it. An attorney reads the result and makes the call. Write that two-step down and audit it monthly for the first six months.

Deciding between a hire, a fractional administrator, and a bookkeeper

Not every firm at this stage needs a full time administrator, and pretending otherwise leads to an expensive hire with an underfilled week. Roughly speaking, a firm with two to four attorneys often needs somewhere between a half and three quarters of a role, which can be met by a part time hire, a fractional administrator shared across a few small firms, or a bookkeeper plus a clearly assigned internal owner for vendors and onboarding. Above five or six attorneys, the volume of billing, staff, and vendor activity usually justifies the full position without much argument.

The trap is the bookkeeper substitution. A bookkeeper handles the books, which is genuinely useful and genuinely narrower than what this role covers. They will not chase a partner about unreviewed pre-bills, run the offboarding checklist when an associate leaves, or notice that the professional indemnity renewal is six weeks out. If the firm hires a bookkeeper and assumes the administrator problem is solved, the operational gaps stay exactly where they were and the partners keep filling them. Be explicit about which of the two problems you are actually solving, and if the answer is both, say so in the job description and price the role accordingly.

How to tell in month six whether it worked

Set the measures before the person starts, because retroactive evaluation of an operations hire is almost always vibes-based and unfair to everyone. Four numbers cover most of it. Days from period end to invoices sent. Total unbilled time older than sixty days. Number of renewals discovered after the fact rather than anticipated. Partner hours per week spent on non-billable administration, measured the same crude way you measured it before the hire. If those four are moving in the right direction by month six, the role is working, regardless of how the week feels.

Add one qualitative check that matters more than it sounds. Ask whether the partners have stopped being the escalation point for operational questions. If staff are still walking into a partner's office to ask about software access, a supplier, or a billing question, the authority did not actually transfer, only the tasks did. That usually means the handover was announced but never formalised, and the fix is a short internal note naming the administrator as the decision maker for a specific list of things. Authority that is not stated out loud tends to drift straight back to whoever held it before.

The hire is the easy part

Most firms that struggle with this role did not hire the wrong person. They hired a capable person into an undefined job, gave them a pile of tasks instead of a domain, kept approval authority informal, and then wondered six months later why the partners were still doing bank admin on a Sunday. The fix is boring and it works. Define the domain, write down the authority boundary, transfer responsibilities in a sequence, and make sure the compliance-sensitive areas are protected by the system rather than by anyone's diligence.

That last point is the one worth spending real time on before the hire rather than after. Guardrails that live in a person's habits do not survive a busy month, a holiday, or a resignation. Guardrails that live in the software survive all three. A trust ledger that structurally cannot go negative, ethical walls enforced where the data actually lives, conflict searches that cover closed matters as well as open ones, and a deadline diary attached to the matter rather than to an individual's calendar are what make it possible to hand over operations to someone new without lying awake about it. If your current setup cannot support that separation of preparation from approval, fix the setup first. Our trust accounting software for law firms page walks through how the enforcement actually works, and Casely is cloud-native with nothing to install locally and a free plan to start on.

Hire the administrator earlier than feels comfortable, define the job more narrowly than feels generous, and protect the compliance edges structurally rather than personally. Firms that do those three things get a genuine step change in capacity within a quarter. Firms that skip any one of them usually end up back where they started, with a good employee, a frustrated partnership, and the same Sunday evening admin that started the whole conversation.