A baseline programme is not a decorative Gantt chart. It is the project's execution constitution: the agreed logic that connects sequence, resources, drawings, procurement, interfaces and milestones from mobilisation to handover. Without it, a site can remain busy while spending much of its time reacting.
On many Indian construction projects, the programme is prepared at the tender stage or just after award, printed, submitted to the client and then rarely looked at again. Site teams work from daily instructions and memory. Progress meetings discuss what happened last week rather than what was planned. When delays appear, nobody can say clearly how far behind the project is, why or what it will take to recover.
This is not a planning problem only. It is a management problem, and it starts with not treating the baseline programme as a working tool.
What a baseline programme is
A baseline programme is the approved plan against which the project is measured. It lists every significant activity, its duration, the logic linking it to other activities, and the key milestones. Once agreed by client and contractor, it is frozen as the reference point. Later updates show actual progress and revised forecasts, but the baseline remains as the original commitment.
A good baseline is built in planning software such as Primavera or Microsoft Project, with activities linked through logical relationships rather than simply drawn as bars. This logic is what makes it useful: when one activity slips, the software shows which other activities and milestones are affected.
Define activity logic before site pressure takes over
The time to think through the logic of a project is before work begins, when there is space to consider alternatives. Once the site is active, decisions tend to be driven by immediate pressure rather than the overall plan.
The baseline forces the team to answer key questions early: Which areas will be built first? What are the dependencies between civil, structural steel, MEP and finishing works? How will the monsoon affect the sequence? When must equipment foundations be ready for vendor installation? Where are the critical paths, and how much float do other activities have?
Connect milestones to drawings, procurement and workfront readiness
A programme that shows only construction activities is incomplete. Construction depends on inputs: drawings, approvals, materials and equipment. A strong baseline includes these as activities, with need-by dates linked to the construction work that depends on them.
This makes the inputs visible. If the PEB structure must be erected in March, the baseline shows that the design must be approved in December and fabrication must start in January. If the approval is late, the impact on erection is immediately clear.
Create a common reference for client, consultant and contractor
When everyone works from the same agreed programme, discussions become clearer. Client, consultant and contractor can see which milestones are coming, which inputs each party owes and where risks lie. Disagreements about delays can be discussed against an objective reference rather than competing recollections.
Without a common baseline, each party tends to keep its own view of the schedule, and these views drift apart over time.
Measure actual progress against a known plan
Progress is meaningful only when compared with a plan. Saying that a slab was cast this week tells you little. Saying that it was cast two weeks behind the baseline, and that this pushes the roof completion into the monsoon, tells you what action is needed.
Regular updates, ideally weekly on active sites, record actual progress against the baseline and forecast the remaining work. Trends in these updates show whether the project is recovering, holding steady or falling further behind.
Identify slippage early enough for recovery action
Small slippages are easy to recover if they are spotted early. A three-day delay found in the first week can be absorbed by adding a crew or resequencing. The same delay compounded over six weeks becomes a month, and recovery becomes expensive or impossible.
The baseline makes small slippages visible. Without it, they remain hidden in day-to-day activity until they surface as a missed milestone.
Separate genuine change from avoidable execution loss
Projects change. Clients add scope, designs are revised, site conditions turn out differently from expectations. These changes can legitimately affect time and cost. At the same time, some delays are caused by the contractor's own execution.
A baseline programme makes it possible to separate the two. By comparing the impact of each change against the agreed plan, the project can identify which delays are attributable to changes, and therefore may justify an extension of time, and which are execution losses that the contractor must recover. This protects both client and contractor and makes commercial discussions fairer.
What a weak baseline looks like
Many programmes submitted on Indian projects share the same weaknesses. Activities are drawn as bars without logical links, so a delay in one does not show its effect on others. Durations are copied from previous projects without considering this site's scale, location or season. Drawings, approvals and procurement are missing entirely. The monsoon is ignored, or treated as if it will not affect productivity. Activities are so broad, such as "superstructure: 120 days", that progress cannot be measured meaningfully.
A programme like this looks complete but cannot serve as a baseline. It cannot show the critical path, forecast the effect of delays or distinguish one party's responsibility from another's. Investing a little more effort at the start to build a proper, logic-linked baseline pays back many times over during the project.
Keep the baseline alive
The baseline loses value if it is not reviewed. It should be discussed in weekly site meetings and monthly reviews, linked to the three-to-six-week look-ahead plan, and used to drive decisions about resources, procurement and sequence. When major changes occur, a formally revised baseline may be needed, with the reasons documented.
Creativve's Approach
At Creativve Constructiions, we treat the baseline programme as the backbone of project control. We build it with logical links, include drawings, approvals and procurement alongside construction activities, agree it with clients and consultants, and track progress against it regularly. The baseline does not make a project run smoothly by itself, but without it, no project can be managed with clarity.