Built around the people who deliver projects.

Schedules, forecasts, cost reports, progress records, risk registers and short-term plans all hold parts of the answer. So do compliance registers, models, spreadsheets and the knowledge people carry between meetings.

Yet those pieces often stay disconnected. A programme update records movement without explaining its cause. A forecast and a progress report use different periods. The same numbers are reconstructed for another meeting, while useful information reaches the person responsible too late.

Construe works in those gaps: less reconciliation and repeated handling, clearer planning and controls conversations, and more confidence in what a team is using to make a decision.

Construe is a consultancy, not a standard SaaS product that every client must fit into. The response follows the problem, whether it sits across an organisation, within a project function or in one person's recurring task.

That might mean a better controls process, a reporting integration, a planning workflow, a small application or a browser extension. It might mean making better use of an existing platform—or simplifying a process without adding any software.

Established systems have value. They also have constraints. The aim is to work with what earns its place and connect what is missing.

A status report is useful, but it is not the end of the work. A team also needs to understand what changed, why it matters and what is likely to happen next.

Good project information makes it possible to consider a response, assign responsibility and then ask whether the action had the intended effect. Sources, assumptions and uncertainty need to stay visible throughout that conversation.

The purpose is a continuing cycle of understanding, decision and reassessment—not a dashboard that looks complete while the underlying questions remain unanswered.

Analysing a P6 update need not mean replacing P6. A baseline utility can address one scheduling problem. Planning analytics can use existing Touchplan data. A planning-map workflow can be extended without building another planning platform.

The same thinking applies to connecting registers with programme information or shaping an earned-value reporting workflow around existing systems. These are examples of focused interventions, not claims about client engagements.

Use existing systems where they work. Improve the gaps between them. Build only what earns its place.

Utilities, prototypes and demonstrations are a way to test ideas, explore workflows and show what focused development can make possible. Some use synthetic data; some are deliberately limited. They are not necessarily packaged commercial products.

The useful question is: what could this look like with our information and the way our team works? The tool gallery collects candidates for that conversation. Chainage is available as an interactive preview; other hosted apps are still in development. The Learn section also contains placeholders for future explanations and simulators.

AI stays in the toolkit.

AI supports research, development, analysis, testing and prototyping behind the scenes. It may be part of a client solution when it genuinely helps. It is not the proposition: put only what is useful in front of the people doing the work.