The site has no signal. The schedule still holds.
A field tab that keeps working with no connection, a Gantt where finish-to-start actually means finish-to-start, and an RFI register that will survive being read back to you in a dispute. Choose Engineering & Construction at setup and all three are queued.
Default project tabs
Gantt replaces List, and RAID is on — dependencies and risk are contractual here.
Projects created on day one
- Programme
- Site Works
- Design & Approvals
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
06:50 — the crew opens the Field tab in a basement
No bars, no problem. The Field tab is mobile-first and keeps working without a connection: work gets marked, notes get written, and everything lands in a per-device queue. When signal returns the queue reconciles — and where two people changed the same thing, the conflict is surfaced for a human to settle, not silently swallowed by whoever synced last.
13:20 — a prerequisite slips and the plan tells the truth
On the Hard-Dependency Gantt, finish-to-start is a rule rather than a warning. Drag a bar somewhere illegal and it refuses or warns instead of quietly letting you draw an impossible programme, and a real slip cascades to everything downstream with an audit row explaining what moved and why.
16:05 — the RFI is raised properly the first time
A numbered register per project, attachment rules so the drawing actually comes with the question, and an ordered approval chain that walks submitted → under review → answered → closed. Each RFI links to the task it is blocking, so the schedule and the paperwork say the same thing.
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working — or install any one of them on its own, later, from the marketplace.
Offline Sync Protocol
A mobile-first Field tab built for a site with no coverage. Work continues offline into a per-device queue and reconciles when the connection returns.
- A Field tab designed for a phone in a hard hat
- Works with no signal at all
- A queue held per device, not per account
- Conflicts surfaced for a human, never swallowed
Hard-Dependency Gantt
Strict finish-to-start dependencies. The Gantt refuses or warns on an illegal drag and cascades downstream moves when something genuinely slips.
- Finish-to-start enforced, not merely flagged
- Illegal drags refused or warned on
- Downstream tasks cascade automatically
- A sweep ripples real slips and writes an audit row
RFI Workflows
A numbered RFI register per project with attachment rules, an ordered approval chain and a status lifecycle you can point at in a meeting.
- Numbered register, one per project
- Attachment rules so the drawing comes with the question
- An ordered approval chain
- Submitted → under review → answered → closed, linked to tasks
How Engineering & Construction actually runs.
Each of these is a project in Noots — its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
These sit on top of the whole product.
- Site and client meetings become owned action items on the right board
- The timeline grades progress from checklist pace against the next milestone — never from a column name
- RAID risks raised in a meeting land in the project's risk log
- Budgets, goals and deployments are tabs on the project, not another tool
- Autopilot detects a dependency ripple and tells the owners of the tasks it moved
The honest edges.
- The base Gantt in every Noots plan flags a dependency conflict but never moves anyone's dates for them. Automatic cascade is what the Hard-Dependency Gantt adds.
- The Field tab syncs work in the Noots data model. It is not a drawing-management or BIM system.
- There is no Procore, Autodesk or Bluebeam integration.
Built for the way your trade actually runs.
The ones buyers ask first.
Does the Field tab really work with no connection?
How is this different from the Gantt everyone gets?
Are RFIs numbered per project or across the org?
Can we turn one of these off?
Open a workspace that already knows Engineering & Construction.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required