The two-week look-ahead, translated into names and hours

Thursday morning, the GC’s coordination meeting. The look-ahead comes out as a PDF: three weeks of bars across the top, activities down the side, your scope sitting in four of them. The superintendent goes around the table asking everyone to confirm.

You say yes, because the bars do not look wrong.

Two weeks later you are short four people on Level 3 and the GC’s schedule says you are late. Nobody lied in that meeting. The problem is that the look-ahead answers the GC’s question, and you confirmed it as though it answered yours.

The look-ahead is the GC’s artifact, not your plan

A GC’s look-ahead exists to sequence trades and protect the critical path. It is built from activities and durations: Level 3 overhead rough-in, 8 days, start Monday. That is the correct unit for the person coordinating nine trades in one building.

It contains none of the four things you need to staff the work:

• how much work is in that bar, in your units;
• how many hours that is at the rate your crews actually install;
• how many bodies that is across the days available;
• which specific people, who are also on two other jobs.

So the translation is yours, and nobody else in that room can do it. This article is that translation, and then the five rules that keep it honest.

What the GC’s version does give you

Read it for four things, and read it with a pen.

The areas that are supposed to be available to you, and on which days. That is the real content of the bar.

The predecessor. Something has to be complete before your bar starts — deck poured, walls framed, ceiling grid out, inspection passed. The look-ahead shows it as an earlier bar and never as a condition. It is a condition.

Who else is in there with you. Two trades in one ceiling on the same days is a stacking problem that gets decided by whoever shows up with more people, unless somebody raises it on Thursday.

What you are about to commit to publicly. Everything you confirm in that meeting becomes the baseline you are measured against, and the minutes are the record.

The translation, in four moves

1. Quantity by area. The bar says Level 3. Your estimate says 2,400 feet of conduit, 18,000 square feet of board, 12 VAV boxes, 40 fixtures. Pull the quantity for that area out of your own takeoff or your schedule of values line, not out of the bar’s length.

2. Hours. Divide the quantity by the install rate your own crews have actually produced on a finished job of this type. Not a published rate, and not the estimator’s number if that number has never been checked against a completed job. Building that units-per-hour rate out of your own history is its own exercise, and it starts with recording hours by job and by area — which is what makes the next look-ahead arithmetic instead of a guess.

3. Crew size. Hours divided by the working days in the bar, divided by eight. If the bar is eight days and the work is 640 hours, that is ten people every day for two weeks.

4. Names. Ten is not a plan. Ten with names is a plan, and it is where most look-aheads quietly fail, because the tenth name is already committed on another job.

If step three produces a number you do not have, you have found the single most valuable thing in the meeting — and the only moment it is cheap to say.

Three things to say on Thursday, and two to ask for

Say the manpower you will actually have. “I can put six on Level 3 Monday and eight from Wednesday” is a useful sentence. “Yes” is not. A GC can re-sequence around a number told early; nobody can re-sequence around a shortage discovered in week two.

Say the predecessor you need, by date. “I start Monday if the grid is out of the east half by Friday.” Now the dependency is on the record as a condition rather than as a hope.

Say the stacking problem. If the mechanical contractor is in the same ceiling the same week, the superintendent is the only person who can fix it, and only before it happens.

Then ask two questions and listen for a date: who confirms the predecessor is complete, and what the plan is if it slips.

Get the answers into the minutes. If the minutes do not reflect what you said, send one short email the same day stating your commitment and your condition. That email is dated, and a dated record is the entire difference between a delay you get time or money for and a delay that becomes your problem — which is what documenting a delay is about.

Where it collides: three jobs, one journeyman

Each GC hands you a look-ahead for its own job and assumes you are infinitely elastic. You are not. Your constraint is not crews, it is names — the foreman who can run a layout, the one tech who commissions, the two people who can finish a level 5 wall.

So the look-ahead you work from is not the GC’s. It is one page with every job across the top and the next ten working days down the side, filled with names. Build that page and the collisions are visible before they happen: the same name in two columns on Tuesday.

