A timeline for completion of a project is a dated sequence that starts at the finish line and works backward. It lists the phases of the work, how long each one takes, which ones cannot start until another ends, and the handful of milestone dates that everyone outside the team will hold you to. If those four things are on one page and someone updates them weekly, you have a timeline. If any of them is missing, you have a wish.
Construction is the hardest place to get this right, which makes it the best place to learn it. Trades depend on each other in strict order, inspections are booked by someone else, materials arrive when they arrive, and the weather does not read the schedule. A method that holds up on a building site holds up almost anywhere.
This guide walks through building a completion timeline step by step, the specific dates in construction that slip most often, and how to keep the timeline honest once work starts. It ends with a short comparison of where the timeline can live, with prices checked on October 8, 2026.
Most timelines are drawn forward: start date, first task, next task, and wherever the last bar lands becomes the finish. That approach answers "when could this be done?" The question an owner or client is usually asking is different: "can it be done by this date, and what has to be true for that to happen?"
Working backward answers the second question. The steps are:
The output of step six is the most valuable number in the plan. It tells everyone how much room there is. A project that needed to start last Tuesday has none, and every decision after that is about buying time back.
A residential or light commercial build tends to fall into a recognizable set of phases. The names vary by region and contract, but the order is stable:
| Phase | What it covers | What it waits on |
|---|---|---|
| Pre-construction | Design, permits, contracts, procurement of long-lead items | Approvals from outside the team |
| Site work | Clearing, grading, utilities, layout | Permit in hand, weather |
| Foundation | Excavation, footings, slab or basement walls | Site work, inspection, curing |
| Structure | Framing or steel, roof, sheathing | Foundation cured and inspected |
| Dry-in | Windows, exterior doors, weather barrier, roofing | Structure complete |
| Rough-in | Plumbing, electrical, mechanical inside the walls | Dry-in, so materials stay dry |
| Inspection and insulation | Rough-in inspection, then insulation | Inspector availability |
| Interior finishes | Drywall, paint, flooring, cabinets, fixtures | Insulation signed off |
| Closeout | Final inspections, punch list, cleaning, handover | Everything above |
Notice the right-hand column. Almost every phase waits on something that the crew doing the work does not control: an inspector, a cure time, a delivery, a decision. That column is where completion dates are actually won or lost, and it is the column most timelines leave out.
The handoff points between phases deserve their own markers on the timeline. "Foundation inspection passed" and "rough-in inspection passed" are milestones in the true sense: zero-duration events that gate everything after them. Putting them on the chart as diamonds or flagged cards makes them visible in a way that a long bar never is.
Once the phases are listed, the next step is to connect them. A dependency says that one task cannot start, or cannot finish, until another reaches a certain point. Four types exist, but one does most of the work:
The detail that separates a working construction timeline from a decorative one is lag: a fixed wait between two linked items. Concrete needs time to gain strength before loads go on it. An inspection request has a lead time before the inspector arrives. A countertop is templated and then fabricated before it is installed. In each case, the next task depends on the previous one with a gap that nobody can compress by working harder. Write the lag as a separate number on the link, or as its own bar labeled as a wait. Hiding it inside the duration of the task before makes the task look slow when it is not.
With durations, dependencies, and lags in place, the critical path appears: the longest chain of linked items from start to completion. Any delay on that chain moves the completion date day for day. Items off the chain have float, meaning they can slip a little without touching the finish. Knowing which is which changes how a site lead responds to a problem. A late delivery of interior doors, which usually have float, is an inconvenience. A late delivery of roof trusses, which almost always sit on the critical path, is a schedule event that needs a call to the owner the same day.
On a small job, the critical path can be found by hand: follow the longest chain of finish-to-start links from the first item to handover. On anything larger, a tool that draws the links will show it faster.
Experienced schedulers will name the same culprits. None of them are about crews working slowly. They are almost all about waiting.
Permits and approvals. The timeline usually shows a date the permit is expected. The agency does not know about that date. Put the permit on the chart as an external dependency with a named owner who checks its status weekly.
Long-lead materials. Windows, switchgear, elevators, custom millwork, and structural steel can have lead times measured in months. The order date, not the delivery date, is the item to track. A timeline that shows "windows installed" in week fourteen but no "windows ordered" item in week two has a hole in it.
Inspections. Each one gates a phase. Booking lead times vary by jurisdiction. The schedule should show both the request date and the expected inspection date.
Owner decisions. Finish selections, change orders, and design clarifications are tasks with an owner who is not on the crew. Give each decision a due date on the timeline, set early enough that the material can still be ordered in time.
Weather. Exterior phases, concrete pours, and roofing are exposed. Many schedulers carry a block of weather days as a visible buffer at the end of the exterior work, rather than spreading invisible padding across every task.
Trade stacking. When an earlier phase runs late, the trades booked for the next phase often arrive anyway, and two crews end up in the same rooms. Productivity drops for both. A resource view that shows which crew is where each week catches this before it happens.
The full timeline is for the owner and the contract. The crew leads need something shorter. Most construction teams run a look-ahead schedule: a rolling view of the next two to six weeks, broken into specific tasks with named owners, reviewed at a weekly coordination meeting.
A simple routine keeps the look-ahead and the master timeline in sync:
Step five is the one that gets skipped. When actual dates do not flow back, the master timeline stops reflecting the job within a month, and the next owner report gets assembled from memory. The fix is not discipline so much as convenience: if updating a date is a matter of dragging a bar rather than editing a cell, a formula, and a chart, it gets done.
Keep a baseline too. The baseline is a frozen copy of the plan as agreed. Comparing it with the current timeline is how a delay is explained later: which item moved, when, and what it pushed. Without a baseline, every conversation about delay becomes an argument about memory.
There is no single right container. The table below sets out the common options for a small team. Prices were checked on the vendors' pages on October 8, 2026, and exclude tax.
| Option | What it handles well | What to watch |
|---|---|---|
| Spreadsheet with a bar chart | Free, familiar, easy to send | Dependencies are manual. One person edits at a time, copies multiply |
| Smartsheet Pro, $9 per member a month billed annually ($12 monthly) | Gantt view, dependencies, cell history | Limited to 10 members. Baselines and activity log are in Business, $19 annually or $24 monthly |
| Dedicated construction scheduling software | Critical path method, resource leveling, owner reporting | Cost, training, and usually one scheduler who owns the file |
| A shared board tool with a Gantt view | Same cards as the task board, drag to reschedule, everyone sees changes | Check whether it draws dependency links and baselines before relying on it for critical path work |
On the Smartsheet pricing page, Pro lists Gantt view, dependencies and cell history, while baselines, the activity log, and guest seats for outside users appear only from Business upward. That split is common across tools: drawing bars is cheap, while keeping the record of what changed costs more.
For a team of five that already runs its weekly work on a board, the cheapest timeline to keep current is often the one built from the same cards. Some board tools now include a Gantt board as part of the free tier, where each card's start and due dates become a bar, the scale switches between days and weeks, and a red line marks today. Anything left of that line and unfinished is late at a glance. A separate resource board, with people as rows and dates across the top, shows trade stacking as overlapping bars. Board permissions can be set so a client or owner gets view-only access, which keeps the timeline shared without exporting a copy every week. These tools generally do less than dedicated scheduling software on critical path calculation, so the choice depends on whether the project needs formal CPM reporting or just a schedule the whole team will actually open. The features page and guide show what a board-based Gantt view covers.
If the timeline is new, the first two weeks decide whether it survives. A practical sequence:
The value of the timeline shows up in that last step. A delay reported two weeks in, with a named cause and a recovery plan, is a scheduling conversation. The same delay discovered at handover is a dispute.
Pick the three dates on the current job most likely to slip, almost always a permit, a long-lead order, and an inspection, and put each on the timeline as its own item with a named owner and a weekly check. Then move the timeline somewhere the whole crew can update it by dragging a bar rather than editing a file. If the team is five people or fewer, Pinateca includes a Gantt board, resource board, and kanban board on the free plan.
Start from the required completion date and work backward through the phases, giving each a duration in working days from the people who will do the work. Add the waits, such as inspections, curing, and material lead times, as separate items. Then add a visible buffer at the end of the riskiest phases instead of padding every task.
A project timeline is the high-level view: phases, milestones, and the completion date, meant for owners and stakeholders. A construction schedule goes down to tasks, crews, dependencies, and lags. Most teams keep both, with a short look-ahead that breaks the next few weeks of the timeline into tasks.
At least weekly, at the coordination meeting, with actual start and finish dates recorded for anything that moved. Items on the critical path should be checked whenever something changes, because a delay there moves the completion date day for day.
A formal calculation is rarely necessary, but knowing the longest chain of dependent tasks still helps. On a small job it can be found by hand: follow the finish-to-start links from the first task to handover and see which chain is longest. That chain is where a delay hurts the finish date.
Phases, milestone dates such as inspections and substantial completion, the owner decisions due and their deadlines, and the current forecast against the agreed baseline. Leave task-level detail out. A view-only shared board or chart keeps the client current without sending a new file each week.
All articles in “Schedules and Gantt charts”Back to the blog