Data ownership and exit terms in builder software contracts

Most builders now run a job from several software products at once. Quotes and takeoffs sit in one system, job files and photos in another, variations and selections in a client portal, timesheets in an app on the phone, and the accounts feed in the accounting package. Each product arrived with a sign-up page and a set of terms that few people read in full, and most of those terms were written by the vendor, for the vendor.

This article answers a narrow question. What does your software contract say about who owns the data you put into it, what format you can take it out in, and what it costs to leave? That is a different question from the duties you owe clients over their personal information, which is a separate matter. Here the subject is your rights against the vendor, and what you will be left holding when the relationship ends.

The answers usually sit in three or four clauses that nobody negotiates. Read them before the first subscription is paid, because the time to ask for a change is before years of job history are inside the system.

Why the job history is worth more than the subscription

A subscription for estimating or job management software is a modest monthly cost. What the system holds is not modest. Over several years it accumulates your price book, the rates you have paid subcontractors, the margin you achieved on each type of job, the variations you priced and whether the client accepted them, and the photos that show what the slab looked like before the tiles went on. That is the evidence behind a payment claim, a defect dispute or a tender response, and it is the basis for quoting the next job accurately.

A builder who loses access to that history has lost a working tool and a record. The record matters most in the situations where a builder is already under pressure: a variation dispute, a claim from a former client, or a licence query that asks what was done and when. Treat the vendor as a place where you keep your business records, not just a place you rent a screen from.

The ownership clause and what it actually grants

Vendor terms often say the customer owns its data, and then a few paragraphs later grant the vendor a licence to use that data to run the service, improve the product and produce anonymised or aggregated information. Read those two parts together. Ownership of the raw job records may well be yours, while the right to use them for the vendor’s own purposes can be very wide. Ask what “improve the product” means in practice, whether it includes training models on your pricing, and whether aggregated information could be traced back to your business.

Check also who else the vendor shares data with. Most cloud software is hosted by a third party, and the terms should say so. Ask where the data is stored and whether the vendor can move it to another location without telling you. None of this is exotic. It is the same question you would ask a subcontractor about who else sees your drawings.

What a usable export actually looks like

A vendor can say you have an export function and still leave you with nothing you can use. The test is whether the export keeps the structure of the job. A list of jobs in a spreadsheet is not enough if the variations no longer link to their jobs, the photos arrive as loose files with no record of which job or which stage they belong to, and the selections have lost their dates.

Ask for a test export of a real job before you commit, then open it on a computer that does not have the vendor’s software installed. Check that you can find the job, see its quote and final cost, see each variation with the date it was raised and accepted, and open the photos. A PDF of an invoice is a record of what was sent. It is not data you can search, filter or move into another system.

When you review the export, look for these things in particular:

• Whether jobs, variations, selections and payments stay linked to one another.
• Whether attachments and photos come out with the job they belong to, and keep their dates.
• Whether the export is in an open, documented format, and whether the vendor will explain the fields.
• Whether you can run the export yourself, at any time, without waiting for support.
• Whether the price book, subcontractor rates and client contact details come out in full.

The exit costs that do not appear on the price list

The subscription price is the visible cost of leaving. The less visible costs usually sit in the terms, and they tend to surface at the point when you are least able to choose: when you have decided to go, and the job you are in the middle of cannot wait.

Look for a charge for a full export, a fee for read-only access after cancellation, and a requirement that you give written notice of cancellation, sometimes well before the renewal date. Some vendors remove access on the day the subscription ends, with no window to take a copy. Others keep the data for a retention period and then delete it, and the terms may not say whether the deletion is confirmed to you in writing. An automatic renewal can add a further year of fees if the notice is missed.

Each of these costs is small on its own. Together they can turn a move to a better product into a choice between paying twice and losing the records.

Termination, retention and what the vendor keeps

The termination clause decides what happens to your data when the agreement ends for any reason, including when the vendor ends it. Check three things: how long you have to take your data out after termination, whether the vendor keeps copies in backups after it deletes the live data, and what triggers deletion. A clause that says the vendor will delete your data “in line with its retention policy” is not a commitment. Ask to see the policy and to have the deletion confirmed in writing.

Also check what happens if the vendor is sold, merges or closes. A reasonable term says a change of ownership does not reduce your rights to your data, and that you will get notice and a window to export before access ends. If that clause is missing, raise it before you sign. Asking for it afterwards gives the vendor every reason to say no.

