Plan
Systems, components, the work on them, the people and their AI: everything that runs a project, today.
Give every team a shared view of what matters. Plan the work, see how it connects, and turn project knowledge into better decisions, with people and AI working from the same structure.
Systems, components, the work on them, the people and their AI: everything that runs a project, today.
2D drawings, a connected work canvas and BIM, every system in view where it is.
Dashboards and data views from live project data, shared with anyone, and the learnings of every project.
Everything that runs a project, on one structure: in four parts.
Connect systems, people and project data from day one. Every requirement, test and decision adds to a shared picture that the whole team and their AI can work from.
Open any system and see the work, documents and conversations that belong to it. One connected history, from the first requirement to operation.
“Build the system list for Building B from these tender documents.”
It works in Systems with your access, and its work is marked as AI.NS 3451, TFM or your company’s own codes, from the first day.
From chapters down to single components, with what is under each in view.
Every piece of information belongs to a system, so it is always found where it should be.
Component types, TFM codes and what each type needs, kept once for the whole project and attached to the systems they serve.
“Which component types have no checklist template yet?”
It works in Components with your access, and its work is marked as AI.TFM tags follow the project’s pattern, so the labels on site, in the model and in the O&M files agree.
Requirements, checklist templates and required documents, set once per component type.
Match model objects that carry the same component codes, and keep them in step.
Buildings, floors and rooms in one tree. Place a system or a component, and its location goes with it, so everyone on site knows where to find it.
“Place every system on Plan 2 of Building B in its room, from the drawings.”
It works in Locations with your access, and its work is marked as AI.Buildings, floors, rooms and areas, nested as deep as the project needs, in the order you drag them into.
Each place shows how many systems and components sit in it, and in everything below it.
A placed system carries its location, such as +Bygg B/Plan 2, wherever it shows up.
Requirements written on the systems, components and integrations they govern, with every change shown in redline: who added what, who removed what, and when.
“What changed in the ventilation requirements since the tender?”
It works in Requirements with your access, and its work is marked as AI.On the system, component type or integration they govern, not in a separate binder.
Compare revisions, with every addition and deletion signed by person and company.
The team and their AI automatically work from the latest revision. Earlier versions stay available, with every change in context.
Progress, checklists, integrations, responsibilities, documents, punch items and scheduling, each tied to a system or a component.
Every system through your phases and MMI levels on one grid, from basic information to operation, across every company on the project.
“Which systems in Building B are still below MMI 400?”
It works in Progress with your access, and its work is marked as AI.MMI and FMI out of the box, or your own phases and levels.
Not in a status report. Update the system and everyone sees it.
By chapter, location, company or phase, top-down or one system in depth.
Checklists from templates or written with AI, each with a builder, a performer and QA, followed from draft to approved on the system it belongs to.
“Create functional test checklists for every AHU, based on the requirements.”
It works in Checklists with your access, and its work is marked as AI.Builder, performer and QA on every checklist, so nobody signs off their own work.
Protocols, photos and measurements on the item they prove.
Start from a template, or let your AI draft them from the requirements.
The interfaces between trades, alive: each integration links two systems, carries its own specification and owner, and gets tested, so nothing falls between companies.
“Read the fire strategy and create every integration it implies.”
It works in Integrations with your access, and its work is marked as AI.Write the interface once. Every change is a new revision, not a new email.
Checklists per integration, with the result on both systems.
Jump between the two systems an interface connects.
A living responsibility matrix: companies as groups, roles as codes and people on systems, carried down the tree so nothing is left unassigned.
“Set up the responsibility matrix from this contract appendix.”
It works in Responsibilities with your access, and its work is marked as AI.Access, interfaces and invitations follow the company.
Assign once on a chapter, and every system and component below inherits it.
Placeholders for people who are not invited yet.
Every document filed per system and NS 3456 category, with revisions and status codes, so the documentation is complete before anyone asks.
“Sort these O&M files into the right systems and categories.”
It works in Documents with your access, and its work is marked as AI.The matrix says what each system needs, from day one.
Know which version is current and whether it is approved.
Upload a folder and your AI files every document on its system and category.
Punch items pinned to systems and components, assigned to the responsible company, prioritised and tracked to done.
“Turn these walk-through notes into punch items.”
It works in Punch items with your access, and its work is marked as AI.Name and colour your own priority levels.
Punch items go to the company that owns the system, never to the wrong trade.
Open, in progress, completed, and overdue the moment the date passes.
Put checklists on a timeline, link what depends on what, and see what is unscheduled before it becomes late.
“Plan the fire scenario tests for week 42 in the right order.”
It works in Scheduling with your access, and its work is marked as AI.Sprinkler flow switch before fire alarm, fire alarm before AHU stop.
Every checklist is on the plan or on a backlog you can see.
This week’s tests or the whole commissioning phase.
Chat, search and the Log keep every conversation, answer and change where the whole team can find them, their AI included.
Chatrooms for the project, direct messages for quick questions, and a thread on every system, checklist, document, integration and punch item, with the history kept for whoever comes next.
“Summarise everything said about =365.001 this month.”
It works in Chat with your access, and its work is marked as AI.Rooms for the project, a trade or a week of commissioning, and anyone one click away.
Mention people and tag systems, documents or punch items. Tags become links, and links become history.
Every system, checklist and punch item has its own conversation.
One full-screen search across systems, components, documents, checklists, punch items, conversations and people. Press ⌘K anywhere and go straight there.
Systems, TFM tags, documents, checklist items, punch items, messages and people.
Narrow to one kind of result without leaving the keyboard.
Every result opens where it lives: the system, the checklist or the conversation.
Who changed what and when, on every system, whether it was a person or an AI. Open any system and read its full story.
“What changed on =562.001 in the last 30 days, and who changed it?”
It works in Log with your access, and its work is marked as AI.Every system’s history in order, from the first sketch.
Every change made by an AI is marked as AI.
The record goes with the building, not with the contract.
Project settings, exports and your own AI, so SystemTracker fits your company instead of the other way round.
Modules, steps, code standards, statuses, priorities, role codes and locations: set them up for the project, and change them mid-project without losing anything.
“Set up this project like our last hospital project, with NS 3451 and TFM.”
It works in Project settings with your access, and its work is marked as AI.Rename, add and reorder steps, with the levels inside each.
Document statuses, punch priorities and role codes, named the way your team says them.
Everything already in the project keeps its place.
Export any part of the project in the structure you built: PDF, Excel, or a ZIP that mirrors your system tree. No asking, no fees, no lock-in.
“Which systems would arrive as empty folders in the handover ZIP today?”
It works in Export with your access, and its work is marked as AI.Every export follows your system tree, so the files make sense without SystemTracker.
Systems, components, integrations, responsibilities and punch items, in Excel.
Anything missing in your data shows up in the export, from documents and checklists to responsibilities and punch items, before anyone else spots it.
Connect the AI you already use. It works in every module through MCP, with your access, and every change it makes is marked as AI.
Bring your own agents and the workflows you have built. No AI tokens to buy from us.
Bring any MCP-ready assistant or agent, and swap any time.
It sees and changes only what you may.
Everyone sees what was done by an AI, and on whose behalf.
See every system where it is: on the drawings, on the model and on one canvas the whole team works on.
Ask for the numbers you need. Dashboards and data views from live project data, shared with anyone, and the learnings of every project.
We are building organisational intelligence: find the people who make a difference, understand the patterns across projects and put shared experience to work.
Get insights from earlier projects, connected to the decisions, tests and results behind them.
Test the fire dampers against the fire alarm before the full-scale test.
Two dampers did not close on the day, and the test moved a week. On the next project the interface test ran three weeks earlier.Preserve why decisions were made and what happened next, even when people change roles or a project ends.
Why we tested the interfaces earlier.
The decision, its context and the outcome, kept together.Discover strong teams and companies, recognise the people who help others, and bring their experience into new projects.
Find patterns in delays, test failures and product issues across projects, with the context needed to understand them.
Find what successful projects have in common and share proven approaches across teams, projects and countries.
Compare tender assumptions and forecasts with actual delivery. Use the differences to improve the next estimate and plan.
Illustrative previews of upcoming features.