The report leaves site with you. The record stays for years.

Site inspections, drawings and project records in one Master Project File, with an AI assistant that cites its sources.

Tonight the write-up will be rebuilt from a camera roll. Tomorrow it does not have to be. One morning on a Dublin site shows how.

SiteNotePro dashboard showing the next inspection due, open findings, recent activity and compliance readiness per project
The same dashboard on a phone
Web app on phone and desktop, works offline too Built for Irish construction, project data on servers in Ireland AI that reads your project, not the open internet
08:05 start08:27 finding is a task09:10 draft reviewedDay 12 signed off
See the working example: one inspection, start to finish

About the screens in this pack. They are design prototypes of the proposed product, shown with example project data. They set the layout and behaviour we are building to. Final screens may differ in detail.

In this pack

  1. What SiteNotePro is, at a glance
  2. The problem it removes
  3. One inspection, start to finish
  4. Everything logged, in order
  5. The outcome we build for
  6. Your numbers: what the write-up time is worth
  7. Trust, data and control
  8. Roadmap and what happens next

At a glance

One tool for the people who build, inspect and sign off. The visit becomes the record.

SiteNotePro captures photos, voice notes, drawing markups, tasks, RFIs and compliance records into one chronological Master Project File. An AI Inspection Assistant reads across that record and your private knowledge base, and cites every answer. You review; you issue; AI never certifies.

One place instead of six

Camera roll, spreadsheet, WhatsApp, PDF drawings, the compliance folder and what was only in someone's head collapse into one record per project. Nothing scattered, nothing retyped.

AI that reads your project

The assistant answers from your own records and your private knowledge base, not the open internet. Every answer cites the inspection, finding or document it came from.

Built for the field

Works with no signal. Voice notes transcribed. Photos GPS-stamped. Pins dropped straight onto the drawing. Easy to do one-handed, even on a wet screen.

Reports from the record

Daily logs, issue reports, stage reports and the full project export are drafted from what was already captured on site, then reviewed by you.

The professional stays in control

AI output is a suggestion, clearly marked, never a decision. Nothing is issued, sent or certified without your review.

Irish compliance built in

BCAR stage inspections, the ancillary certificate register, planning compliance and taking-in-charge workflows, for the projects that need them.


The problem

Today the project record lives in six places, and none of them will answer for you in two years.

Tonight, somewhere in Ireland, an engineer will open a camera roll and try to remember which riser, which visit, which finding. The notes are in WhatsApp. The markup is on a printout in the van. The stage forms live in a folder only one person understands. The report will be written from memory after dinner.

That is not a process. That is risk on a loop.

Phone camera roll Spreadsheets and Word WhatsApp and email Paper and PDF drawings Ad-hoc compliance folders Memory One Master Project File Chronological, linked, exportable in full Phone camera roll Spreadsheets and Word WhatsApp and email Paper and PDF drawings Ad-hoc compliance folders Memory One Master Project File Chronological, linked, exportable
Phone camera rollHundreds of site photos with no project, location or inspection attached.
Spreadsheets and WordFindings and snag lists retyped from notes, one file per visit.
WhatsApp and emailDecisions and instructions buried in threads nobody can search later.
Paper and PDF drawingsMarkups on a printout, or on a PDF that never makes it back to the file.
Ad-hoc compliance foldersCertificates, forms and notices in a folder structure only one person understands.
MemoryWhat was noticed on site but never written down, reconstructed at the desk that evening.

What that costs

  • There is no single, traceable record of what was seen, when, and by whom.
  • Every report is written from scratch, usually in the evening, from memory and a camera roll.
  • Follow-ups slip because the finding, the task and the contractor live in different tools.
  • For regulated projects, cross-form inconsistency between inspection plan, stage records and certificates is the most common reason a submission is bounced.
  • When a dispute lands two years later, the record has to be reconstructed.

Inspections happen on live sites with no signal, on shared phones, one-handed on a wet screen. Any tool that forgets that gets abandoned by week two.


One inspection, start to finish

A first-fix fire-stopping inspection, as it actually happens.

One morning on a house extension in Dublin 4. Every screen is the proposed product. Nothing here is typed up at the desk afterwards, and that is the point.

On site · 08:05 to 09:10

08:05Capture
Master Project File entry reading Inspection started, first fix, fire stopping, at 08:05 by Aoife Byrne, tagged INS-015

