Rivet runs your plant, your crews and your compliance from one place, and it keeps working at the bottom of a trench with no bars on the phone. Built for New Zealand trades and civil contractors. We run the server; the records stay yours.
Most site software is written for an office and handed to a crew. It wants a signal, it wants a login every morning, and it wants the job done its way. So the prestart gets filled in at four o'clock from memory, the docket lives in a ute door, and the JSA is signed on a page nobody files.
Rivet was built the other way round: on the job, with the people doing it, for two New Zealand contractors who use it every day. Every part of it exists because somebody asked for it on a Tuesday.
Drawings are already on the phone. A sign-on with no coverage is recorded, queued and sent when the truck comes back over the hill. Photos, JSAs, prestarts, the lot. Nothing waits for a bar of signal, and nothing is lost because there wasn't one.
You are sold the parts you use. A drainlayer never sees the electrical certificates (unless that drainlayer is planning a change of profession), and a sparky never sees the trench calculators. Turning a module off hides it and keeps every record behind it: switch it back on a year later and it is all still there, right down to the last prestart.
A Certificate of Compliance is handed to a customer, kept for seven years and read by people who know exactly what the government form looks like. So Rivet prints the form, not a summary of it: the same boxes in the same places, the tick boxes ticked, the test results block, the declarations word for word, and the compliance mark.
Fill it in on the phone at the board. Check it on screen before it becomes a record. It files itself, and the registration number comes off the worker's own licence rather than being typed again, and says so if that licence has expired.
Public holidays worked out from the Holidays Act, with Mondayisation and the anniversary day your crews actually observe. Addresses that autocomplete to real NZ ones. WOF, rego and RUC rather than MOT and tax. AS/NZS 3000 on the certificates.
None of it is a setting somebody has to find and get right. It is simply correct on the morning you open it.
Most site software is built in an office and then sold to a site. Rivet was built the other way round: on the job, with the people doing it, for two New Zealand contractors who are in it every day. Every part of it is here because somebody asked for it on a Tuesday: sick of writing the week on a whiteboard, and sicker of paying stupid money for a system that takes a fortnight to learn.
Built by a tradie, for the trades. Not by a lawyer, and not by an IT bloke in a dark room who has never stood in a trench. Ask for something and it does not go on a roadmap for next year: fixes and improvements go out most weeks, not most quarters.
No server for you to patch, back up or worry about. That is ours. What stays yours is the data: your own database rather than a row in somebody's shared table, so nothing of yours sits alongside another company's.
Every backup is encrypted with a passphrase only you hold and lands in your own Microsoft 365. Your records live where your other company files live, and you can walk away with the lot. Two-step sign-in and a full audit trail on top.
The quickest way to know whether Rivet suits your outfit is half an hour on a real one, with your own jobs in front of you. No slide deck, no trial that expires: a look at the thing itself, and an honest answer about whether it fits.