Architecture, engineering and surveying

Tight fees, and hours that never reach an invoice

We build software for design, engineering and survey practices in Nelson Tasman. It links the hours, the changes to the brief and the council's requests to the fee, so you see where the work is going while you can still bill it. You make the design decisions and sign everything.

1 · Where the money and the hours go

Changes nobody writes up, and stages that run over the fee

A couple ask on Sunday what it would cost to open up the kitchen and add a family room. The fee proposal goes out a week after the first meeting, built from an old proposal and your memory of how long that job took. Halfway through developed design they ask to move the kitchen. You draw it, and nobody writes it up as additional services. Then the council's request for further information arrives, half of it for the engineer, and the clients ring to ask why the consent is still with council.

For an engineer, at the end of the build, it is the PS4 waiting on the builder's PS3s. For a surveyor it is a requisition, or a 224(c) the developer rings about every week. At month end the consent stage has used more hours than its fee covered.

A design, engineering or survey practiceTodayWith the software in place
Enquiry to fee proposalEnquiries wait for a gap in the principal's day. The fee proposal goes out a week after the meeting, with the hours for each stage guessed.Each enquiry gets a first reply the same day with the questions you would ask first (address, age of the house, existing plans, rough budget), and is logged with the brief. A fee proposal by stage is drafted from your template and the hours similar jobs really took. You set the fee and send it.
Changes to the briefThe client asks for a change in a meeting or an email. It gets drawn, and is never written up as additional services.Client emails and meeting notes are checked for changes to the brief. An additional services note with an estimate of the extra hours is drafted for you to adjust and approve before it goes to the client.
Timesheets and hours against feeTimesheets are filled in on Friday from memory, and hours by stage get looked at after the stage has run over.Timesheets are drafted each day from calendars, job emails and the job folders people saved work in, for each person to correct and confirm. Hours against each stage's fee are shown weekly, from your practice system's figures where it has them, with a warning when a stage nears the limit you set.
Council requests for further informationThe RFI letter sits in email. Who owes which answer and how long each item has been open is in someone's head, and the hours spent answering often go to admin instead of the job.Each RFI item goes into a register showing who owes the answer and for how long. The covering letter is drafted item by item for you to check, and the hours go against the job.
Waiting on consultants and buildersThe PS1, the geotech report, the topo and the builder's PS3s are chased by phone, when someone remembers. For a surveyor it is the council's 224(c) inspection and the developer's outstanding works.A chase list shows what each consultant, builder, developer or council owes on each job and since when, with reminders you approve before they go.
Stage invoices and debtorsStage invoices go out when someone has time, often weeks after the stage closed. Debtors get chased when work is quiet.The invoice is drafted from the fee proposal when a stage closes, or at month end for the share of each stage done, and from the timesheets on time-charge work. You approve it, it goes out through Xero, and payments are matched. It cannot make a client or developer pay.

This will not bring in more work, lower build costs or speed up the council. It shows you the hours going into changes and council requests while the job is still running.

What it is worth

What unbilled changes to the brief cost you

Use your own numbers, and count only the changes you would have charged for if someone had written them up.

a year

These are your own figures multiplied out: what unbilled changes cost you now. A client may not pay for every change.

2 · Automate the process

Watch a house alteration from enquiry to paid

A couple want to open up the kitchen of their 1970s house in Atawhai and add a family room. A small design practice takes the job from the website enquiry to the stage invoice matched in Xero, with a voice-over. You can also have one written for your own practice. The businesses, people and prices are made up.

  1. Enquiry: the clients send a project enquiry on the practice's website.
  2. Chat: the assistant takes down the address, budget and timing and books a site meeting.
  3. Project plan: the measure-up notes become a plan by stage, and the surveyor and the engineer are brought in.
  4. Fee proposal: drafted from past job hours, approved by the principal, then sent.
  5. Schedule: stage one is planned around the surveyor's and the engineer's days on site.
  6. Updates: a change to the brief is written up and signed, and the clients hear when the consent is lodged.
  7. Paid: the payment for the stage invoice, with the signed extra on it, is matched in Xero.

3 · Stand apart

Then add something the others do not have

These use your own timesheets, past RFIs, property files and site visits. They are ideas we can scope around your practice.

Fee proposals priced from your own past jobs

A new brief is matched with past jobs of the same kind (alteration or new house, floor area, sloping or flat site, which council) and the hours each stage really took on them. The fee proposal and terms of engagement are drafted in your template the same day. You set the fee, and it is only as good as your timesheets.

Your RFI history as a lodgement checklist

Every request for further information from Nelson City Council and Tasman District Council goes into one register, sorted by Building Code clause, building type and consultant. Before you lodge, the technician gets a checklist from your own list plus the items raised on similar jobs. It does not judge compliance or promise fewer requests.

Property file and title summary before the first meeting

The property file and the title you have ordered are read and summarised: past consents and plans, easements, consent notices and any hazard notes, each with its page number. You read it before the measure-up and the fee proposal, so an easement or consent notice turns up before the concept instead of at developed design. It is a reading aid, not a planning or legal view, and someone still checks the originals.

Site visit notes and photos that build the report

Photos and notes are taken on the phone against the construction monitoring or observation level agreed for the job, and site instructions and the builder's PS3s are logged as they arrive. The engineer's PS4 file, or the designer's observation report, is put together for the person who signs to review. It never signs or issues a producer statement, and it does not protect you from claims.

Getting started

A sensible first project

Start with changes to the brief on one kind of job, alterations say, and a few live projects. Run it for a few weeks and compare what it shows with what you already knew.

  1. Changes to the brief

    Additional services notes drafted for the principal to approve.

  2. Hours against fee

    A weekly view from the systems you already use, with a warning before a stage runs over.

  3. Then invoices and RFIs

    Stage or monthly invoices drafted from the fee proposal, then the RFI register.

Questions

Questions before you start

Do we have to replace our practice system or spreadsheets?

No. We start from the timesheets, job list and Xero you already use. If your system already shows hours against each stage, we use its figures and build only what is missing. If a system has no way to connect, we tell you before we build.

Will it check our drawings for Building Code compliance or tell us if we need a consent?

No. It builds a checklist from your own lodgement list and the items councils have raised on your past jobs. Compliance is the judgement of the person who signs the design, and the council decides on the consent.

Does it write or sign producer statements?

No. It gathers the site records, photos and the builder's PS3s so the file is complete when the engineer sits down to write the PS4. The engineer reviews and signs. Nothing is issued without a person.

Where are our drawings and client files kept?

In your own systems, or in storage we set up for you in an agreed place. Before we build, we agree what the software can read and which AI service it uses, and we check how that service treats what you send. Once it is paid for, the code and the data are yours.

See all industries · See all live demos

Related: Trades and property services · Professional services and clinics

Based in Nelson, working with businesses across Nelson Tasman and the top of the South. Meet the team