Seven things that go wrong reviewing a GC schedule by hand.

Every specialty contractor does some version of the same job when a schedule lands. Open the PDF. Find your trade. Work out what you are being asked to do, by when, and whether it is possible. Most people are good at it. The process is still broken, and it is broken in ways that have nothing to do with how carefully anyone reads.

1. Your scope is scattered, not grouped

A GC schedule is organised the way the GC runs the job: by area, by level, by phase. Your work is sprinkled through all of it. Drywall at Level 2 North sits four hundred lines away from drywall at Level 2 South, with six other trades in between. Nobody writes down a list of your activities, so you build one in your head, and the one you build on a Tuesday afternoon in October is not the one you built in August.

The practical consequence is not that you miss a line. It is that you cannot see your own work as a shape. You cannot tell whether your scope is front-loaded or back-loaded, whether it has gaps, or whether two areas that look separate are actually competing for the same crew in the same week.

2. The activity codes do not say what they mean

L2-N-DW-HNG-034 is clear to the person who built the WBS. To everyone else it is a guess. Worse, the convention changes between projects, between schedulers, and sometimes between revisions of the same schedule. Any filter you build by hand is a filter on somebody else's naming habits, and it breaks silently when the habit changes.

3. Reading a printout costs you the logic

A PDF of a Gantt chart is a picture. The predecessors and successors that decide every date on it are not in the picture. So the obvious question — what is my start actually waiting on? — cannot be answered from the document you were sent, and the answer you give instead is the one the bar chart implies, which is not the same thing.

This is where most arguments later come from. You planned around a date. The date was derived from a relationship you could not see, and the relationship changed.

4. Float gets read as slack

Total float on an activity is not spare time that belongs to you. It is spare time in the path, and whoever consumes it first gets it. Reviewing by hand, the float column reads as reassurance: ten days, fine. Two revisions later that ten days has been absorbed by a trade upstream and nobody told you, because nobody had to.

5. Durations get checked, quantities do not

The review question people ask is "is fifteen days enough for that activity?" The question that matters is "what crew size does fifteen days imply, and do I have that crew?" Those are the same question only if someone has done the arithmetic. On a hand review, almost nobody does it for every line — they do it for the three activities that look tight, which are rarely the three that turn out to be tight.

6. The review is not repeatable

The GC reissues. You now have two documents and one memory. Whatever you concluded the first time is in a notebook, an email, or nowhere. The second review is not a comparison; it is a fresh review done faster and less carefully, with the quiet assumption that anything you did not notice has not changed.

7. By the time it is done, it is late

A careful manual review of a large schedule is one to two days of a senior person's time. Most of the value of a review is in the first week after the revision lands — while there is still time to raise an RFI, push back on a sequence, or move a crew. A review that finishes on day nine is a record, not a decision.

What to do about it

None of this is solved by reading harder. It is solved by changing what you are reading: turning the document into data, pulling your scope out of it as a list, and keeping that list stable between revisions so the second pass is a comparison rather than a repeat.

That is the job GanttAI does first. Upload what the GC sent — PDF, MPP, XER or Excel — and you get a live schedule you can search and filter, with the activities in your scope identified for you. On a schedule it has never seen it finds 80–90% of your scope, and it is trainable: correct it once and by the next revision of that job it is at 99%+.

The review stops being an afternoon and starts being a question you can ask twice.