The superintendent started hanging drywall on level three before the above-ceiling inspection was signed off. It made sense in the field. The inspector was booked out a week, the crew was on site, and the ceiling grid could wait.
In the schedule, though, "Hang Drywall L3" now shows an actual start while its predecessor, "Above-Ceiling Inspection L3," has not started. The update goes in. Nobody flags it. Two months later the owner's rep asks why the level three finishes are stuck at 80 percent and why the critical path suddenly runs through an inspection everyone thought was done.
That is out-of-sequence work. It is one of the most common things in a construction schedule and one of the least discussed until it causes a problem.
What "out of sequence" actually means
An activity is out of sequence when it has progress, an actual start or percent complete, while the logic says it should still be waiting on something. The plan said A, then B. The field did B before A finished.
Sometimes that is fine. Crews resequence work for good reasons: access, weather, a late delivery, a sub who showed up early. The plan should bend to reality.
The problem is not that it happens. The problem is that the schedule usually does not tell anyone it happened, and the way it gets handled quietly changes what the schedule is saying.
Why it hides in the update
Out-of-sequence progress rarely announces itself. A few reasons it stays buried:
The finish date may not move. One out-of-sequence activity often has little effect on the project end date this month. If the reviewer checks the finish and the critical path and moves on, it slips through.
The scheduling setting decides the story. In P6, the choice between retained logic and progress override changes how the remaining work is calculated. With retained logic, the rest of the out-of-sequence activity waits for the predecessor to finish. With progress override, the open logic is effectively ignored. Same field facts, two different forecasts. Many people reading the update do not know which one the file uses.
It compounds quietly. One out-of-sequence activity is a note. Forty of them is a schedule whose logic no longer describes how the job is being built. By then the critical path is less a plan and more a guess.
Nobody owns the conversation. The scheduler sees the flag. The superintendent made the call. The PM is in the OAC meeting. Without a routine, out-of-sequence items fall between those three people.
What it costs when it surfaces late
Forecasts lose credibility. When the remaining logic does not match the field, the forecast finish is built on relationships nobody is following. Owners notice when dates swing for reasons the team cannot explain.
The critical path jumps. A long-open predecessor, like that inspection, can suddenly drive the end date once its successors cannot finish without it. To the owner it looks like a new problem. It is an old one that was never cleaned up.
Time requests get harder. If a delay claim or time extension comes later, a schedule full of unresolved out-of-sequence logic is easy to challenge. The record does not clearly show what was planned, what changed, and when.
Schedulers spend review time hunting. Finding these items by scrolling layouts or building Excel filters every cycle is slow, so it gets skipped when the update is due tomorrow.
A better routine, with or without tools
You do not need new software to get control of this. You need to make out-of-sequence work visible every update and give it a short, repeatable decision.
1. Pull the list every update
Every cycle, list every activity that has progress while a predecessor is still open. Include the activity, the open predecessor, the relationship type, the responsible trade, and how long it has been out of sequence. New items and carried-over items should be easy to tell apart.
2. Sort each item into one of three buckets
Most out-of-sequence items fall into one of these:
- Planned logic was wrong. The field is building it the right way and the schedule never reflected that. Fix the logic.
- Intentional resequence. The team chose a different order for a real reason. Update the logic so the plan matches the new approach, and note why.
- Statusing error. Someone entered a start or percent complete that is not real. Correct the status.
If an item does not fit any bucket, that is a conversation for the superintendent, not a note in the file.
3. Set a short time limit for cleanup
An out-of-sequence item should not survive more than one or two updates without a decision. Carrying them forward indefinitely is how forty of them pile up.
4. Know your scheduling setting and say it out loud
Agree with the owner on retained logic or progress override, and state it in the narrative. That one sentence removes a lot of confusion when dates move.
5. Put it in the narrative in plain English
"Three activities were out of sequence this period. Two reflected an intentional change to the level three finish sequence and logic was updated. One was a statusing error and has been corrected." Owners trust a schedule more when it explains itself.
Before and after
Before: The update comes in. The scheduler checks the finish date and the critical path. Out-of-sequence items show up in a P6 report nobody reads, or not at all. They pile up until the path jumps or the owner asks a question nobody can answer quickly.
After: The update comes in. Within minutes the team has a list of every out-of-sequence activity, which ones are new, and which are aging. The scheduler sorts them into three buckets, confirms the odd ones with the superintendent, and fixes logic or status the same week. The narrative explains it in two sentences. The critical path stays honest.
The scheduler still makes the calls. They just stop spending the morning finding the items before they can make them.
Where AI helps, and where it does not
This is a good fit for AI because the finding part is pattern work: compare progress against logic across thousands of activities and surface what does not line up.
Where it helps:
- Flagging out-of-sequence activities across the whole schedule every update, not just the ones someone remembers to filter for
- Answering plain-language questions like "which activities started before their predecessors finished?" or "which out-of-sequence items carried over from last month?"
- Showing out-of-sequence items next to the other quality checks reviewers already care about, like open ends and logic changes
Where people still decide:
- Whether the field's sequence is better than the plan
- Whether to change logic, correct status, or accept a deviation
- How to explain it to the owner
What to watch:
- Bad status in, bad flags out. If percent complete is guessed, the list will include noise. The fix is better statusing, not more review.
- Context lives in the field. No tool knows the inspector was booked out a week. The superintendent does.
- Settings matter. Make sure everyone reading the results knows which scheduling setting the file uses.
How we approach it
At InstinctIQ, we work as a forward-deployed team. Before we change anything, we sit with your schedulers and project teams through a real update cycle and watch where the review time goes: what gets checked, what gets skipped when the deadline is close, and which questions the owner keeps asking.
From there, IQ-Scheduling supports the review your team already runs. Upload the update and ask in plain language which activities are out of sequence, alongside checks for circular logic, redundant or reverse dependencies, and delayed or stacked tasks. Save those questions once and run them again with every new update. Results come back with WBS, dependencies, and dates, and export to Excel or Word for the narrative. When your team is short on scheduling bandwidth, Hire a Scheduler adds a vetted CPM scheduler, trained on IQ-Scheduling, who works inside the same routine.
The goal is not to take judgment away from your scheduler. It is to give them the time to use it.
A useful next step
Pull your most recent schedule update and count how many activities have progress while a predecessor is still open. Then ask how many of those were discussed with the field before the update went to the owner.
If the answer is "we did not check," we are happy to run that update with you and walk through what the out-of-sequence list looks like, one activity at a time.
Ready to see IQ-Scheduling in action?
Join hundreds of AEC teams already saving hours every week.