The daily log, the toolbox talk, and the RFI nobody answered.
The day gets written up at half past six in the evening from memory, the toolbox talk is a signature on a sheet in the cabin, and the ticket that lapsed on Friday was on a spreadsheet nobody opened. The Jobsite tab puts all three on the phone already in the crew's hand: a daily log built to take under two minutes, with weather, crew, deliveries, plant, delays and photos; a talk each attendee signs under their own name; and expiry warnings on the ladder your insurer asked for rather than one we chose. It keeps accepting the log in a basement with no bars. Choose Engineering & Construction at setup and the Jobsite tab, the offline field queue, the RFI register and the Gantt are queued for you.
11 apps queued at setup - untick any of them before you finishDefault project tabs
Gantt replaces Timeline - here a slipped prerequisite is contractual, not cosmetic - and RAID carries the risk register the client reads at the monthly review.
Projects created on day one
- Programme
- Site Works
- Design & Approvals
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.
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.
Jobsite
One tab for the site itself: where it is and how to get on, the rules and hours, the crew and their roles, the drawings and method statements, and the site's own updates feed - with the daily log, the toolbox talks and the certifications under it.
- A daily log built for under two minutes, with photos
- Toolbox talks each attendee signs under their own name
- Certification warnings on a ladder your firm sets
- Safety observations photographed, dated and owned by somebody
RFI Workflows
A numbered register per project that leads with age and ball-in-court, with attachment rules so the drawing comes with the question and an ordered approval chain behind it.
- Numbered register, one per project
- Days outstanding and who owes the answer, on every row
- Filter and sort by status, age or owner
- Submitted → under review → answered → closed, linked to the task it blocks
Offline Sync Protocol
A mobile-first Field tab built for a basement, a lift shaft or a site with one bar. 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
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:40 - the log is written on site, not from memory that evening
The daily log opens on the five fields that matter and pre-fills yesterday's crew, hours and plant, because those usually did not change. Weather, deliveries, work performed, adverse conditions, delays: all optional, none retyped. A delay is more than a sentence here - the work front, when the obstruction started and finished, and its status each day - and an area handover records which party held which part of the site and from when. Photographs carry the date they were taken and their coordinates where the phone supplied them. It keeps accepting entries with no signal, queued on the device, and reconciles when the bars come back.
09:10 - the talk is signed, and two tickets are close to lapsing
A toolbox talk records who gave it and who was there, and each attendee signs it themselves: the signature is the person's own session rather than a name somebody typed for them, so twenty boxes ticked by the presenter say so. Beside it the Certifications register warns before a card lapses, on a ladder your firm sets - thirty days, then fourteen, then seven by default, and up to six numbers of your own instead. It flags somebody on work their tickets do not cover, and says which of three reasons applies: missing, expired, or an evaluation that belongs to the employer who made it and does not travel.
14:50 - the RFI is in its ninth day, and the register says whose it is
The RFI register sorts by age and shows ball-in-court: how many days each one has been outstanding and who owes the answer, filtered by status, age or owner, with the old ones surfaced before they are an argument. Each RFI links to the task it is blocking, so the schedule and the paperwork say the same thing. When the answer finally moves a date, drag the bar on the Timeline and it re-sorts as you let go, highlighted so you can see what you moved, with undo and redo beside it. On the Hard-Dependency Gantt a real slip cascades downstream with an audit row and a notice to whoever's dates just changed.
These sit on top of the whole product.
- The Jobsite tab is the site itself: the pin and the address with a link that opens it in whichever maps app is on the phone, the rules, hours and access notes, who is on site and in what role, and the drawings, method statements and permits filed against it
- Site updates is the project's own channel rather than a second message store, so what happened here reads newest first, notifies the people on it and is searchable with everything else
- The Hard-Dependency Gantt enforces finish-to-start instead of flagging it: an illegal drag is refused or warned on, and a genuine slip cascades downstream with an audit row and a notice to the owners of the dates it moved
- Hands-On Scheduling puts the editing on the timeline and the calendar themselves: drag a bar to a new date or drag either end to change its start or its finish, sweep across empty days on the calendar to create an event already dated, snap to whole days, and optionally carry dependent work along with the drag. Adding, renaming, re-dating and dragging a milestone works on both surfaces in every plan, extension or not
- Approvals is the submittal and change-order queue: the paperwork routes to a named signature and the record of who approved what, and when, sits on the task
- Checklists & SOPs hold the punch list at handover and the safety walk before it - written once, run per site, every step ticked with the name of the person who ticked it
- RAID is a tab on every project: the risk register the client reads at the monthly review, with assumptions, issues, changes and stakeholders beside it, and a risk raised in a meeting lands there
- The Vendor & Client Register holds every subcontractor and supplier with a main contact, a status and a renewal date; the Policy Library holds the site rules and method statements with an effective date
- The Corkboard is the wall for a design review or a risk walk - notes you drag, a pen, a thread on any note - before any of it is a RAID row
- Site walks, design reviews, progress meetings and safety briefings each get their own steer on the recorder, and the actions they produce land on the right board with an owner and a real start and due date taken from what was said
The honest edges.
- The location card shows the address, the coordinates and a link that opens the place in your own maps app. A drawn map is off until somebody turns it on, and the OpenStreetMap option says in the setting itself that it sends the site's position to openstreetmap.org on every render.
- The weather on a daily log is typed by whoever writes it. Noots reads no forecast service and fills nothing in from one.
- A toolbox talk is a dated record of who signed it inside Noots. Nothing is filed for you, no form is produced for a regulator, and no interval is imposed - how often you hold one is between you, your insurer and your client.
- Certification warnings run on the ladder you set and on the dates somebody entered. Noots does not check a card against the body that issued it, and the work a ticket has to cover is a label on the task rather than a field of its own.
- The Field tab and the offline daily log sync work in the Noots data model. This is not a drawing-management or BIM system, there is no drawing register with revisions, and there is no Procore, Autodesk or Bluebeam integration.
- There is no permit-to-work cycle. A permit is a document filed on the site, not an issue-and-return workflow with signatures at each end.
- 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.
Built for the way your trade actually runs.
The ones buyers ask first.
Is there a real daily site diary?
Does it work with no signal?
How do the certification warnings actually work?
Do we get a map of the site?
Are RFIs numbered per project or across the org?
Where do submittals and change orders go?
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