The inspection opens the record.

One tap starts it. From here, everything captured lands in this project, this inspection, with the engineer's name on it.

08:22Mark up
Plan viewer with a floor plan, numbered pins for a defect, a progress photo set and a snag, and a side panel listing the pins on the sheet

Four photos of the riser penetrations, pinned to the drawing.

No signal in the riser. The photos are taken anyway, stamped with time and location, and dropped as Pin 1 on Plan A-101, Rev C. They upload when coverage returns.

Pins on this sheet panel listing a defect, a progress photo set, a snag and a photo pin, with the selected pin's finding card

Every pin has a type and a status.

Tap one and its finding, photos and task open beside the plan. A pin on Rev C is never confused with Rev B.

08:24Capture
Four consecutive Master Project File entries: photos added and pinned to plan A-101, a transcribed voice note, a finding raised with moderate severity, and a task created for the contractor

Three minutes, three linked entries.

Hands full on the scaffold, so it is said out loud, not typed. By 08:27 the observation is a finding and the finding is somebody's job.

  1. 08:24
    Voice note, 42 seconds, transcribed.“The collar isn't seated square.” In the record before the boards go on.
  2. 08:26
    Finding #14 raised, Moderate.Linked to the same pin and the same inspection, with the photos as evidence.
  3. 08:27
    Task to the contractor.Re-seat the fire collar, riser 2. Owner and due date attached.
08:30Capture
Open photo card showing taken by, location, linked finding and note fields

Every photo knows who, where and why.

A photo without a project, a location and a reason does not exist here. The camera-roll problem goes away because the camera roll is never the record.

08:34Capture
Photo record screen with All, Defect, Progress and Snag filters, six photos tagged Defect, Progress, Uploading and Snag, and an open photo card showing taken by, location, linked finding and note

Some photos are there to prove the work was right.

The slab pour and the scaffold strike-down are filed as Progress, with the same time, location and inspector stamps as a defect photo. When someone asks later whether the pour was seen before it was covered, the record shows it was.

08:40Ask
AI inspection assistant answering which projects have overdue fire-stopping findings, drafting a follow-up note, and answering what the guidance requires at a riser penetration from Technical Guidance Document B and the firm's own specification, each answer citing its sources

“Which fire-stopping findings are overdue?”

The assistant reads this project's records and the firm's own knowledge base, the uploaded specifications and the Irish regulation packs. Every answer carries the source chip it came from. Ask what the guidance requires where the riser services pass through the compartment wall and it answers from Technical Guidance Document B and the firm's own fire-stopping specification, citing both. It drafts the follow-up note; it never sends it.

Knowledge base access screen for one project: standard packs with on and off switches for the Technical Guidance Documents, the BCAR Code of Practice, Uisce Éireann codes of practice and Eurocode summaries, then the organisation's own sources: a fire-stopping specification, an inspection checklist, past reports and planning conditions, with a button to add a source

What you let it read.

The standard packs come switched on: the Building Regulations Technical Guidance Documents, the BCAR Code of Practice and the Uisce Éireann codes of practice. Your own specifications, checklists, past reports and planning conditions sit underneath, private to your organisation, and each one can be switched on or off for a project.

09:10Report
Build a report card with a weekly progress template, selected sources, and an AI-drafted preview carrying source chips above a Generate report button

Pick the template, pick the sources, read the draft.

The draft cites only records inside the sources chosen, and it is reviewed and edited before it becomes a watermarked PDF. Nothing is written from memory, because nothing has to be.

The report is finished before you leave site.

The days after

Day 3Follow up
Done column on the task board with the card Photograph closed damp course seal, tagged INS-021, Finding number 1

The contractor, or you, closes it when the work is done, and photographs the fix.

The finding stays open until the work is done and the evidence is attached. The close-out photo lands in the same record, under the same pin.

Day 12Record
BCAR stage table showing Commencement, Foundations and Superstructure signed off with certifier initials and dates, First fix in progress with one finding open, and Completion not started

The stage is signed, with nothing open behind it.

A stage cannot be signed off while it has an open finding. When the last one closes, the inspection plan, the stage record and the certificates already agree with each other.


Everything logged, in order

What one morning adds up to, and what still stands in a dispute.

Every entry carries who, when, where on the drawing, and links to the entries around it. The report is one way of presenting that chain. The chain is the product: the same morning as the Dublin 4 walkthrough, still standing when someone asks years later.

