The best three-week lookahead I ever inherited fit on one 11x17 sheet and told me everything I needed to know before the Monday coordination meeting even started. The worst one I ever saw was a 40-column spreadsheet that a project engineer spent two hours a week feeding and that no foreman ever looked at. The difference wasn't the software. It was the template — what it asked for, what it left out, and how it was organized. Get the template right and building next week's plan takes twenty minutes and the field actually uses it. Get it wrong and you've built a data-entry chore that produces a document nobody trusts.
This is a practical guide to designing a three-week lookahead template that earns its keep. Whether you build it in a spreadsheet or in dedicated software, the same principles apply. I'll walk through the fields that matter, the ones that quietly kill your template, and how to structure the three weeks so the thing reads like a plan instead of a database dump.
Start with the job the template has to do
A three-week lookahead exists to answer one question every week: what work is ready to go, and what has to happen in the next two weeks to keep the week after that ready? Everything on your template should serve that question. If a field doesn't help someone either commit to work or clear a constraint, it's decoration.
That framing changes how you design. You're not building a project archive. You're building a make-ready worklist with a commitment week bolted onto the front. The template's whole reason for living is to surface the stuff that isn't ready yet — the missing submittal, the RFI that's been open eleven days, the deck that the concrete crew won't release until Thursday — while there's still time to do something about it.
The core columns — and why each one earns its spot
Keep the activity backbone lean. In fifteen years of running these, I've never needed more than a handful of columns to describe the work itself:
- Activity description — Written the way the crew talks. "Set and pour Grid E–H footings" beats "Foundation work, Zone 2." If a foreman can't tell what the work is from the description alone, the description has failed.
- Location — Level, area, grid line, unit number. This is the single most abused field on most templates. Pick a naming convention for the whole job on day one and never deviate. "Level 3 North" has to mean the same thing on the structural sheets, the lookahead, and out of the super's mouth at the OAC meeting.
- Responsible party — The trade and the specific foreman or company, not just "MEP." When two activities collide, you need to know exactly whose phone to call.
- Duration, start, finish — Working days, not calendar days. Note it clearly so nobody's confused about whether Saturday counts.
- Status — Not started, in progress, complete, or blocked. Four states. That's plenty.
That's the whole activity line. Resist the urge to add "cost code" and "CSI division" and "bid package number" just because you have them. Nobody in the field trailer plans work by CSI division. Every column you add is a column somebody has to maintain, and maintenance is where lookaheads go to die.
The constraint fields are the point of the whole exercise
Here's the part most templates get backwards: they treat constraints as an afterthought — one skinny "notes" column crammed at the right edge. Flip that. The constraint tracking is the lookahead. A schedule of work that's already ready doesn't need a lookahead; you'd just do it. The lookahead earns its money on the work that isn't ready.
Give constraints real fields:
- Constraint type — A short standard list so you can spot patterns: material, submittal/info, prerequisite work, labor, equipment, permit/inspection, access/space, engineering. When you notice half your blocks are "submittal," that's a message about your procurement, not your field crews.
- Description — One plain sentence. "Waiting on approved shop drawings for stair rail" — not "coordination pending."
- Owner — A person's name. Constraints without an owner don't get cleared; they get discussed. Every open constraint needs exactly one throat to choke.
- Need-by date — The date the constraint has to be gone for the work to start on plan. This is the field that turns a wish list into a countdown. It tells you which of today's open items are actually on fire.
- Status — Open, in progress, cleared.
The discipline that makes this work: an activity does not move into Week 1 — the commitment week — until every one of its constraints reads "cleared." That's the whole make-ready mechanism in one sentence. If you commit to work that still has an open constraint, you're not planning, you're gambling, and the field learns fast that your Week 1 is fiction.
Organize the three weeks by what you're promising, not just by date
The three columns aren't three equal weeks. They carry different weight and different levels of detail, and your template should make that obvious at a glance.
Week 1 is the commitment week. This is what you're telling everyone will actually happen. It should be fully constraint-free, resource-loaded, and specific down to the crew. Treat anything in this column as a promise you're making to the other trades. This is where you track whether it happened — more on that in a second.
Week 2 is active make-ready. This is the week you're clearing constraints hard. Every open item here should have an owner working it right now. By Friday, Week 2's activities should be clean enough to slide into next Monday's commitment column. If they can't, you've found your problem a week early — which is exactly the point.
Week 3 is the heads-up week. Lighter detail, coarser activities, but it's where you catch the long-lead constraints — the material that needs a four-week order, the inspection that has to be scheduled, the engineering answer that takes ten days to come back. Week 3 exists so nothing in it surprises you when it becomes Week 1.
Design the sheet so those three roles read differently — heavier rule between the commitment week and the make-ready weeks, a clear header on each. When a foreman glances at it, the eye should land on Week 1 first. That's the work he owns this week.
Track whether the commitment actually happened
A lookahead template that only looks forward is only doing half its job. Add two small fields tied to the commitment week and you get a feedback loop that quietly makes the whole crew more reliable:
- Did it complete? (yes/no) — Checked at the end of the week against what you committed to on Monday.
- If no, why? — A short reason from a standard list: prerequisite not done, material late, manpower short, weather, changed priorities, rework, design/RFI.
Count the yeses against the total and you've got your Percent Plan Complete — the single most honest number on any jobsite. A crew running 50% PPC is a crew whose Monday plan is basically noise; you can't sequence trades around promises that hit half the time. Push toward the 70s and 80s and the whole flow of the job tightens up. And the "why not" reasons, tallied over a month, tell you precisely where to fix the system. If a third of your misses are "prerequisite not done," your problem is trade sequencing, not lazy crews.
Where good software beats a spreadsheet
You can absolutely run all of this in Excel, and plenty of great supers do. But a couple of things get painful by hand as the job scales, and they're the same couple of things a purpose-built tool like LookAheadWall handles without you thinking about it. The big one is rolling the weeks forward — every Monday, Week 2 becomes Week 1, Week 3 becomes Week 2, and a fresh Week 3 appears. Do that by hand across a dozen trades and you'll eventually fat-finger a row into the wrong week. The other is filtered views: the drywall foreman wants to see only his work, the super wants to see only what's still constrained, the PM wants the whole board. In a spreadsheet that's a lot of copy-paste; in the right software it's a click, and everybody's looking at the same underlying plan instead of six diverging copies. Location-based, visual planning also makes trade collisions jump out — two crews stacked in the same area on the same day is obvious on a wall board and easy to miss in a list.
None of that changes the template design. Whatever you build in, the fields and the three-week structure are the same. The tool just removes the bookkeeping so you spend your Monday planning, not maintaining a spreadsheet.
The mistakes that kill templates
Nearly every dead lookahead I've seen died from one of these:
- Too many fields. The template that asks for everything gets fed nothing. If you can't keep it current in twenty minutes, it's too fat. Cut columns until it hurts, then add back only what you truly missed.
- Constraints buried. If the "what's blocking this" information is hard to see, people stop entering it, and the lookahead becomes a to-do list — which the field already has.
- Inconsistent location names. The moment "L3-N" and "Level 3 North" and "3rd flr north" all appear on the same job, filtering breaks and coordination gets sloppy.
- No commitment discipline. If constrained work is allowed into Week 1, PPC collapses and the crews stop believing the plan.
- Built in an office, never tested in the field. Run any new template on one real project for a month before you standardize it. The foremen will tell you within two weeks what's missing and what's noise.
Build it, then let it earn changes
Start narrow. Activity backbone, real constraint fields, three weeks with distinct roles, and the two PPC fields on the commitment week. That's a template that already does more than most. Run it live, sit in on a few Monday meetings, and watch where people reach for a pen to write something the template didn't capture — that's your signal to add a field. Watch which columns are always blank — that's your signal to cut one.
A three-week lookahead template isn't a form to fill out. It's the operating rhythm of the job written down: commit to ready work, clear next week's constraints, look far enough ahead that nothing blindsides you. Keep the template lean, make the constraints impossible to ignore, and hold the line on committing only to work that's genuinely ready. Do that and you'll have the one-sheet plan the whole trailer actually reads — the kind you inherit and think, finally, somebody who gets it.