Every superintendent I know has a folder on their laptop called something like "Old Schedules" — a graveyard of Gantt charts and spreadsheets from jobs that are long closed out. The instinct is right: you finished a healthcare TI last spring that ran clean, so why not start the next one from it? The problem is that a copied schedule is a photograph of one job on one site with one set of subs. A real template is different. It captures the sequence and the judgment that made the last job work, strips out the site-specific noise, and gives you a running start on the next one without pretending the next one is identical.
That distinction is the whole game with templates. Done right, they turn hard-won field knowledge into something the whole company can reuse. Done lazily, they hard-code one crew's mistakes into every future project. Here's how to build them so they help you instead of quietly steering you wrong.
Start With Sequence Templates, Not Date Templates
The most valuable thing to template is the order of operations for a given work type, not the calendar. A copied schedule brings the dates with it, and dates are the first thing that's wrong on the new job. What you actually want to preserve is the trade-flow logic: the chain of who follows whom through a space, and the buffers between them.
Take a typical interior buildout. A sequence template for that work type should carry the backbone every one of those jobs shares:
- Layout and top-track, then in-wall rough-in — plumbing, then HVAC, then electrical and low-voltage, because the big pipe wins and the wire is the most flexible.
- A hard hold for in-wall inspection before anyone hangs a sheet of rock. This is the single most-skipped dependency in copied schedules and the one that costs the most when it's missed.
- Insulation, one-side board, MEP trim prep, then close the wall.
- Tape and finish, then a real 1–2 day buffer for the wall to dry and get sanded before paint. Not zero. Somebody always tries to make it zero.
- Prime, ceiling grid, above-ceiling rough and inspection, then ceiling tile — and grid goes in before flooring so the trades on lifts aren't standing on your new finish floor.
- Flooring, paint finish coat, trim-out, fixtures, then final clean and punch.
Notice that none of that has a date on it. It has an order, a couple of mandatory inspection holds, and two or three named buffers. That's what makes it portable. When you build these as reusable sequences in a look-ahead tool — LookAheadWall does this with connected trade flows, which is exactly the use case — you're saving the dependency chain, and the actual dates fall out of the start you give it on the new job.
Bake In Realistic Durations and Buffers
Templated activity durations are only worth anything if they came from jobs you actually ran, not from the number someone wished for in a bid meeting. Pull your production rates from completed work. If your framing crew historically hangs and boards about 1,500 square feet of wall a day on light-gauge interior partitions, that's the number that belongs in the template — not the optimistic figure a sub throws out when he's trying to win the job.
Buffers matter as much as the durations, and they're the first thing people delete to make a schedule "fit." A few that earn their place in almost any template:
- Inspection turnaround. Whatever your AHJ actually gives you — often next-day, sometimes 48 hours in a busy jurisdiction — bake it in as its own line, not as slack hidden inside the trade's duration. When it's visible, nobody accidentally schedules over it.
- Frame-to-rough-in cleanup. A day for the framers to clean up and for the space to be ready for the MEP trades keeps you from stacking crews on top of debris.
- Cure and dry times. Mud, self-leveler, sealed concrete, painted surfaces — these don't care about your schedule. A template that pretends drywall finish is instant is a template that generates a lie every time it's used.
The point of putting these in the template is that they stop being a negotiation. A buffer you have to argue for every week gets cut every week. A buffer that's already sitting in the standard sequence has to be deliberately removed, and that friction is doing its job.
Template the Constraints, Not Just the Tasks
The Last Planner idea that makes short-interval scheduling actually work is that an activity isn't ready until its constraints are cleared — material on site, prior work complete, permit in hand, equipment available, crew assigned. The best templates carry a standard constraint checklist for each recurring activity, so nobody has to remember the list from scratch under pressure.
For a rough-in activity, a templated constraint check might read: approved shop drawings in hand, material delivered and staged, prior trade signed off, inspection scheduled, and the correct crew size confirmed. It's boring. That's the point. The failure mode this prevents is the one every superintendent has lived through — a crew shows up ready to work and can't, because a submittal wasn't approved or the material's still on a truck. A templated constraint list turns your weekly work plan from a list of hopes into a list of activities that are genuinely ready to go.
Standardize the Paper, Too
Sequence templates get the glory, but document and communication templates quietly save more hours a week. Daily log templates that prompt for weather, headcount by trade, deliveries, delays, and safety observations mean your logs are actually usable six months later when a delay claim shows up. A blank log gets a one-line entry; a prompted one gets the details you'll wish you had.
The same goes for the routine emails you send fifty times a job — submittal requests, three-week look-ahead distributions, backcharge notices. A short library of message templates keeps them complete and professional without you rewriting them at 6 a.m. And a standard coordination-meeting agenda — last week's commitments and did-we-hit-them, this week's plan, constraints that need clearing, the two-week look-ahead — keeps the weekly with your subs from wandering into a war-story session. The format is the discipline.
Where Templates Betray You
Now the honest part, because this is where copied "templates" wreck jobs. A template is a default, and a default that nobody questions is a hazard.
The classic disaster is the template built from your best job — the one where everything broke your way. Its durations are your ceiling, not your average, and when you apply it to a normal job you've quietly committed to a schedule you hit once in your career. Build durations from typical performance, and keep an aggressive version separately labeled so nobody grabs it by accident.
The second trap is site conditions the template can't see. An occupied renovation with after-hours-only work, a high-rise with one hoist and a stacking problem, a phased turnover where the owner takes floors as you finish them — these blow up a generic sequence. Templates are a starting point you adapt, never a schedule you accept as-is. The five minutes you spend asking "what's different about this job?" is the most valuable five minutes in the setup.
Third: templates rot. Codes change, your crews get faster or slower, a sub you always used goes out of business. A template last touched three years ago is teaching new PMs how the company used to build. Somebody has to own each template and refresh it, or it turns into confidently-wrong instructions.
Governance Without the Bureaucracy
You don't need a committee to manage templates, but you do need a few rules or they multiply into chaos — fifteen slightly different "office TI" templates and no way to know which one's current.
- One owner per template. A named person responsible for keeping it honest. Ownerless templates are how junk accumulates.
- Master templates are locked; copies are free. Anyone can spin up a job from a master and change their copy all day. Changing the master takes a deliberate act by the owner. That one boundary prevents a rushed edit on a Tuesday from silently changing how every future job gets built.
- Build them with the people who use them. The foreman running the work knows the real sequence and the real durations better than anyone in the trailer. A template written without field input is a wish list. Involve the crew leaders — the same ones who'll see the plan on the mobile app — and it'll actually match how the work goes in.
- Retire what nobody uses. If a template hasn't been pulled in a year, it's either wrong or forgotten. Either way, get it out of the library so the good ones are easy to find.
The Real Payoff
The reason to invest in templates isn't faster setup, though you'll get that. It's that every job becomes a chance to make the next one better. You run a hospital corridor, you learn that the ceiling above-grid coordination needs an extra day because of the medical-gas rough, and you fold that lesson back into the template. Now every hospital job after this one starts one lesson smarter. That's the compounding you're after — not reusing an old schedule, but building a sequence that gets a little truer every time you run it.
Do it the lazy way and you're just copying last year's mistakes into next year's job. Do it right and your templates become the memory of the company — the place where "we learned this the hard way" turns into "the schedule already knows." A good short-interval scheduling tool is where that memory lives and stays current; the discipline of building templates worth trusting is on you.