Navigation

Explore Stratal

Infrastructure delivery. Under control.

Request a demonstration

About Stratal

A clearer operating picture. From field to boardroom.

Stratal is built around the people responsible for delivering infrastructure: the planners, supervisors, field teams and commercial leaders who need the same work to make sense from different perspectives.

See it in a Stratal demonstration →

Our purpose

Bring the whole operation into view.

Infrastructure delivery depends on thousands of connected decisions. A resource allocation affects mobilisation. A permit affects the start of work. A site record affects assurance, valuation and the information a client receives. When those decisions sit in separate systems, the organisation spends time reconstructing the story.

Stratal’s purpose is to make that story easier to follow. We bring the operational disciplines of telecoms, utilities, civil engineering and fibre infrastructure into one working environment, connecting programme demand with the work on site and the controls needed to close it out.

The aim is practical: give teams a shared context for the job, a clearer view of responsibility and a reliable basis for their next decision.

Our approach

Four principles behind the platform.

01

Operational clarity

A programme should be understandable at every level. We organise the working picture around jobs, responsibilities and the decisions that move delivery forward. People need to see what is ready, what is blocked and what requires their attention.

02

Accountability in context

Evidence is more useful when it belongs to the work. Controlled records, permissions and review steps help organisations understand the basis of a decision and the responsibility behind it. Oversight remains with the people authorised to act.

03

Connected disciplines

Planning, workforce, network, assurance and commercial teams share an operational dependency. Stratal brings those disciplines into a common environment so that the delivery record can support the conversations and controls that follow.

04

Practical adoption

The platform needs to fit the working day. A browser workspace, dedicated Windows companion and field PWA support different roles and devices, with available workflows determined by the organisation’s deployment and access model.

An operating environment

The job connects the business.

A work order is more than a task on a list. It can connect a programme, planner, gang, worker, vehicle, plant, network asset, permit and work pack. As delivery progresses, that context supports field evidence, defects, completion review, valuation and client reporting.

Stratal is structured around those relationships. Operational teams can work with the detail relevant to their responsibilities, while supervisors and managers review the wider delivery picture. Controlled client access supports external visibility within the agreed programme and job scope.

The Portal, Enterprise Desktop and PWA are different ways of working within that environment. The choice of device should support the task, while permissions and organisational controls remain central to the deployment.

Explore the platform →

Working with Stratal

Start with the operation you need to run.

A meaningful platform conversation begins with your delivery model. We use the demonstration and scoping discussion to understand the programmes you manage, the people involved, the controls you need and the systems that already support the business.

Deployment planning then considers the relevant modules, user roles, field workflows, client access, identity requirements and configured integrations. Hosting, support responsibilities and the approach to rollout should be clear before implementation begins.

Enterprise requirements vary. Licensing and deployment scope reflect the organisation’s modules, users and operational needs. A focused discussion gives both sides a better basis for assessing fit than a generic package comparison.

Read about deployment →

Looking ahead

Keep decisions grounded in delivery.

As programmes evolve, so does the information teams need to manage them. Our product direction centres on stronger connections between operational records, clearer intervention queues and more useful visibility across the delivery lifecycle.

Intelligence should help people identify what deserves review. It should remain connected to the underlying work and the human decisions that follow. That principle guides how Stratal presents operational signals, assurance and commercial exceptions.

If your organisation is looking for a more connected way to run infrastructure delivery, we welcome a conversation about the work you do and the outcomes you need.

Talk to Stratal →

From first allocation to final account

Run the operation
from one place.