Skip to content

Construction and project-based

Many construction delays start in the resource plan, when crews and cranes are booked site by site. One model plans every project at once.

  • Free 30-minute call
  • No commitment
  • You own the code
Typical decisions
project and task scheduling, equipment and asset assignment
What you gain
You see crew and crane clashes before they happen on site
First step
A free 30-minute call

Typical problems in construction and project-based.

On Monday morning, the crane you booked is on another site and the formwork crew is waiting. Every idle day costs you penalties, rent and the client’s patience.

Delay has a daily cost

Each day late brings a penalty, a crew paid to wait and a crane rented for nothing. The costs add up every day.

Resources clash

Two site managers both book the crane for Tuesday. Each plan made sense alone, and neither saw the other.

Subcontractors uncoordinated

The electricians arrive before the walls are closed. They leave again, and getting them back takes two weeks.

Dependencies ignored

The roof is three days late, so the facade starts late, then the fit-out. One late task pushes everything after it.

In short: A construction resource schedule plans when each task on each site is done. It plans only as much work as your crews, cranes and equipment can handle when several sites share them. Multi-project resource levelling moves task dates so that no crew and no crane is planned twice in the same week.

Delay has a daily cost

Monday, 7 am: the formwork crew is on site. They build the moulds that the concrete is poured into. But the crane they need is on another job. They wait until noon. Every late day costs money in penalties, idle crews, rented equipment and a client losing patience. And many delays don’t start on site at all.

They start in the plan, when crews, equipment and subcontractors were booked site by site, with no view of the other sites. Each site manager plans their own project. Two of them book the same crane, and nobody notices until Monday. Fixing it once the work is already late is expensive, and the delay spreads to every task that follows.

What changes when one plan covers every site

Today, each site books crews, cranes and subcontractors on its own, and clashes surface on the day. Our model plans every project together, before work starts. When a task runs late, the plan shows what moves with it, and you reschedule the rest in one go.

Your project managers see one plan for all projects, and every crew and machine is booked only once in it. Subcontractors arrive when the work before them is done. You see which tasks a late task will delay while there’s still time to act.

Multi-project resource levelling across sites

Construction resource scheduling is a known problem with a long name: the resource-constrained project scheduling problem (RCPSP). It starts from your Gantt chart, the bar chart that shows every task on a timeline. The chart also says which tasks must finish before others can start. Then it adds the limits a Gantt chart ignores: one crane, one formwork crew, one electrician team. Multi-project resource levelling moves task dates so no week is overbooked across your sites. Resource smoothing evens out the peaks without moving the deadlines.

When the crane was on another site, does the penalty still apply?

Guides on resource levelling treat a crane clash as pure maths. But what a delay costs you depends on your contract. Many construction contracts give you more time when a delay isn’t your fault, and an agreed penalty then falls away. But you usually have to tell the site management at once and in writing, or the claim is lost. So check what your own contract says before the first delay.

A clash between your own sites usually counts as your own fault, so the penalty stands. That’s the strongest case for planning all projects in one model. For delays from outside, the model records when each task slipped and why, so the notice goes out the same day.

How a project runs.

Each of the three phases ends with something you can check before we go any further.

  1. Understand

    We start with your operation. What do you plan, where does it go wrong, and what would a better week look like? Then we tell you straight whether optimisation can help, and sometimes the answer is no.

    • A written assessment
    • A clear go or no-go
  2. Model

    We write your decisions, goals and rules into a mathematical model, which is just a precise description of how your operation works. Then we run it on your own data. You see side by side what each plan costs and what it delivers, and pick the one that fits your priorities.

    • A documented model
    • Results on your own data
  3. Implement

    We test with your data and go through the results with your team. Once they trust it, we connect the model to your systems, so it runs every day without anyone stepping in by hand.

    • Source code and documentation
    • Training for your team

Common questions.

Something else? Ask us directly.

Levelling moves the start and end dates of tasks until no resource is overbooked. A resource is a crew, a crane or a machine. The project may finish later as a result. Smoothing evens out the peaks in resource use while keeping the deadlines. Across several sites, you usually need both, and a model shows what each choice costs.

That depends on your contract. Many construction contracts grant more time for a delay you didn’t cause, and the penalty then falls away. For that, you usually have to inform the site management at once and in writing. If you don’t, you get no extra time. A model that records when and why each task slipped makes that notice quick to send.

Plan all sites in one model, with travel time between them as part of each move. The model then knows a crew can’t pour concrete in one town at eight and start formwork in another at nine. At any time, it plans each crew on one site only, across all projects. Site managers see the same plan, so no crew is booked on two sites at the same time.

It depends on the problem, so we agree the timeline with you up front. Every project starts with a diagnostic, a short look at how you plan today. It shows which data, how much time and what budget a model for daily use needs. Only then do you decide.

No. We connect to your ERP, your warehouse management system or your planning spreadsheet. We build the model only for the planning that gives you trouble today. Your systems keep running as before.

Almost nobody’s data is clean. The diagnostic shows what the model needs and what’s missing. Then we build the model to cope with messy data.

Off-the-shelf tools are built for many companies at once, so they don’t know your special rules. We build a model that follows exactly your rules. Then we hand it over, and your team owns it.

Tell us what you’re planning.

In a free 30-minute call with a specialist, you find out whether optimisation can help.

  • Free, no commitment
  • You talk to a specialist directly
  • A clear go or no-go