MetandumFREE TOOLS. NO SUBSCRIPTION.Find a calculator My projects
FIND THE QUANTITY ERROR

Read whether a productivity quote is per person or per whole crew.

Publication and review

Author
Metandum Team

14 years of experience in digital web projects.

Reviewer
Metandum Team

14 years of experience in digital web projects.

Published
Last reviewed
Last updated

Choose the Rate Basis

To estimate the time for 138 measured units, first determine what your production rate counts: one productive person-hour or one crew-hour. The Crew Production Duration Calculator returns 2.30769230769 scheduled working days in the published example under either entry method. That matching result depends on matching the rate’s basis to the Workers input. The estimate covers production time using the entered productive hours per worker per day; it does not establish a calendar finish date.

In this example, all figures are hypothetical inputs for the same 138 measured units. One method enters 2.3 units per productive person-hour and four comparable crew members. The other enters an existing rate of 9.2 units per crew-hour and sets Workers to 1 for normalized arithmetic. These inputs express the same assumed output, so the calculator returns the same duration. Choose the method that reflects how the rate was measured.

Define the Measured Work

Before entering a rate, define the 138 units consistently. Count the quantity that the production rate actually represents, such as completed units meeting your chosen task boundary. If the rate is based on installed units, do not enter a broader count that includes material merely delivered or work still incomplete. The calculator uses the task quantity and rate as entered; it cannot decide what qualifies as a completed unit for your project.

Keep the measurement scope aligned across the quantity and rate. If the 138 units combine unlike tasks, phases, or conditions, a single average can hide important differences in output. Where practical, estimate separate quantities using rates that correspond to each portion, then compare those durations in your planning. The published example treats all 138 units as one comparable task quantity. That is an assumption for the arithmetic, not proof that every project unit takes equal effort.

Enter a Person Hour Rate

For the first published method, enter Task quantity as 138, Quantity per productive person-hour as 2.3, Workers as 4, and Productive hours per worker per day as 6.5. Here, 2.3 means each productive person-hour produces 2.3 measured units. The rate is per worker, so the four comparable crew members contribute four sets of productive hours. Keep the rate and worker count on that same individual basis.

The calculator reports 60 productive person-hours and 2.30769230769 scheduled working days. The local arithmetic is 138 units divided by 2.3 units per person-hour, giving 60 person-hours; four workers provide 26 productive person-hours per day at 6.5 hours each, so 60 divided by 26 gives about 2.31 days. The displayed precision is longer than a practical schedule usually needs. For planning, retain the calculator result and communicate a sensible rounded estimate.

Enter an Existing Crew Rate

For the second published method, enter Task quantity as 138 and Quantity per productive person-hour as 9.2, set Workers to 1, and enter Productive hours per worker per day as 6.5. This is normalized arithmetic for an existing rate of 9.2 units per crew-hour. Setting the worker field to one makes the entered hourly capacity act as one crew’s output for the duration calculation.

The calculator displays 15 productive person-hours and 2.30769230769 scheduled working days. In this method, interpret the intermediate 15 hours as 15 crew-hours, because the entered 9.2 rate counts units per crew-hour. Do not call those hours personal labor. The calculator’s field label says person-hour, but the meaning of an existing rate comes from how that rate was measured. Preserve that distinction in notes so nobody later treats 9.2 as output by one worker.

Avoid Counting the Crew Twice

The crew-rate method already includes the output of the whole crew in its 9.2 units per crew-hour. If you multiply 9.2 by four again while also using Workers as four, you count the crew size twice. For 138 units, that mistaken calculation gives 138 divided by 36.8, or 3.75 hours, then 3.75 divided by 6.5, or about 0.58 days. That incorrectly quarters the elapsed time compared with the published result.

Use one of two consistent pairings: a per-person rate with the actual number of workers, or a whole-crew rate with Workers set to 1. If you have a crew rate but want to enter the actual headcount, first convert the rate to a per-person basis only when the crew’s output is reasonably attributable across those workers. In the example, 9.2 divided by four equals 2.3 units per person-hour, which matches the first method.

Set Productive Hours Per Day

Both published methods use 6.5 productive hours per worker per day. This input represents the hours counted as productive for the calculation, not automatically the full length of a shift. Use a value that matches the basis of the rate and your planning assumption. If the day’s available productive time changes, update this field and recalculate; the scheduled days will change even when the quantity and hourly rate stay fixed.

For an on-site decision, consider what your workday assumption includes. If access windows, setup, coordination, inspections, breaks, or interruptions reduce productive time, the 6.5-hour input should reflect the productive time you intend to schedule. The calculator outcome remains arithmetic based on the value supplied. It does not independently measure those project conditions. Decide whether those constraints are already reflected in the rate or in productive hours, and avoid reducing output for the same constraint in both places.

Interpret the Scheduled Days

The result of 2.30769230769 scheduled working days is a duration in days calculated from the entered productive hours per worker per day. It is not a dated completion commitment. To place it on a schedule, identify when the work can begin, which days count as working days, and whether the crew is available for the assumed productive hours. The calculator’s result can inform that decision, but the example does not specify a start date or calendar.

Record Assumptions for Reuse

When you save this estimate, record the 138-unit scope, the rate basis, crew size, and 6.5 productive hours per worker per day together. State whether 2.3 means units per productive person-hour or 9.2 means units per crew-hour. That note prevents a later reader from copying the rate into a different field interpretation or applying headcount again. The two methods agree only because the example’s inputs describe equivalent production capacity.

Questions about this guide

Which rate should I enter if my records say 9.2 units per crew-hour?

Use 9.2 as the existing crew-hour rate and set Workers to 1 for the published normalized method. Interpret the resulting intermediate hours as crew-hours, even though the calculator labels them productive person-hours.

When should I enter four workers?

Enter four when your rate is per productive person-hour, as in the example’s 2.3 units per person-hour. Do not also use four with a rate that already counts the whole crew’s output.

What does the 6.5-hour daily input mean for this estimate?

It is the assumed productive hours per worker per day used to turn hourly capacity into scheduled working days. Use a value that reflects the productive time you intend to plan around.

Should I schedule exactly 2.30769230769 days?

Treat that as the calculator’s arithmetic result for the entered assumptions. Decide how partial working days fit your crew and task sequence, and use a practical scheduling convention when assigning dates.

Use the matching calculator

Updated . Reviewed . Methods and scope.

Related decisions

Connected work guides and comparisons

Browse all work types

Collect your material inputs

Browse material preparation sheets

Evaluate your own supplied alternatives

Browse quantity scenarios