Enhancing Worker Efficiency with the Rowan Premium Plan

Every factory floor runs on a quiet negotiation: how do you pay a worker fairly for speed without tempting them to cut corners? Piece-rate systems reward pure output, but they can push workers to rush and compromise quality. Straight time wages are safe but give no reason to work faster. The Rowan Premium Plan sits between these two extremes, and it does something clever with the maths that most other incentive schemes don’t: it slows down its own bonus as time-saving gets extreme. Here’s how it works, why it was designed that way, and where it fits into how labour costs are recorded in India.

What is the Rowan Premium Plan? 🔗

The Rowan Premium Plan is a wage incentive system that guarantees a worker’s time wage and adds a bonus linked to the time saved against a standard time. It was developed by James Rowan as a refinement of the older Halsey Plan, and it remains one of the most widely taught premium bonus systems in cost accounting because of how it balances productivity with restraint.

Where it fits among wage systems 🔗

Cost accounting recognises several ways to pay workers: straight time rate, straight piece rate, and a family of “premium bonus” plans that blend the two. Halsey, Rowan, Taylor’s differential piece rate, and Gantt’s task and bonus plan all belong to this premium bonus family. What separates Rowan from the rest is the way it calculates the bonus, not just as a fixed share of time saved, but as a proportion that itself shrinks once a worker starts saving too much time.

The Rowan formula explained 🔗

The total earnings of a worker under this plan are calculated as:

Earnings = (Time Taken × Rate per hour) + [(Standard Time − Time Taken) / Standard Time] × Time Taken × Rate per hour

In short: Earnings = T×R + [(S−T)/S] × T×R, where T is the actual time taken, S is the standard time allowed, and R is the hourly wage rate. The first part of the formula, T×R, is the guaranteed time wage. The second part is the bonus, calculated as the fraction of time saved (relative to standard time) applied to the wage for the actual time worked.

A worked example: seeing the numbers 🔗

Numbers make this easier to follow. Say a worker is assigned a job with a standard time of 10 hours, at a wage rate of ₹50 per hour. Here’s how earnings change as the worker gets faster:

Notice the pattern. The bonus is highest, ₹125, exactly when the worker takes half the standard time (5 hours out of 10). Push beyond that and save even more time, and the bonus actually falls back to ₹80, the same as it was when the worker saved far less time. This isn’t a coincidence; it’s the whole point of the formula.

The built-in speed limit: why saving too much time doesn’t pay 🔗

Mathematically, the Rowan bonus peaks when time taken equals exactly half the standard time, and it falls symmetrically on either side of that point. This means that beyond the 50% mark, every additional hour saved adds less to the bonus than the one before it, and eventually the bonus starts shrinking in absolute terms too.

This diminishing curve is a deliberate safeguard. If a worker could earn an ever-increasing bonus simply by going faster and faster, there would be a strong temptation to rush, skip checks, and let quality slip, especially once genuine time-saving from skill runs out and shortcuts take over. By capping the reward for extreme speed, the Rowan Plan discourages workers from sacrificing workmanship just to chase a bigger cheque.

Rowan vs Halsey: who wins when 🔗

The Halsey Plan pays a simpler bonus: a fixed percentage, usually 50%, of the time saved, applied at the hourly rate. Comparing the two on the same job reveals something useful:

Whenever time saved is under 50% of the standard time, the Rowan Plan pays a slightly larger bonus than a 50-50 Halsey split, which is exactly why it’s often seen as more generous for genuinely efficient work. Once time saved crosses that halfway mark, though, Halsey overtakes it comfortably. This crossover, where the bonus under the two plans becomes exactly equal when time taken is 50% of the standard time, is one of the most tested concepts in cost accounting exams, precisely because it explains the plan’s logic so cleanly.

Why the guaranteed time wage matters 🔗

Both Halsey and Rowan share one non-negotiable feature: the worker is never paid less than the time wage, regardless of how the bonus calculation turns out. This isn’t just good practice, it aligns with how Indian labour law treats wages. The Code on Wages, 2019, which consolidated the Minimum Wages Act and three other central laws, requires that workers receive fair wages and protection against exploitation as a matter of statutory right, not employer discretion. Any incentive scheme, however it calculates the bonus on top, has to sit on this floor. The Code also prohibits employers from paying below the minimum wage fixed by the central or state government, which is exactly the guarantee the T×R portion of the Rowan formula is built to satisfy.

Advantages of the Rowan Premium Plan 🔗

A few reasons this plan is still taught and used:

• Wage security: Workers are guaranteed their time-based pay no matter what, which reduces anxiety around income.
• Built-in quality control: Because the bonus curve flattens and then falls after the 50% mark, workers have less reason to rush and cut corners.
• Rewards genuine efficiency: For the common range of time-saving (below 50%), it pays out more generously than a flat-share plan like Halsey.
• Useful for new or inconsistent workers: Because the bonus doesn’t reward extreme speed disproportionately, it works reasonably well even when standard times aren’t perfectly calibrated for every worker.

Limitations to keep in mind 🔗

The plan isn’t without drawbacks:

• Calculation complexity: The formula is harder to explain to workers on the shop floor than a simple percentage-of-time-saved model.
• Weak incentive at high efficiency: Once time saved crosses 50%, the bonus growth slows sharply, which can feel demotivating to genuinely skilled workers who keep improving.
• Dependence on accurate standards: The entire scheme only works if the standard time is set correctly through proper time and motion studies. An unrealistic standard time skews the bonus for everyone.
• Employers must share efficiency gains: Some managements are reluctant to hand over a portion of productivity savings as bonus, preferring the more predictable cost of straight time wages.

Where this fits in cost records 🔗

Bonus payments under schemes like Rowan aren’t a side calculation kept separate from the books. Under the Cost Accounting Standard on Employee Cost (CAS-7), incentive payments and bonuses form part of employee cost and must be identified with the relevant cost centre or department, just like basic wages. This matters for accurate product costing: if a company under-records or over-records bonus payouts, the labour cost per unit gets distorted, which in turn affects pricing and profitability decisions. Understanding how the Rowan formula behaves isn’t just an academic exercise, it feeds directly into how accurately a business can price what it makes.

What do you think? If you were designing a wage incentive scheme for a factory today, would you accept a plan that discourages workers from saving more than 50% of the standard time, or does that cap feel unfair to your most efficient workers? And how would you go about setting a standard time that both management and workers would trust?

References

1. https://www.accountingnotes.net/cost-accounting/labour/incentive-plans-for-remunerating-workers-cost-accounting/14970
2. https://icmai.in/upload/Students/MTPSyl2012June14/Inter/Set1/Paper8-Solution.pdf
3. https://www.pib.gov.in/PressReleasePage.aspx?PRID=2193095
4. https://prsindia.org/billtrack/the-code-on-wages-2019
5. https://www.icmai.in/upload/CASB/docs/Standards/CAS-7-LR-01042017-Revised.pdf