Define one unit of work
Choose a unit that matches the handoff, such as one takeoff package, one bid comparison, or one drawing log update for a defined sheet set. Write the definition so two reviewers would count the same item the same way. A unit that changes size from week to week makes every trend meaningless.
Keep the definition beside the dashboard and revise it only with a dated note. Different work types need separate units rather than one blended score. A takeoff package and a quote log update consume different attention and produce different failure modes.
The estimating manager service page describes the oversight role that uses these measures, and the weekly handoff guide shows where the numbers should be discussed. Keep a short definition sheet next to the dashboard so a new reviewer counts the same way. A blended score hides the work type that is actually consuming capacity.
If takeoffs take longer than quote logs, one average makes both look acceptable and neither look urgent. Report each unit separately for two months before deciding whether a combined view is useful. Most teams find the separate view answers the capacity question without the blend.
Track cycle time
Cycle time starts when the request is complete enough to work and ends when the handoff is accepted. Record both timestamps, not just the completion date. A fast completion on an incomplete request creates rework, which is why the start definition matters.
Report the median and the oldest open item rather than an average that hides the tail. Separate waiting time from working time. If a package waits two days for a missing drawing, that delay belongs to the handoff, not to the assistant.
The distinction helps the estimating lead fix the intake before asking for more production. It also prevents a capacity conversation from turning into a blame conversation. Record the handoff date in the same time zone for every project so the cycle time is comparable.
If the team works across zones, store the timestamp in UTC and show local time only in the report. Review the longest three items each month and ask what delayed them. The answers usually point to intake problems rather than production speed.
Adjust for quality
A throughput number without rework is a volume number. Count corrections that change a quantity, a scope row, or a bid total, and report them beside the completed units. A simple quality-adjusted output divides accepted units by accepted plus reworked units.
The result is not a performance rating, but it shows whether speed is being bought with rework. Use the correction causes from the review log rather than a general defect count. If most rework comes from an unclear brief, the fix is upstream.
If most comes from a missing source, the fix is intake. The measure should point to a change someone can make. Do not use the rework rate as a standalone ranking of assistants.
The same rate can mean a hard project mix or a weak brief, and those causes need different responses. Pair the rate with the correction causes and the project type before drawing a conclusion. The measure is a prompt for review, not a verdict.
A correction that changes a note but not a number should be counted separately from one that changes a quantity. Mixing the two makes the quality signal look worse than the estimate risk actually is.
Use two counts, material and nonmaterial, and report the material count in the monthly summary. That distinction keeps the review focused on changes that affect the bid.
Review capacity, not utilization
Utilization asks how busy the assistant looks, while capacity asks how much accepted work the team can absorb before quality falls. Track the point where cycle time rises and rework increases, then treat that point as the practical ceiling. A team at full utilization with rising rework is not producing more value.
Plot cycle time against open units to see where the curve turns upward. Plan the next batch against the ceiling rather than the best week. Leave room for questions, revisions, and the unexpected package that arrives before a bid.
The AACE recommended practices supports the idea of a documented review process, but the ceiling itself has to come from your own records. A plan that assumes the best week will fail as soon as a bid package arrives with missing drawings.
Report in plain language
A monthly report should answer three questions: what was accepted, how long it took, and what had to be corrected. Add the oldest open item and the capacity headroom for the next two weeks. Avoid a wall of charts that no one reads.
One page with the definitions attached is enough for a management review. Keep the raw counts available for anyone who wants to check the summary. Report the same way each month so a trend can form.
If the definition changes, show the break in the series instead of pretending the old and new numbers are comparable. A short note above the table can explain the break without hiding it. Send the report to the estimator and the assistant lead at the same time so both see the same numbers.
Add a short note on what changed since the prior month and what the team will try next. Keep the definitions in an appendix rather than repeating them in every email. A report that invites a specific question is more useful than one that invites a general reaction.
| Measure | Definition | Use |
|---|---|---|
| Accepted units | Handoffs accepted without material rework | Volume trend |
| Cycle time | Complete request to accepted handoff | Capacity planning |
| Rework rate | Corrected units divided by accepted plus corrected | Quality signal |
| Oldest open item | Age of the oldest unfinished handoff | Queue health |