Master Project File timeline listing an inspection start, photos queued to sync, a transcribed voice note, a finding raised and a task created, in time order

One chronological Master Project File, filterable by type.

Inspections, photos, voice notes, findings, tasks, markups and reports in one timeline. This is the record that survives a dispute, and it exports in full at any time.

LocationDateDrawing revisionObservationPhotographIssueNotificationCorrective actionRe-inspectionClose-out

Entry types

EntryWhat it carriesExample from the record
InspectionType, stage, date, inspector, siteINS-015 · First fix, fire stopping · Aoife Byrne
PhotoTime, GPS, who, type (defect, progress, snag), pin on the drawing, linked findingRiser 2 penetrations · Plan A-101 · Pin 1
Voice noteAudio and transcript, timestamped, attributed“Seal at the second penetration looks reinstated but the collar isn't seated square” · 0:42
Site diary noteTyped text, attributed, timestampedRoof truss delivery confirmed; crane slot 07:30 to 10:00
FindingSeverity, status lifecycle, linked photos and pinFinding #14 · collar not seated square · Moderate
TaskOwner, due date, contractor, linked findingRe-seat fire collar, riser 2 · BuildRight Ltd · overdue 16 Jun
RFIQuestion to the design team, linked location, statusRFI-009 · damp-proof course detail · waiting
Drawing markupPin or cloud on a named revision, attributedA-101 Rev C · revised riser route clouded
Stage sign-offCertifier, date, ancillary certificate PDFFoundations · signed A. Byrne CEng · 28 Apr 2026
ReportTemplate, sources cited, watermarked PDFWeekly progress · week 6 · ready
DocumentSpecifications, standards, planning conditions, past reportsSearched by the assistant, cited in its answers

Reports the record produces

Stage reportPreliminary Inspection Report

Initial findings following the first site visit.

InvestigationSite Investigation Report

Site conditions, materials and test results.

Issue reportIssue-Specific Report

One defect, finding or compliance item.

Daily logDaily Inspection Report

Attendance, observations and actions noted.

BCAR supportBCAR-Support Inspection Log

Structured stage inspection record.

Full exportMaster Project File Export

The complete chronological record.

Status chips: Saving, Uploading 3 photos, Queued to sync, Sync complete, Sync failed with retry, and an offline banner

What offline actually looks like.

Capture never waits for signal. Each photo and note shows its own state: saving, queued, synced, or failed with a retry. Offline, the phone shows the last known record and says so. A failed upload is never silent.

Knowledge base with regulation packs including Technical Guidance Documents and the BCAR Code of Practice, and a cited answer to a question about stage inspections

What the assistant reads.

Your planning conditions, specifications, standards and past reports, uploaded once, plus the Irish regulation packs. Never shared with other organisations, never used to train models.

On the phone

The same record, in a pocket, in the rain.

Every screen is designed at phone width first. Capture, pins and tasks work offline; the assistant needs signal. Tap any screen to open it in a phone and scroll through it.

Phone dashboard
DashboardNext inspection and what is overdue
Phone Master Project File timeline with a photo set queued to sync
Project recordPhotos queue and sync when coverage returns
Phone plan viewer with pins on a floor plan
Plan viewerPinch, pin, attach the photo
Phone task list
TasksAssign and close out from site
Phone AI assistant with cited answers
AssistantCited answers, suggestions only

The outcome we build for

Never be the engineer who has to say "I think…" when the client asks what happened.

Off site with the report issued. A file that answers "what happened here?" with "our records show", for as long as your name is on the job. When the builder is gone, the record is what is left.

The contractor and PM"Report was in before they were off site. No arguing about what was said, it's all there with the photo."
The Assigned Certifier"Everything I needed to sign, in order, photo pinned to the location."
Building Control"They sent a complete, well-organised file, not a scattered one with half the information missing."
The client"Quick, precise, organised. Follow-ups and sign-offs without a fight."

The standard the product is built to, in the words we want said about you. Not customer quotes yet.

Five Founding Firm places, with applications opening in early 2027. Full detail in the roadmap. First, check the numbers.


Your numbers

What the write-up time is worth.

Seven in ten Irish practices we surveyed spend two hours or more a week each on inspection write-up; four in ten spend five or more. Put your hours and rate in and see what those evenings cost, or what they would bill. The results are per engineer: multiply by the number of people who go to site.

