Free through your first project · no card · start on one live job
Not in one big number. In four small ones that each look reasonable on the day, and only add up once the job is closed.
Paper timesheets come in on Friday, get typed up the week after, and reach the accounts at month end. The cost of a Tuesday in January is a number you first see in February.
Somebody on site is told to do it, so it gets done. The instruction is verbal, the price is agreed later, and until it is agreed the work sits in your labour cost and in nobody else’s.
Travel, waiting for materials, standing time when a trade cannot start until another finishes. All of it is paid, and none of it is in the rate you priced the job at.
The excavator finished on the Wednesday. It goes back when somebody remembers. That gap is charged at the same daily rate as the days it worked.
“Late is the same as wrong, if you cannot act on it.”
Month-end reporting tells you what happened to a job you can no longer change. A twelve-week programme reported monthly gives you three readings, and the first one lands when a quarter of the work is already done.
Keeping a job on budget is not about reporting harder. It is about the gap between the day a cost happens and the day you can see it. Close that gap and an overrun becomes something you can still do something about.
Reported monthly
The overrun is history by the time you read it.
Priced as it happens
Example figures
Week two, with something still to decide.
One thing, really. The record a worker makes when he taps in is the same record your project cost is built from. Nothing has to agree with anything afterwards.
The hours a worker logs on site and the cost on your project are one record, not two that have to be reconciled
Labour lands against the budget the day it is worked, not the month it is invoiced
Every site is on one screen, so you stop driving over at seven to find out who turned up
Your accountant gets every hour against every project, and it exports to Xero and to a spreadsheet
This is not a replacement for your accounts package and it will not price a job for you. If your spreadsheet works, keep it. What this adds is the join between the hours worked and the cost on the project, which is the join that is usually missing.
From the first week. A worker taps in on site, the hours land on the project, and the cost against the budget updates the same day. There is no month-end step in between.
No. Add one live project with its budget and run it alongside whatever you use now. If it does not tell you something your current method does not, you have lost a few minutes.
They log hours the same way against the same project, so their cost sits on the same line as your direct labour rather than arriving separately on an application.
Yes. It exports to Xero and to a spreadsheet, and you can cancel whenever you like with no notice period. Your records leave with you.
Your own budget, your own people, your own numbers. Read what it tells you at the end of the first week, and decide then.
Register NowShort of people rather than short of numbers? How we place trades on your site