On most weeks that list is short, and every name on it is someone you depend on. That is the week’s real risk, and it is invisible in three separate PDFs.

The manpower curve nobody writes down

Work does not arrive flat. A rough-in that needs eleven people Monday through Wednesday and four on Thursday is normal, and the ramp is the part that costs money: the extra four came off another job, or came in on overtime, or came back for a second mobilization because the area was not ready when they got there.

Write the curve, day by day, even roughly. A ramp you planned is a cost you priced. A ramp you discovered is a premium you paid.

Why writing it down pays off next week

The look-ahead’s second job is to be the baseline your daily logs are read against.

Planned six on Level 3; logged four, with two of them on Level 2 instead. That difference is worth money if you know why: the area was not ready, or the GC’s predecessor slipped, or somebody got pulled to another job by your own office. The first two belong in a change event or a delay notice the same week. The third is a decision you made, and you should at least know you made it.

Without a written plan, the log is just a record of what happened, with nothing to compare it to. That comparison is the whole reason the exercise is worth an hour on Friday.

Five rules that keep a look-ahead honest

1. Only commit people you can name. A bar staffed by “a crew” is a bar staffed by nobody.
2. Two weeks, not six. Beyond two weeks you are writing fiction, and fiction nobody updates gets used anyway.
3. One owner, one update, same day every week. Thursday after the GC meeting, published Friday morning. A look-ahead that is sometimes current is worse than one everybody knows is weekly.
4. Mark the predecessor on every line. The line without one is the line that will not start.
5. Never show capacity you do not have to be agreeable. It buys you one pleasant meeting and costs you the next six.

How SubMark handles it

Nothing turns the GC’s look-ahead into your crew plan, and nothing should pretend to — the translation above is judgment about your own crews. What SubMark does is hold the output of it, across every job, and then show you what actually happened against it.

• One calendar across every job, in a month view, a week grid or a list. Each job carries a color.
• Schedule a crew or a named individual onto a job, on a date, with estimated hours and a note. A crew is a named group with members and a foreman, built once; an individual is one person on one job on one day.
• Double-bookings are flagged as you create them. When the same crew or the same named worker is committed to two jobs on the same date, both entries are flagged and the toolbar carries a conflict count that lists each one by name, with both job names and the date. Someone with the right permission can dismiss a conflict when the split is deliberate, though the next detection run can flag the same pair again. Before saving a worker entry you can also check that person’s availability for the date: whether they are already scheduled by name, to which jobs, and for how many hours (a crew they belong to is not counted).
• Then the other half, which is the one that matters on Friday. Where Workers Are reads the day’s labor logs and groups them by job — who was on which job, with a date you can scrub backwards through. You read it beside the plan you wrote, and the difference is the conversation.
• The same hours feed job costing at each worker’s wage rate, so the week’s labor shows up as cost on the job without anybody retyping a timesheet.
• Field users are free and unlimited. Foremen and crews see their own schedule on a phone as a read-only week agenda; editing stays in the office on purpose.

Three limits worth knowing before you sign up. The conflict check is per date, not per hour — it tells you somebody is committed to two jobs Tuesday, not that the two commitments add up to eleven hours. Crew entries and individual entries are checked separately, so a crew on one job and one of its members scheduled by name on another the same day is not flagged. And there is no built-in planned-versus-logged report; you read the calendar and the logs side by side.

Our pricing is one company subscription that includes three office users, a per-seat price for each one after that, and a 14-day free trial, no card needed. Crew scheduling for commercial subs goes deeper on the calendar itself.

Do this on Thursday

1. Take the GC’s next look-ahead and write your quantity against each bar that is yours.
2. Convert one bar to hours and bodies using a rate from your own finished job. Just one, to see how close the bar is.
3. Name the people. Where you cannot, that is Thursday’s message to the superintendent.
4. Write the predecessor on every line, with the date you need it by, and send the one-paragraph confirmation email.
5. On Friday, put last week’s plan beside last week’s logs and mark every line that differs. Four weeks of that tells you which job is being used as everybody’s float.