Henri Ahoste, our Head of Product, and Jussi Engblom, our Lead Data Scientist, have both spent years working closely with construction projects, seeing how work is actually planned and run on site.
They’ve seen the same pattern repeat: There is always a schedule. Often detailed, carefully built, and agreed on. It might live in Excel or in a long Gantt chart. A lot of effort goes into it.
And still, when the day starts, people don’t really use it to guide their work.
At Sitedrive, this is where the thinking started. Questioning whether the way construction is planned and managed today truly supports the people doing the work.
That question gradually led to something broader. A different way to think about schedules, production, and how a site is run.
Today, that thinking is known as Flow-Based Production.
Henri has experienced this firsthand.
While working on construction projects, Henri wasn’t building traditional Gantt schedules himself. He had already moved towards location-based planning.
But through the customers and projects around him, he kept seeing the same pattern repeat: Detailed schedules existed. Often long, complex, and built using critical path logic.
And still, they didn’t guide daily work on site.
“If it’s detailed enough to manage with, no one understands it. If it’s simplified, you can’t really run the project with it.”
That tension shows up in everyday work.
The schedule exists, but people don’t rely on it when making decisions. Coordination happens through conversations, not through the plan. The schedule becomes something maintained rather than something that helps run the work.
And that’s where the role of the schedule starts to break down.
Henri has seen firsthand the same pattern repeat itself in construction projects: detailed schedules existed. Often long, complex, and built using critical path logic. “If it’s detailed enough to manage with, no one understands it. If it’s simplified, you can’t really run the project with it.”
Jussi often brings the conversation back to something very simple.
“In the end, we’re dealing with two things. Time and location.”
Everything that happens on a construction site happens somewhere, at a specific moment.
But most schedules don’t reflect that in a way that matches how people think and operate.
Instead of long lists of tasks, Flow-Based Production looks at how work moves through a building. Work is grouped into phases, and those phases progress from one location to another.
Henri describes it from the perspective of someone on site.
“If I’m a worker, I don’t think in task lists. I think: on Monday I’m here, doing this.”
When the schedule reflects that logic, it becomes easier to understand. You can see what is happening, where it is happening, and what comes next without needing to translate it.
This way of thinking builds on existing approaches in construction. It brings together logical dependencies, flow, and location-based planning into a practical solution.
And when the structure is right, something else becomes possible.
Henri describes it through a very concrete example.
“We can say that in this specific apartment, in this bathroom, tiling happens at this time, by this person.”
That level of detail alone doesn’t create clarity.
Clarity comes from how that data is structured and shown: in a visual, easy-to-read, location-based schedule.
The detail allows teams to connect planning with actual execution, compare projects, and eventually integrate other data, such as supply chains or resource planning, into the same structure.
In Flow-Based Production, detailed data exists within that clear structure. And that’s what makes it usable in everyday work: Teams can immediately see what is happening, where it is happening, and what comes next.
And over time, it opens the door to automating parts of the planning process.
“And later, you can start automating parts of it,” Jussi adds.
One thing both Henri and Jussi emphasize is that construction doesn’t follow a single structure.
Different phases behave differently. Groundwork has its own logic. Interior phases follow one another. Some situations require more precision, others less.
“You can’t force everything into the same structure,” Henri says.
That’s why Flow-Based Production is not a rigid framework.
Teams can still use familiar ways of planning. They can move step by step, increasing the level of detail when it makes sense. Different approaches can exist within the same project.
The method adapts to the project, not the other way around.
This way of thinking also shapes how the team works at Sitedrive.
There is no single “correct” way to approach these problems. People like Henri and Jussi spend their time figuring out how construction logic, data, and product development come together to improve daily on-site work.
They work with real constraints, real projects, and real complexity. They test ideas, learn from what works, and keep refining.
At the same time, Sitedrive is expanding into new markets, working with customers in different countries, and seeing the same core challenge recur.
The plan exists.
But it doesn’t guide the work.
For people who have seen this up close and feel that something could work better, this is a problem worth solving.
And for those who want to be part of building that change, this is where it’s happening.