Files per officer is a workload question before it is a target.

Two officers can carry the same number of files and very different workloads. One book may be clean and close-ready. Another may be full of curative work, delayed demands, rescheduled signings, and transactions that will not close this month.

A file count without stage and mix is not a staffing plan.

Define the count before comparing it.

State whether the report counts new orders, active files, scheduled closes, or completed files. Use the same period and definition for each officer. Keep cancelled orders visible. They consumed opening work even though they produced no close.

Next, separate the pipeline into stages the office actually uses. A file waiting on a third party is not the same as a file waiting for available staff. Combining them can make a staffing problem look like a title problem, or the reverse.

Put assistant coverage beside the officer number.

Record who handles order entry, follow-up, document preparation, signing coordination, and post-close work. Identify shared assistants and the other queues they carry. An officer-level productivity comparison is misleading when one officer’s support work sits elsewhere on the payroll.

• Active files by stage and transaction type.
• Expected closes in the agreed planning period.
• Files with a named blocker and the party responsible for clearing it.
• Officer and assistant coverage, including planned absences.
• Rework and recurring tasks that do not appear in the closed-file count.

The purpose is to understand the work, not to create a ranking before the definitions are settled.

Keep contribution separate from capacity.

More closes do not automatically mean a better branch result. Compare collected fees with agreed direct costs and compensation for the corresponding files. Show shared overhead separately so the owner can see what is a direct operating effect and what is an allocation choice.

An officer split tells only part of the story. Assistant time, employer costs, waived fees, and repeated work can change the economics. Agree on those definitions with the accounting team before presenting a per-file number as a basis for a compensation decision.

Ask what the next hire would remove.

Before adding an officer, identify the queue that is constrained. The office may need officer capacity. It may need assistant coverage, clearer decision rights, or a better handoff at one stage. The answer should show up in the work, not in a generic files-per-person benchmark.

For an operating review, bring a defined period of orders and closes, the active-file queue, transaction types, staffing coverage, and the branch P&L. The first deliverable is a common set of definitions. The next is a view that connects workload to contribution without pretending they are the same number.

An operating perspective, not a legal, regulatory, accounting, or security opinion. Requirements and controls depend on the business and its professional advisers.