When the Schedule Says One Thing and the Field Says Another

December 26, 2025

On a recent project our team encountered a situation that happens far more than acknowledged: a project controls professional in the PMO was frustrated because the contractor’s schedule didn’t match what they personally observed onsite. From their perspective, what they saw onsite was the ultimate “truth” therefore anything reported in the schedule was automatically “wrong.”

To us this wasn’t just a schedule issue, it was a 𝗱𝗮𝗻𝗴𝗲𝗿-𝘀𝗶𝗴𝗻: a disconnect between 𝗾𝘂𝗮𝗻𝘁𝗶𝘁𝗮𝘁𝗶𝘃𝗲 and 𝗾𝘂𝗮𝗹𝗶𝘁𝗮𝘁𝗶𝘃𝗲.

𝗤𝘂𝗮𝗻𝘁𝗶𝘁𝗮𝘁𝗶𝘃𝗲 𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗲 𝗥𝗲𝗽𝗼𝗿𝘁𝗶𝗻𝗴 is the factual history, objective “math”, and “best knowledge as of the data date”:
• What happened & how long it took
• What consumed float
• Was work on the Longest Path, critical, near‑critical
• What’s forecasted to happen next, how long will it take, in what sequence
𝗤𝘂𝗮𝗹𝗶𝘁𝗮𝘁𝗶𝘃𝗲 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝘁𝗶𝗼𝗻 is what the field shows you:
• Crew behavior & productivity
• Workarounds & interruptions
• Real‑time constraints & conditions
• It’s human, messy and incredibly valuable.

𝗪𝗵𝗮𝘁 𝗮 𝗠𝗶𝘀𝗺𝗮𝘁𝗰𝗵 𝗥𝗲𝗮𝗹𝗹𝘆 𝗠𝗲𝗮𝗻𝘀. When schedule-field don’t align it usually points to:
• Progress not updated accurately or 𝘪𝘯 𝘥𝘦𝘵𝘢𝘪𝘭
• Outdated logic & durations
• Potential gamesmanship to mask delays
• A schedule used for compliance not management

𝗗𝗶𝘀𝗰𝗿𝗲𝗽𝗮𝗻𝗰𝗶𝗲𝘀 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝘀𝗰𝗵𝗲𝗱𝘂𝗹𝗲 & 𝗳𝗶𝗲𝗹𝗱 𝗶𝘀 𝗮 𝘄𝗮𝗿𝗻𝗶𝗻𝗴. The risks emerge when a PMO:
• Dismisses field intelligence because “it’s not in the schedule”
• Ignores schedule data because “that’s not what I saw”
• Overlooks the potential for selective reporting

When these perspectives diverge PMOs lose the ability to:
• Identify risks to key dates
• Make informed decisions
• Communicate accurately
• Hold teams accountable
• Defend the project against claims / disputes

𝗪𝗵𝗮𝘁 𝗦𝗲𝗸𝗵𝗺𝗲𝘁 𝗱𝗶𝗱. We explained 𝗾𝘂𝗮𝗻𝘁𝗶𝘁𝗮𝘁𝗶𝘃𝗲 & 𝗾𝘂𝗮𝗹𝗶𝘁𝗮𝘁𝗶𝘃𝗲 𝗱𝗼𝗻’𝘁 𝗰𝗼𝗺𝗽𝗲𝘁𝗲 – 𝘁𝗵𝗲𝘆 𝗶𝗻𝗳𝗼𝗿𝗺.
• 𝘐𝘧 𝘵𝘩𝘦 𝘴𝘤𝘩𝘦𝘥𝘶𝘭𝘦 𝘥𝘰𝘦𝘴𝘯’𝘵 𝘳𝘦𝘧𝘭𝘦𝘤𝘵 𝘳𝘦𝘢𝘭𝘪𝘵𝘺 – 𝘧𝘪𝘹 𝘵𝘩𝘦 𝘴𝘤𝘩𝘦𝘥𝘶𝘭𝘦.
• 𝘐𝘧 𝘵𝘩𝘦 𝘧𝘪𝘦𝘭𝘥 𝘪𝘴 𝘥𝘦𝘷𝘪𝘢𝘵𝘪𝘯𝘨 𝘧𝘳𝘰𝘮 𝘵𝘩𝘦 𝘱𝘭𝘢𝘯, 𝘥𝘰𝘯’𝘵 𝘪𝘨𝘯𝘰𝘳𝘦 – 𝘪𝘯𝘷𝘦𝘴𝘵𝘪𝘨𝘢𝘵𝘦.

𝗧𝗵𝗲 𝗙𝗶𝘅 𝗜𝘀 𝗦𝗶𝗺𝗽𝗹𝗲 – 𝗡𝗼𝘁 𝗘𝗮𝘀𝘆:
1. 𝗧𝗮𝗹𝗸 𝘁𝗼 𝘁𝗵𝗲 𝗳𝗶𝗲𝗹𝗱 regularly using 𝗮 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗹𝗼𝗼𝗽: Field → Schedule → PMO → Field.
2. The 𝗳𝗶𝗲𝗹𝗱, 𝘀𝗰𝗵𝗲𝗱𝘂𝗹𝗲, 𝗻𝗮𝗿𝗿𝗮𝘁𝗶𝘃𝗲, and 𝗿𝗲𝗮𝗹𝗶𝘁𝘆 𝗺𝘂𝘀𝘁 𝗮𝗹𝗶𝗴𝗻.
3. 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀𝗹𝘆 𝘃𝗮𝗹𝗶𝗱𝗮𝘁𝗲 𝗹𝗼𝗴𝗶𝗰 𝗮𝗻𝗱 𝗱𝘂𝗿𝗮𝘁𝗶𝗼𝗻𝘀. Have a work plan, model the plan, work the plan.

𝗧𝗵𝗲 𝗕𝗼𝘁𝘁𝗼𝗺-𝗟𝗶𝗻𝗲. When observations from the field don’t match schedule data, the data isn’t just “wrong” it’s an opportunity to improve communication, strengthen forecasting, reduce risk, build trust, and make better decisions.

Share:

Comments

Leave the first comment