LIGHTNING
FOR BUILDING AND CONSTRUCTION FIRMS

The job is moving. Keep the office up to date.

Give customers a clearer view of your work and your team a better way to manage it. Websites, site forms, job records and connections to accounts can bring photos, approvals and costs into the right place without another round of typing.

Where the day gets lost between the gate and the office

01

Variations agreed at the gate, argued over at month end

A verbal instruction at the gate, a photo in a group chat, a note on the back of a drawing. No CVI raised, nothing priced, nothing signed. By the time the application for payment goes in, someone is reconstructing the extra work from a thread and hoping the client remembers it the same way.

02

RAMS, CDM and certificates in five different places

The pre-construction information sits in an inbox. The method statement is on one laptop. The current revision of the RAMS is pinned up in the cabin and nowhere else. When the principal contractor asks for your part of the health and safety file, someone stops what they are doing and rebuilds it by hand out of O&M information, test certificates and as-builts that already exist somewhere.

03

Valuations rebuilt from a blank spreadsheet every month

Last month's workbook gets copied, measures re-keyed off the drawings and the schedule of works, retentions and CIS worked out again by hand. One broken formula and the application goes in light. Nobody can see what changed between valuation four and valuation five without opening both and comparing them line by line.

04

Subcontractor scheduling that lives on one phone

Groundworks confirmed on a call, the roofer moved by text, plant booked against a delivery date nobody wrote down. It holds together while the person carrying it is at their desk. The week they are away, the office is guessing who is where and what has been promised to whom.

A site manager in a hi-vis vest and hard hat standing on a partly built structure, checking a phone, with scaffolding, stacked blocks and a telehandler behind him.

Work that starts on site and ends up in the office system

01

Site capture that lands before the van does

One form on a phone: labour and plant on site, weather and delays, photos and a variation raised against a job number and a cost code. It saves with no signal and syncs when there is some. The contracts manager and the QS read the same record, with the name and the time attached.

Custom software and reporting
02

One store for the RAMS, certificates and O&M packs

We move method statements, pre-construction information, test certificates and handover packs off personal drives and the old server into one structure per project, revisions kept and the issued version marked. We build the place these documents live and set up who can reach what. We do not write them or assess them.

Integration and migration
03

The chasing nobody in the office has time for

Subcontractor insurance and CSCS card expiry dates tracked, with the flag raised before the date passes rather than when someone is turned away at the gate. Timesheets and delivery tickets read and matched to the right job. Valuation packs drawn together from what site already recorded. The office moves from re-keying to checking, and anything that needs a person to sign it off still goes to a person.

AI and automation
04

A site that stands up to being checked before a tender

Your site is the first thing a main contractor, framework manager or private client can check before they decide who gets invited to price. We build one that shows the schemes you have completed, the sectors you work in, the accreditations you already hold and how to reach the person who answers, instead of a photo gallery shot four phones ago.

Websites and digital platforms
05

The week's confirmations somewhere other than one phone

Groundworks, roofers, plant and deliveries confirmed into one week view the office can read: who is booked, for which job and what was promised on the call. Confirmations go back out by text or email from the same place, with the date and the job number on them. When the person who arranged the week is on site, on a roof or away, someone else can still read what was agreed.

Phone, email and CRM
A site manager reading drawings on a construction site

We start on a live project not in a software demo

We ask to see one live project before we propose anything: the folder it lives in, the last three applications for payment, the group chat the site manager actually uses and the RAMS pack as it was issued. Then we watch someone fill in what they fill in now. What we are looking for is the point where the same information gets written down twice, once at the gate and again in the office.

Your commercial figures stay in your accounts package and we read from it rather than replace it. Where we do move documents off personal drives, the store is set up in your company's name, with the logins and the ownership written into the handover. Whatever we build reads in your own job numbers, cost codes and revision letters, so the QS and the site manager are not learning a second way of naming the same job. If your existing site software already does the job and nobody was ever shown how, we will tell you that instead of quoting.

One project, one outcome, one price

No platform rollout, no company-wide change programme. We take the one thing that causes the argument at month end, usually the variation trail or the valuation, and build that. It goes in front of a site team on a live job with a real application going through, and we fix what they tell us before anything else gets discussed.

  • 01Time on site and time in the office, watching both ends of the same job
  • 02One project's paperwork mapped end to end: instruction at the gate, CVI, variation, valuation, application
  • 03A single form built for gloves, glare and one bar of signal
  • 04Documents moved off personal drives into one store with revision history
  • 05A written handover both ends get: what we built, where it sits and who to ring when it stops working on site
SITE VISIT FIRSTbefore we write anything
WORKS OFF-SIGNALforms that hold a dead spot and sync later
ONE NAMED OWNERthe same person on site and on the phone
FIXED SCOPEpriced per project, agreed before we start

Before you start. Practical questions, answered.

What to consider when deciding whether this work is right for your business.

01

Can Procore talk to Xero so job costs and subcontractor invoices stop being keyed twice?

Usually yes, in one direction. The project system owns the cost codes and Sage or Xero owns the ledger, so the route is normally an export of approved cost transactions mapped onto your nominal and job codes. Anything without a valid cost code is held back rather than posted to a suspense account nobody looks at.

02

Variations get agreed on site and written down nowhere, and RAMS sign-offs go missing. Can we fix that?

Yes, and it works when recording one is quicker than arguing about it later. A form on a phone captures the job, the instruction, who gave it and a photograph, then creates a variation record on the commercial manager's list straight away. The same form type takes a RAMS signature from the operative starting work. forms and reporting work

03

We are all on site all day and the office phone rings out. What do other contractors do?

Call handling can be scoped to collect a name, location and brief description when the office cannot answer. The useful part is what happens next: getting those details to the right person, with a clear callback responsibility. We agree the questions, routing and fallback before connecting it to your business number. how the phone side works

04

Our clients want to know where their job has got to without ringing the site manager. Possible?

Often, yes, and sometimes the tool is already in the building. Buildertrend ships a client view, so the first job is checking what your licence covers. Where a job lives across a programme and a costing system instead, a client page reads the stage each job sits at and shows that alone, with nothing about margin on it.

05

We are coming off COINS and the quotes for a replacement are frightening. What would you do?

Probably not a full rebuild. Contract accounting, CIS and retentions logic sit deep in those systems, so for the ledger itself, use the product you already pay for. The question worth asking is which parts you actually use, and the usual answer is that a few reports and one awkward export are doing the damage. Those get built beside it.

06

Does any of this touch CIS deductions and the retentions our QS signs off?

No, and it should not. CIS deductions and retention releases are calculated where your accounts live, and we do not put a second calculator next to them. What we can do is make the inputs cleaner: a subcontractor record with the verification status and the deduction rate held once, so the same detail is not re-entered on every invoice.

A build is a chain of decisions made at a gate, in a cabin and on a phone. The office should not be the last place to hear about any of them. Get the day off the site and into the system before the van gets back.

Start with the change you want to make.

Tell us what you use now, where the work slows down and what a better result would look like. We will explain the next step, with any paid work agreed before it starts.

Talk to Lightning