Your engineering team has cut review time, and a client wants to know when you can issue their next plan set. Before you give them a date, put the preparation and senior review on the calendar in the order they have to happen. For example, let’s say a reviewer has ten free hours over two weeks, with only two before the client needs the drawings. If the set takes six hours to review, the date depends on where those six hours can go.
We helped a civil engineering firm move recurring corrections into the preparer's first pass, so fewer of those issues reached the senior engineer. At the six-week follow-up in the pilot offices, senior review took 8.1 fewer hours per plan set, just over one workday. The division also accepted three pursuits it had previously deferred. A year after delivery, the client reported operating margin on net revenue of 20.4%, up from 15.2% at baseline. The client credited about 2.8 percentage points of that increase to the program, with business mix and market conditions contributing the rest.
That experience shows why a review improvement matters to a practice leader who wants to take on more work. The scheduling example below takes the next decision from a request through a confirmed booking, so you'll know which date you can offer and what room you'll have for the next project.
Start with the people who have to do the work
Pick one project and ask what needs to happen before the client can receive the drawings. Write down when the inputs will be ready, who'll prepare the set, who can review it, and when the client wants it issued. Ask both owners how many hours they'll need for that scope. A project can fit the design calendar and still arrive at the reviewer too late, which is why you need both estimates before you commit.
In that example, project P needs ten hours of design preparation followed by six hours of qualified senior review. Its inputs are due at the start of week one, and the client wants the set issued that week. The design lead has twelve free hours in week one and four in week two. Before you tell the client the date works, check when the design lead can finish and when the review lead can take the set.
Count the hours you can still reserve
Start with each person's working hours for the week. Subtract leave and other duties if the calendar still includes them, then subtract the hours they owe to current projects and a buffer for uncertainty. Use the latest estimates of work remaining, including expected corrections. If those estimates already reflect faster reviews, the gain is already in the calendar, so adding the historical savings again would book the same time twice.
Ask the owner when the hours are actually available. Two hours on Monday and four on Tuesday won't help a set that finishes preparation on Thursday. Check for the blocks your own review process requires, and leave a missing estimate or unnamed reviewer open until someone can confirm it.
A calendar like this helps you decide whether review time is holding back a specific project. When the goal is to grow the whole practice, it helps to ask what's keeping the firm from taking on and finishing more of the work it wants.
If you’re an engineering practice leader and want to grow your firm without promising project dates your senior reviewers cannot support, we’ll identify the biggest bottleneck standing in your way, build the plan to remove it, and implement it in eight weeks* or less - guaranteed or we continue to work for free and you don’t pay.
Find my bottleneck* Eight-week delivery, or twelve weeks when substantial data foundations are required, as agreed before work begins. If a covered stage fails its agreed benchmarks, we provide up to four additional weeks of remedy work at no charge, then waive or refund that stage’s fee if it still fails. Successfully delivered stages remain payable. Agreed client-caused delays pause the clock. Delivery guarantee terms.
Test the date the client asked for
The review lead for project P has 24 usable hours each week after leave and other duties. Current work needs 18 hours in week one and 12 in week two. For this example, the lead keeps four hours open each week for uncertainty, which leaves two hours in week one and eight in week two.
| Review lead's calendar | Week 1 | Week 2 |
|---|---|---|
| Usable hours after leave and other duties | 24 | 24 |
| Hours committed to current work | 18 | 12 |
| Hours held for uncertainty | 4 | 4 |
| Hours available to reserve | 2 | 8 |
| P's review hours for requested week-one issue | 6 | 0 |
| Hours left or short under the request | 4 short | 8 free |
| P's review hours if issue moves to week two | 0 | 6 |
| Hours left after P's confirmed booking | 2 | 2 |
Design can finish its ten hours in week one. The review lead would still be four hours short that week, even though ten review hours are free across the two weeks. A week-two issue can work if design confirms the handoff, the reviewer confirms six hours before issue, and the client agrees to the new date. If the client needs the original date, check whether another qualified reviewer can confirm the required time. If neither date nor staffing can change, defer or decline the commitment and keep the required review in place.
Reserve the time before offering it again
Suppose the client agrees to week two and both owners confirm the sequence. Once the commercial owner clears the commitment, book the preparation and review in the calendar your team already uses. Give the six-hour review booking an ID, such as P-R1, so the person handling the next request can see exactly which hours are taken.
Now a second project, Q, needs four review hours in week two. The lead had eight before P was confirmed and has two left, so Q needs a different date or a confirmed qualified reviewer. If P is still waiting for the client's answer, show its time as a tentative hold with an expiry and a confirmation owner. That gives the next scheduler a way to resolve the hold before offering those hours.
If P's inputs arrive late, check when design can finish and whether the review booking still fits. If either stage moves, have the project manager update the affected bookings and dates. At the next schedule review, compare the estimates with actual hours and check whether the new work displaced another commitment. That gives the team a better basis for the next date it offers.
Put one live request through the project card
Use one row per field for a project you're considering this week. Have the project manager fill it in with the design and review leads, then take the resulting date to whoever owns the client commitment.
| Field | Copyable blank entry | Worked example for P |
|---|---|---|
| Request and commercial status | [Scope, proposed or accepted, and fee owner] | One plan set. Proposed, with the practice lead confirming terms. |
| Inputs and preparation | [Input-ready date, preparer, hours, and completion date] | Inputs at start of week one. Design lead needs ten of twelve available hours and finishes that week. |
| Qualified review | [Named reviewer, required work, hours, and estimate basis] | Review lead needs six hours for the agreed scope, confirmed by the lead. |
| Calendar cutoff and existing load | [Calendar version and remaining commitments by person and week] | Two-week calendar v1. From 24 usable review hours each week, subtract 18 and 12 for current work and four each week for uncertainty. |
| Requested issue and first shortage | [Date, stage that fails, and hours short] | Week-one issue. Review needs six hours and has two, so it's four hours short. |
| Feasible dates and confirmation | [Preparation, review, issue, and owner and client confirmations] | Design prepares in week one, review follows in week two, and issue follows completed review. Both leads and the client confirm. |
| Booking and competing requests | [Booking IDs, remaining capacity, and conflicts] | P-R1 books six hours in week two. Q needs four and only two remain. |
| Changes and next check | [Trigger, person responsible, and next calendar review] | Project manager checks changes to inputs, scope, or staffing and compares actual hours at the next schedule review. |
If you have a project waiting for a date, fill in the card and find the first stage that can't fit. You'll have a specific date to offer, a person to ask about a reassignment, or a clear reason to hold the commitment. Once the date is agreed, reserve the time so the next request starts with an accurate calendar.
If you’re trying to grow your own firm, start with your goal, look at what it'll take to achieve it, and then identify what's keeping you from taking action. Just remember that every firm is different and that time lost to repeat corrections was just their bottleneck and it might not be yours.
If you’re an engineering practice leader and want to grow your firm without promising project dates your senior reviewers cannot support, we’ll identify the biggest bottleneck standing in your way, build the plan to remove it, and implement it in eight weeks* or less - guaranteed or we continue to work for free and you don’t pay.
Find my bottleneck* Eight-week delivery, or twelve weeks when substantial data foundations are required, as agreed before work begins. If a covered stage fails its agreed benchmarks, we provide up to four additional weeks of remedy work at no charge, then waive or refund that stage’s fee if it still fails. Successfully delivered stages remain payable. Agreed client-caused delays pause the clock. Delivery guarantee terms.