Durations come from the field, not the software
Primavera will accept any number you type, and the schedule will look
professional either way.
A planner who has watched the work happen writes ten days where somebody reading
a productivity table writes six. Three months later that difference is a delay
notice and an argument about money. This is why site experience matters more in
this role than fluency in the tool.
Negative float is a warning, not a display problem
It appears, somebody finds it alarming, and the quickest fix is deleting the
constraint that caused it.
That does not make the project achievable, it only removes the warning. Negative
float means the plan cannot meet a date it has been given, and the honest
responses are to change the plan or renegotiate the date. Resisting the third
option is part of becoming a planner rather than a schedule operator.
The schedule is a contract document
On an EPC project the programme is attached to the contract, reviewed monthly by
the client, and used to argue about delay and money.
Logic has to be defensible. Progress has to be recorded against a baseline nobody
quietly edited. That formality feels excessive until the first time a schedule is
scrutinised by somebody looking for a reason not to pay.
Walk the job
The planners who are respected are not the ones with the tidiest Gantt chart.
They are the ones who were on site on Tuesday, spoke to the foreman, and knew the
sequence had changed before the progress report said so. A programme built from
emails drifts away from reality within a month.