The planner occupies a unique position because every function needs a time dimension.

  • The QS needs to know when quantities will be executed and certified.
  • The Cost Controller needs to know when costs will be incurred and how long resources will remain.
  • The Contract Manager needs to demonstrate the chronology of events and impacts.
  • Supervisors need to know which work fronts must be available and what work comes next.
  • The Project Manager needs to know which decisions protect the milestones.

The schedule can become the common model that connects activities, areas, quantities, resources, costs, contractual milestones, changes, owners and evidence. However, there is a risk in presenting the planner as the owner of all information. The planner should not:

  • Approve measurements without authority.
  • Validate costs that the planner does not know.
  • Interpret the contract unilaterally.
  • Replace the supervisor in construction decisions.
  • Define the commercial strategy.
  • Modify the scope.
  • Certify payments.
  • Assume responsibilities that belong to others.

The central function is integration, coordination and consistency. The planner must ensure that the information from each discipline has visible consequences in the project's time model and that the whole team is aware of it.

Integrated information model

For integration to work, the different functions need a common structure.

Work Breakdown Structure

The WBS organises the scope. It can be structured by:

  • Phase.
  • Area.
  • Discipline.
  • System.
  • Work Package.
  • Contract.
  • Deliverable.

The schedule WBS does not have to be identical to the cost structure, but it must be possible to map it to that structure.

Cost Breakdown Structure

The CBS organises the budget and costs.

Bill of Quantities

The BOQ organises the measurable and valuable quantities.

Location Breakdown Structure

For construction, it is especially useful to organise by building, level, area, zone, front or system.

The common code

True integration appears when an activity can be related to:

  • A work package.
  • A cost code.
  • A BOQ item.
  • An area.
  • A contract.
  • An owner.
  • A change.
  • A risk.

Not all systems need to store all the information, but they must be able to exchange it. This interrelationship can be achieved by establishing a good, well-structured schedule with activity codes that allow grouping and filtering to obtain the information each person needs. The different files from each department feed a single source of truth where everything is interrelated.

Common conflicts between roles

The planner and supervisors

The supervisor may consider that the schedule does not reflect reality. The planner may consider that the supervisor improvises without respecting the sequence. Both may be partly right. The solution is to involve site teams in the logic, use areas and quantities, explain to supervisors the importance and usefulness of the schedule, and have the planner reduce the administrative burden and facilitate decision-making on site.

The planner and the Quantity Surveyor

The QS may measure by BOQ while the planner measures by activities. If there is no mapping, the percentage from each will be different. The solution is to define BOQ-activity correspondence, cut-off criteria and treatment of additional quantities.

The planner and the Cost Controller

The planner may work with a monthly calendar while cost uses accounting periods. There may be differences between execution dates, invoice dates and accrual dates. These differences must be recognised, not artificially eliminated.

The planner and the Contract Manager

The Contract Manager may seek a contractual narrative while the planner must maintain an objective technical analysis. The planner should not manipulate the schedule to favour a claim.

Risks

The model has advantages, but it also has risks.

Risk 1. Planner overload

If the planner must collect, clean, integrate and chase all information, the planner can become a bottleneck.

Solution:

  • Clear responsibilities.
  • Structured data.
  • Automation.
  • Cut-off dates.
  • Source owners.

Risk 2. Lack of authority

The planner may detect inconsistencies without being able to correct them.

Solution:

  • Support from the Project Manager.
  • Formal governance.
  • Escalation.
  • Decision register.

Risk 3. Confusion of responsibilities

The planner may end up making decisions that belong to others.

Solution:

  • Differentiate integration from approval.
  • RACI matrix.
  • Clear ownership.

Benefits of correct integration

When the planner, QS, Cost Controller, Contract Manager and supervisors work connected, the project obtains:

  • More reliable forecast.
  • Early detection of deviations.
  • Better change control.
  • Greater cost recovery.
  • Lower contractual exposure.
  • Better cash flow.
  • Greater schedule credibility.
  • Faster decisions.
  • Less duplication.
  • Better traceability.
  • Better documented claims.
  • Better coordination between field and office.

The main benefit is not producing a more attractive dashboard. It is reducing the distance between site reality and the information used to make decisions.

The schedule must stop being understood as a monthly document and start being used as the operational model that connects execution, quantities, cost and contract. When this happens, the planner stops being the person who updates dates and becomes an essential piece for decision-making.