A landscape crew can finish a job in two days and still consume very different amounts of labor.
That is why a labor estimate should be built in labor-hours, not only elapsed days.
If three people are on site for two eight-hour days, the job uses:
3 people × 2 days × 8 hours = 48 labor-hours
The calendar says two days.
The cost model needs 48 hours of labor input.
Break the job into operations
Do not begin with:
“This feels like a two-day job.”
Break the work down first.
Depending on the project, operations may include:
- mobilization;
- site protection;
- removal or demolition;
- excavation;
- hauling;
- grading;
- bed preparation;
- material staging;
- installation;
- cutting or finishing;
- cleanup;
- demobilization.
Then assign labor-hours to each operation.
A bottom-up plan is easier to challenge because you can ask which individual line is uncertain instead of arguing about one total.
Connect quantity to time with production rates
A production rate links physical work to labor.
Examples include:
- plants per labor-hour;
- labor-hours per plant;
- square feet per labor-hour;
- cubic yards spread per labor-hour;
- linear feet per labor-hour;
- tons moved per labor-hour.
Either direction can work.
What matters is that the company uses a definition people understand consistently.
Suppose several comparable shrub jobs produced a combined 69 labor-hours for 240 shrubs.
That is:
69 / 240 = 0.288 labor-hours per shrub
That number is not a universal planting standard.
It is evidence about one company’s performance under the conditions represented by those jobs.
If the next site has more difficult access, the estimator may deliberately use a higher labor assumption and record why.
The important improvement is that the adjustment is visible.
Paid hours and productive hours are not the same
A worker may be paid while:
- loading;
- fueling;
- cleaning the shop;
- attending safety meetings;
- driving;
- waiting;
- collecting material;
- performing field production.
The estimating system needs a deliberate way to recover those hours.
Pretending that every paid hour becomes installation output makes productive-capacity assumptions look better than they really are.
That problem matters twice:
- when estimating the labor required for a job;
- when using productive labor-hours as an overhead recovery base.
If the denominator is unrealistic, the resulting rate can under-recover real company cost.
More crew members do not always create linear speed
Two people do not automatically perform an eight-hour one-person task in four hours.
The work may bottleneck around:
- one machine;
- one narrow gate;
- one wheelbarrow route;
- one saw;
- one skilled installer;
- a restricted staging area.
Sometimes adding people improves production dramatically.
Sometimes it mainly adds waiting.
Estimate the system, not just headcount.
Build unfamiliar labor from the bottom up
For a job without strong historical data, create an operation table.
Useful columns are:
- operation;
- quantity;
- production assumption;
- crew or role;
- labor-hours;
- note or source.
Then ask:
- Which operation has the least reliable evidence?
- What site condition could slow it down?
- What comparable completed job is closest?
- Is setup included?
- Is material handling included?
- Is cleanup included?
- Is disposal travel included?
- Is the crew mix appropriate?
A labor total becomes useful when you can explain how it was built.
Keep employer labor cost separate from pay rate
An employee’s wage is not automatically the company’s full cost of providing one productive field hour.
Depending on the business and jurisdiction, employer labor cost can also involve items such as payroll costs, workers’ compensation, benefits, and paid nonproductive time.
The correct internal rate should come from the company’s own records and professional accounting guidance where appropriate.
Do not copy a labor-burden percentage from a generic example.
The estimating principle is simpler:
Know what your labor rate includes.
If a cost is already inside the labor rate, do not accidentally recover it again elsewhere.
Review the job after completion
The most valuable labor database is built from clean, comparable records.
For selected jobs, record labor by major operation rather than only the whole project.
If a crew reports only:
8 hours — Smith Residence
you know the total crew-clock time, but not whether excavation, planting, pavers, or cleanup caused the variance.
For important operations, capture enough detail to improve the next estimate.
Use context tags such as:
- easy, moderate, or difficult access;
- hand work or machine-assisted;
- plant size;
- soil condition;
- crew size;
- haul distance;
- new construction or existing landscape.
Then investigate outliers before averaging them into a “standard.”
The goal is not perfect prediction.
It is a labor estimate that becomes more evidence-based over time.
Continue with estimate versus actual and production-rate learning.