Unfair terms and the limits of relying on them

The Australian Competition and Consumer Commission publishes guidance on unfair contract terms. In general terms, the unfair contract terms regime in the Australian Consumer Law can extend to standard form contracts with small businesses. A term that is one-sided, that lets one party change the contract unilaterally, or that creates a significant imbalance without a legitimate reason may be open to challenge. A sole trader or a small building company may be able to rely on that regime.

That is a fallback, not a plan. A challenge takes time, the outcome is uncertain, and in the meantime you have jobs to run. The useful way to read the regime is as a reason to ask the vendor to change a term before you sign, and as a guide to which terms are worth pushing on. Get advice from a lawyer before you rely on it in a dispute, because the answer turns on the exact wording and the facts.

Worked example: moving off a quoting platform

Consider a builder in western Sydney who has run quoting and job costing on one cloud product for several years. When a second product with better takeoff tools comes along, the owner asks the current vendor for a full export. The vendor offers one, but it returns a spreadsheet of jobs and line items with no link to the variations, and the photos are not included. The cancellation clause requires written notice before the renewal date, and the vendor keeps read-only access for a period after that, at a charge.

The builder takes three steps. He asks the vendor, in writing, for an export that includes the photos and variations, and keeps the reply. He runs a test export on an old job, opens it on a laptop without the software, and finds the variations cannot be matched to their jobs. He then asks the new vendor how it imports that structure, and decides to keep the old product for read-only reference through the next busy period rather than lose the links. Anyone planning a similar move can cost it using the article on the real cost of switching estimating software. The switch was not hard because the software was difficult to replace. It was hard because nobody had asked, before the first invoice, what would come out the other end.

When the vendor will not move on the terms

Some vendors will not change their standard terms for a small customer, and that is a commercial answer you can work with. The question then becomes whether the product is still the right one at the terms on offer. A cheaper or more capable product with a weak exit clause may cost more over the life of the business than a dearer one with a clean export. Compare the exit terms alongside the features and the price, rather than leaving them until last.

If you decide to proceed on the standard terms, write down the risk you have accepted and the date you accepted it. Note which records would be hard to recover, which ones you can rebuild from the paper file, and which ones exist only inside the system. That note is worth more than it looks when a dispute arrives years later and somebody asks why the records were not kept. It also gives you a clear list of what to protect with the measures in the next section.

Some builders negotiate a short side letter instead of a full contract change. A side letter can confirm the export format, the notice period for cancellation and the access window after cancellation, and it can be signed by the same person who signs the main agreement. Ask whether the vendor has used one before. A vendor that says no to every request has told you something useful about how it will behave when a dispute comes up.

Keeping your own copy of the business records

The most reliable protection is not a clause. It is a habit. Schedule an export from each system into a folder that you control, on a set cycle, and keep the exports for longer than you think you need them. Name each export by the system, the date and the job it covers, so that a record can be found without opening the software. Store the photos separately, with their dates in the file name or in a log, because a photo that has lost its link to a stage is much less useful as evidence.

Test the copies as well as making them. Once a year, open an export on a computer that does not have the software and check that you can read a job from start to finish. If you cannot, the copy is not yet a record. Keeping the copies is the job of the business. The vendor is a supplier, and the business should not depend on the supplier to keep its evidence intact.

Keeping a dated copy of the terms you agreed to

Vendors change their terms, and most do it by posting a new version and letting the old one disappear. Save a dated copy of the terms you accepted, in the same folder as the job records rather than in your email. If the vendor later says a restriction always applied, you can show what you agreed to and when. The same habit helps when you come to sign other digital agreements, which is covered in the article on electronic signatures for building contracts.

Ask the vendor to notify you in writing before any material change to its terms takes effect. A notice that appears inside the product, which you may never open, is not the same thing. Keep a record of the notice, and of your decision whether to accept the change or leave.

The commercial risk is easy to underrate because it arrives slowly. A subscription that is cheap to join can be expensive to leave, and the difference only shows up when the business needs to move. Reading the exit terms before you sign costs an hour. Recovering the records after a dispute, or after a supplier has closed, can cost far more.

If you are working through the wider set of duties that come with running a building business, the PointCPD guide to NSW builder CPD sets out how the licence obligations fit together. Software decisions are a small part of that picture, but they feed directly into record keeping, and records are what an audit asks for.

Questions builders ask

• Admin
• Contracts
• Software

Published 15 October 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.