PodBOK brings industry guidance together with real-world experience from major projects. Use it to inform your approach, and check the facts and requirements that apply to your project.
1.Build the schedule with the people who will deliver it
Ask the delivery team how the work will happen, then express that plan in the schedule. Agree the sequence, handoffs and assumptions with the people responsible for them. A detailed file can still describe a way of working that the site team has never accepted.
Try this: Take one upcoming work area through a planning session with its planner, supervisor and supplying disciplines. Ask each person to explain the sequence and what they need from the others. Resolve differences before using that sequence to judge performance.
2.Join design, procurement and construction in one sequence
Start with how the project can be built, then test it against design effort and material availability. A discipline can meet its own dates while delivering the wrong things for the next team. Make the required handoffs explicit and revisit the sequence when supply constraints change.
Try this: Choose an upcoming construction area. Put its required drawings, materials and access beside the planned work sequence, with the providing teams in the room. Agree what must arrive first and which constraint requires a different sequence.
3.Put executable work into the lookahead
A planned start needs a practical readiness check. Review whether the receiving crew can actually perform the package: drawings, materials, access, permits, predecessor work and people. Make unresolved constraints visible while there is still time to remove them.
Try this: Ask the receiving supervisor to walk through the next package before release. List anything that would stop it, name who will remove each constraint and agree when readiness will be checked again.
4.Match resource commitments to the peaks in the work
Compare resource demand and supply over time, by the trades and work areas that matter. A contractor total or an average headcount can hide a shortage during a critical work window. Use compatible coding so the resource commitment can actually be compared with the work it is meant to deliver.
Try this: Overlay the next work period's demand and committed crews using the same dates and craft categories. For each mismatch, agree whether to change mobilisation, sequencing or the forecast, then carry that decision into the schedule.
5.Measure progress in terms the field can verify
Connect schedule activities to identifiable work and agreed rules of credit. Someone should be able to explain what completed and show the underlying evidence. Keep the detailed record where it is useful and roll it up consistently to the level at which the schedule is managed.
Try this: Trace one reported activity back to its drawings, lines, quantities or other field identifiers. Ask the supervisor how its progress was earned. If the answer is an unsupported percentage, agree a repeatable evidence and rollup method before the next update.
6.Agree the reporting date before comparing performance
State the date represented by the schedule and by its supporting inputs. Mixing a current construction update with older supplier information can give a misleading picture of the same milestone. Where an input must use a different cutoff, make the difference visible and explain how it affects the interpretation.
Try this: Publish a calendar showing each input cutoff, submission date and schedule update date. Put the actual status dates on the review pack and identify any lagging inputs before discussing changes in performance.
7.Give finishing work meaningful progress credit
Examine whether the progress rules give too much credit before work is accepted. Installation, inspection, checking and final signoff all need a place in the completion picture. Set weights that fit the work and its acceptance requirements so near-complete packages do not disappear from view.
Try this: Review a package that has remained nearly complete across several updates. Identify the unfinished acceptance steps and compare their remaining credit with the effort and coordination still required. Agree a defensible rule for comparable work. Record any rule change and explain its effect on comparisons with earlier updates.
8.Show the pace the remaining date now requires
Add a forward view to the progress discussion: what work remains, how much time is available and how the required pace compares with the pace being achieved. Keep that view alongside the schedule logic and work constraints. A smooth recovery curve needs an explanation of what will change in the field.
Try this: For an important workstream, show recent achieved output and the output needed over the remaining period in consistent units. Ask what specific change would make the required pace credible, then test its effect on dependent work and the forecast.
9.Follow a delay through to the project objective
A late delivery deserves investigation, but its significance depends on what it prevents. Trace the affected handoffs through to the milestone the project needs to achieve. Keep cost, operational and other consequences visible even when the completion date is unchanged.
Try this: Take one late item from the review pack. Identify the activity waiting for it, the next dependent handoffs and the consequence for startup or another agreed objective. Use that chain to explain the priority and the response required.
10.Set the action trigger before the recovery window closes
Turn a schedule concern into a decision rule: what evidence will prompt action, who will act and which response is feasible. Test acceleration against real resources and constraints. Keep an alternative ready if the first response cannot be delivered.
Try this: Choose a live schedule risk. Write its observable trigger, action owner and response date, plus the recovery option to test. At the next review, check whether the trigger occurred and whether the promised action actually happened.
This top 10's Bookshelf
Explore the sources behind this article and related reading from our Bookshelf.
Schedule Assessment Guide: Best Practices for Project Schedules
U.S. Government Accountability Office · Referenced by PodBOK
Why it's on the shelfGAO distinguishes a schedule status date, also called its data date, from the date someone views or saves the file. The status date separates actual progress from remaining work. That distinction matters when a freshly refreshed dashboard contains an older schedule position.
Further reading
What is project controls?
Association for Project Management · Referenced by PodBOK
Why it's on the shelfAPM explains how controls brings measurement, forecasting and corrective-action analysis into project management. Its overview also recognises that project size and complexity affect who performs this work. It supports distinguishing the analytical contribution from locally assigned decision authority.
Further reading
Keep exploring
Bibliography
Explore the conversations, publications and reading behind this top 10.
Podcast conversations
-
Conversation with Ahmed Abdelfattah
Passages and links
-
A schedule needs the delivery team behind it
Ahmed Abdelfattah
Ahmed Abdelfattah challenges schedules developed separately from the site team. He describes the resulting mismatch when people execute a sequence they understand but never helped translate into the formal schedule.
-
-
Conversation with Geoff Ryan
Passages and links
-
Design, supply and construction have to meet in one sequence
Geoff Ryan
Geoff Ryan describes building the schedule around what can be obtained, how long design takes and the desired construction sequence. His path-of-construction discussion brings engineering and procurement into that conversation.
-
The receiving team needs executable work
Geoff Ryan
Ryan describes installation work packages that foremen can execute because constraints have been removed. His construction background connects the planning output to the people who receive it in the field.
-
-
Conversation with Grant Stead
Passages and links
-
Compare promised resources with when the schedule needs them
Grant Stead
Grant Stead recalls a turnaround where the resource plan and schedule could not be overlaid. Once they were aligned, flat staffing concealed shortages at peak demand and surplus people later.
-
Build progress from what the field can identify
Grant Stead
Grant Stead explains that field teams know the status of specific drawings, lines and welds. Those details can feed rules of credit for schedule activities, with more granular scheduling for a short turnaround than for a capital project.
-
-
Conversation with Jovita Stander
Passages and links
-
Make reporting cutoffs visible on a project calendar
Jovita Stander
Jovita Stander describes aligning reporting cutoffs on Green Riyadh and publishing a project calendar. A construction-team exception was known and taken into account because its information arrived from several project management consultants.
-
-
Conversation with Travis Arlitt
Passages and links
-
Leave meaningful progress credit for finishing
Travis Arlitt
Travis Arlitt describes progress getting stuck near completion and argues for keeping meaningful credit for final signoff. His concern is that early credit can leave finishing work without enough attention.
-
Compare the pace achieved with the pace the date requires
Travis Arlitt
Travis Arlitt calls the accumulation of unfinished work a bow wave: when the achieved pace is below the pace required for the planned date, remaining work compresses into the time left. He uses a progress view to make that pressure visible.
-
-
Conversation with Matt Mitchell
Passages and links
-
A late activity does not automatically mean a late project
Matt Mitchell
Matt Mitchell asks whether a delay actually changes the project objective. His example is equipment arriving late without changing startup, while still potentially creating a cost consequence.
-
-
Conversation with Tarun Gohel
Passages and links
-
Name the trigger and the person who will act
Tarun Gohel
Tarun Gohel connects mitigation triggers with named owners and action dates. In the same discussion he tests whether acceleration is feasible and considers alternatives when the first response will not work.
-
Publications and further reading
-
Schedule Assessment Guide: Best Practices for Project Schedules
U.S. Government Accountability Office · Further reading
Publication details
GAO-16-89G, December 2015
Best Practice 9, Statusing Progress, printed page 122 (PDF page 136).
-
What is project controls?
Association for Project Management · Further reading
Publication details
Public topic overview; no numbered edition stated
Core elements; Who is responsible for project controls.
This source is APM's public topic overview, separate from its longer project-controls publication.
Source context
The guest examples include both capital projects and short-duration turnarounds.
PodBOK · The Major Project Podcast
https://www.themajorprojectpodcast.com/podbok/schedule-tips · Updated 2026-11-01