Departmental Rates Versus One Rate
A single plant-wide rate is simple and blurs everything. When to split into departmental rates, how many, and what the split reveals.
A single organisation-wide overhead rate is simple, cheap to maintain and blurs every difference between departments. Departmental rates cost more to run and tell the truth about work that passes through different parts of the operation.
The calculation in “Departmental Rates Versus One Rate” depends on reliable source records as well as a documented accounting rule. For organisations researching time tracking with screenshots, explore this product page directly can supply consistent time and project context, while the allocation basis and financial interpretation remain decisions for the organisation and its advisers.
The question is not which is better in principle but whether the departments differ enough to matter.
As an outside benchmark for “Departmental Rates Versus One Rate”, see FASB accounting standards resources. Keep the source record, calculation rule, approval and resulting decision visible as separate steps.
When a split is worth it
Do jobs consume departments in different proportions, and do the departments have materially different overhead intensity? Both must be true for a split to change anything.
Do jobs consume departments in different proportions, and do the departments differ materially in overhead intensity? Both must be true, or one rate gives the same answer as five.
If every job passes through every department in roughly the same proportion, one rate gives the same answer as five.
What a single rate hides
That a job which spends its hours in a low-overhead department is subsidising one that spends them in a high-overhead department.
Where the difference is large — a lightly equipped assembly area and a heavily equipped machining area — a single rate is simply wrong about both.
How many departments
As few as will capture the real differences. Three or four is usually enough; ten is administration.
The unit should be a place where overhead is genuinely different, not every line on the organisation chart.
Building a departmental rate
Allocate the pool to departments first, then spread each department's share on its own base. Two steps instead of one.
The first step — allocating central costs to departments — is where the arguments happen and where the honest answer is often a simple proportion.
Allocating the central pool
By headcount, by floor area, by direct cost, or by a service-level estimate. Each is defensible and each will be challenged by whichever department it penalises.
The usual resolution is a simple, stated, stable rule rather than an accurate one, because accuracy here costs more than it returns.
Service departments
Maintenance, scheduling, quality: departments that serve other departments rather than jobs. Their cost has to be pushed out to the production departments before any rate is computed.
Simple proportional allocation is adequate; the elaborate reciprocal methods rarely change the answer enough to matter.
What the split reveals
Usually that one department carries far more overhead per hour than anybody assumed, and that the work passing through it has been underpriced for years.
That finding alone frequently justifies the exercise.
The cost of running them
A morning a year more than a single rate, once the allocation rule is settled. The recurring work is small; the one-off design work is a few days.
When one rate is right
Small operations. Operations where every job touches every department similarly. Operations where overhead is a small share of cost.
In those cases a single rate is not a compromise, it is the correct answer, and it should be stated as a deliberate choice rather than a default.
The hybrid
One rate for most of the organisation, and a separate rate for the one department that is genuinely different — usually the heavily equipped one.
This captures most of the benefit for a fraction of the complexity and is what most operations should do.
The department that should not have a rate
Service departments that touch no jobs directly: scheduling, quality, maintenance. Their cost is pushed out to the departments they serve rather than recovered on their own hours.
Giving them a rate and charging it to jobs double-counts, because the cost is already inside whichever production rate absorbed it.
How much accuracy the allocation deserves
Not much. The reciprocal methods described in textbooks — where service departments charge each other — rarely move a production rate by more than a per cent or two.
A simple proportional push-out, stated as a convention, is adequate for almost every operation and takes an afternoon rather than a project.
What people ask when departmental rates appear
Why their department's rate is higher than the one next door. The answer is usually premises or equipment, and it is a better conversation than the one a single blended rate produces, which is no conversation at all.
Starting from one and splitting later
The practical route. Begin with a single rate, run it for a year, and look at which departments the jobs actually consume in different proportions.
Splitting on evidence is faster and less contentious than splitting on an organisation chart, and it usually produces fewer departments than anybody expected.
The departmental table
Per department: the pool, the base, the rate, and the reason it is separate. Four columns, three or four rows.
It is a small table, and it answers the question that a single organisation-wide figure cannot: why this job and that job, with the same hours, cost different amounts.