Articles tagged Scheduling
Earned value vs percent complete: one measures progress, the other tells you what it means
Percent complete says how much of the work is done. Earned value turns that progress into the budgeted value of the work done, so it can be compared with the plan and with what was spent. Here is how the two relate, when to use each, a worked example and the mistakes that make every job look on budget.
How to build a three-week look-ahead schedule the field will actually use
The master schedule says what has to happen. The three-week look-ahead says who does it, where, and what has to be cleared first. Here is how to pull it from the master, break it down to crew level, screen every activity for constraints, get commitments from the trades, and roll it forward each week, with a worked example.
How to calculate liquidated damages exposure and carry it in your forecast
Liquidated damages exposure is the days between your forecast finish and the adjusted contract date, times the daily rate, for each milestone that carries LDs, limited by any cap. The hard part is using honest inputs: approved extensions only, a forecast from the current schedule, pending requests and risk shown as separate scenarios. Here is the method and a worked example with two milestones.
How to create a work breakdown structure for a construction project
A work breakdown structure splits the whole scope of a job into pieces you can schedule, budget and measure. Choose the split that matches how the job will be built, decompose to work packages one party can own, check the 100% rule, write a WBS dictionary, then tie the WBS to cost codes and schedule activities. Here is the method and a worked example for a three-story office building.
How to document weather delays so a time extension holds up
Rain, wind, cold and heat stop work on every job, but a weather day only becomes extra time if you can show the weather was unusual, that it stopped critical work, and that you gave notice. Here is what to record each day, how to tally lost days against the contract's allowance, and a worked example for one month.
How to run a pull planning session: from milestone back to Monday
Pull planning has the trades plan a phase backwards from a milestone, one handoff at a time, so the sequence comes from the people doing the work. Here is how to prepare, who to invite, how to run the wall, how to turn it into a look-ahead, and a worked example for a floor of interior build-out.
How to track submittals so long-lead items arrive on time
A submittal log only helps if someone works it every week. Here is how to set submit-by dates from the schedule, what to check each week, how to handle revise-and-resubmit, and how to spot the long-lead item that is about to make the job late, with a worked register snapshot.
Review native schedule publication through the API
Use an authorized inventory, explicit decisions and a verified preview to publish supported native activities without confusing planning with field updates.
Publish a native field schedule from Planner
Choose task policies, review field changes, and preserve exact identities when removing or restoring native activities.
Review schedule changes before moving field dates
A practical workflow for checking calendars, activity matches and linked records before applying calculated dates to an adopted schedule.
Acceleration and disruption: track time recovery and production separately
Distinguish earlier completion efforts from productivity effects and organize the records needed to evaluate changed working methods.
Activity durations and logic: build a schedule the field can update
Choose useful activity detail, support durations with production assumptions and test whether dependency logic represents real construction handoffs.
AI in schedule analysis: separate helpful drafting from verified calculation
Distinguish schedule calculation, risk simulation, prediction and AI drafting, then use an evidence-based review process for generated findings.
A construction schedule audit you can actually act on
Review schedule logic, contract requirements and field evidence separately, then turn findings into specific actions with owners and due dates.
Build a baseline schedule submission the reviewer can follow
Prepare the schedule file, narrative, assumptions and transmittal as one traceable baseline package, using the actual project requirements.
Schedule calendars: why five working days can mean different finish dates
Learn how shifts, weekends, holidays and calendar changes affect a construction forecast, with a worked example and practical review checks.
Concurrent delay: establish the facts before labeling the overlap
Distinguish overlapping events from effects on completion, document independent paths and prepare the evidence needed for concurrent-delay review.
Schedule constraints: explain the date before changing the logic
Review imposed dates, understand negative float and document constraints without confusing a calculation result with responsibility for delay.
Choose a delay-analysis method by the question and the records
Compare prospective impact models, period reviews and as-built comparisons by their evidence needs, assumptions and the questions they can answer.
Extension-of-time preparation: build the evidence trail as the event develops
Organize event records, notices, schedule versions and mitigation evidence for a project-specific extension-of-time review.
GAO and DCMA schedule reviews: use metrics to investigate the plan
Understand the role of schedule-quality metrics, check their populations and thresholds, and connect results to a broader reliability review.
Lags and leads: make hidden waiting time visible
Review relationship lags, negative lag and waiting periods with clear units, calendars and ownership before relying on the construction forecast.
Write a monthly schedule narrative that explains what changed
Turn a schedule update into a clear account of progress, forecast movement, logic changes, risks and decisions with a practical narrative structure.
P6 scheduling settings: the assumptions behind the finish date
Review retained logic, progress override, criticality and lag calendars before comparing Primavera P6 schedules or explaining forecast changes.
How to read a schedule analysis report before trusting the findings
Check source identity, method, assumptions, limitations and evidence before treating a schedule-analysis finding as a project decision.
A recovery schedule needs a construction plan behind every earlier date
Evaluate recovery options with crew, access and procurement evidence, then compare forecast benefit, constraints and implementation commitments.
Build a schedule standards crosswalk without inventing one universal rule
Map schedule requirements to the correct document, edition and clause while separating contract obligations, guidance and software definitions.
Time impact analysis: build a model another reviewer can follow
Prepare a traceable time impact analysis with a documented base schedule, event fragnet, controlled calculation and clear limits on the conclusion.
Total float and free float: explain the difference at the coordination meeting
Use a simple construction network to distinguish total float from free float and understand why an activity can affect a trade before completion.
Received a P6 XER file? Preserve the source before reviewing the schedule
Create a reliable intake record for Primavera P6 XER files, check imports and distinguish original schedule data from recalculated results.
Plan with working calendars, then review the result
Plan with working calendars, review retained-source adoption, and explicitly apply calculated dates to eligible linked tasks.
A weekly schedule review checklist for the project team
Confirm the selected schedule, review the next three weeks, check calculated coverage and assign follow-up before changing field dates.