Your practice

Are you turning work away, or is the write-up happening in the evenings?

Per engineerRateA monthA year
Hours on write-up2 h a week892
What those hours cost you€36.07 an hour€277€3,319
What those hours would bill€80 an hour€613€7,360

Enter your figures on the left to see the sentence for your practice.

An hour worked is one of 1,840 a year; the payslip pays for 2,080, so the loaded hour is about 1.50 times the payslip.

Where the numbers come from
  • Employer PRSI 11.25%. The Class A employer rate since 1 October 2025, rising to 11.4% on 1 October 2026. Source: Department of Social Protection, PRSI contribution rates (SW14, 2026).
  • Pension 1.5%. The employer contribution under automatic enrolment (My Future Fund) from 1 January 2026, for the scheme's first three years, on earnings up to €80,000. It rises to 3% in year four. A firm with its own scheme pays more.
  • Working year, 1,840 hours. A 40-hour week, paid for 52 weeks, on site for 46 after 20 days' statutory annual leave (Organisation of Working Time Act 1997) and 10 public holidays.
  • Kit and overhead €10,000. Our working estimate for one site engineer. Editable; put in your own figure.
  • Two hours a week. The floor from the SiteNotePro survey of Irish practices, 2026: seven in ten spend two hours or more a week each on inspection write-up, four in ten five or more.
  • Charge-out €80. An example. Use your own rate.
  • Not counted. Sick pay (five days a year at 70% of pay, capped at €110 a day), employer's and public liability insurance, health insurance or income protection, Safe Pass and site training, recruitment. Put any of these into the overhead figure if your practice pays them. Non-billable time is the one that matters most: an engineer is paid for 1,840 hours but bills far fewer, so the real cost of a billed hour is higher than the figure above, and that is why a charge-out rate has to be two to three times the loaded cost.
  • Not counted: reconstructing a record when a dispute or a liquidation lands. Director time, broker, solicitor, PI notification and excess. That one has no formula.
  • Put these figures against the rate we quote for your team. Founding Firms get a rate locked for life.

Trust, data and control

Control first. Then speed.

Built for professional use: you decide what issues. AI suggests and cites. The record cannot quietly change. Your data exports in full.

Role-based access

Control who can view, edit and issue on each project. Engineers, inspectors, contractors and clients get the access their role needs and no more.

Full audit trail

Every capture, edit, markup, task change and report issue is logged with a timestamp and a user. The record cannot quietly change.

Built for GDPR

Project records, photos and voice notes are stored on EU servers in Ireland, and voice transcription runs on an EU endpoint. Only email passes through a US provider, under a data processing agreement. Never used to train AI. Built to meet GDPR and the Irish Data Protection Act.

Private by design

Your documents and records are never shared with other customers and never used to train models. Each organisation's data is isolated.

AI you can see

Every AI output is marked as AI-assisted and cites its source. The assistant only answers about your projects and building regulations, and it cannot send, post or certify anything.

Your data, exportable

The full Master Project File exports at any time as a complete chronological record. No lock-in on the thing that matters most.


Roadmap

Proven on real inspections before anyone is invoiced.

Built by a chartered civil engineer who has lived Irish consultancy and site reality, and designed around how inspections actually happen.

NowBuilding and testing

Capture, projects, inspections, findings, offline sync and the plan viewer are built. Next is the real-site offline test.

NextLive on the founder's own projects

SiteNotePro runs on real inspections before any firm is invoiced.

Early 2027The shortlist sees it on their kind of work

From late February 2027, the Founding Firm shortlist sees it working on projects like theirs, and confirms a place only if it works for both sides.

Mid 2027Opens to everyone

After the founding cohort has been onboarded. The date follows the beta, so treat it as a target.


Next steps

Three doors. Start with the fastest.

Score your current records

Twelve questions, four bands, a tailored pack. The quickest way to see where the time is going today.

Take the scorecard at sitenotepro.ie/scorecard

Register founding interest

Five Founding Firms only. Applications open 18 January 2027. Register at sitenotepro.ie/founding.

See the Founding Firms offer

Ask a question or arrange a call

If you want to talk through how this would work on your projects, or the pack leaves a question open, email us and we will arrange a call.

Email info@sitenotepro.ie

Waiting list. Nothing to book yet. Join the waiting list and we will contact you the moment the prototype is ready to show.