Run the job so year two has an answer.
A defect gets queried in year two and nobody can remember who approved the fix. That's the argument. Set a project up here and each change gets written down on the job as it happens: what was agreed, what moved, who raised it, and when. Nothing arrives by itself, and no money moves through it. You put it there while the work is going on, which is the only reason it's still true later.
Already have an account? Sign in
What a project actually holds
Tasks and a timeline, the quotes you accepted, milestones, the daily log, photos, defects, RFIs, variations, status reports and an activity trail. That's the whole list, in roughly the order the work runs.
The quotes you accepted
Quotes on the projectThe quote that won the job sits on the job, at the number it was accepted at, so the price you agreed doesn't quietly become the price somebody remembers. A rate here is a planning figure. It isn't a payment instruction.
Tasks and the timeline
Tasks and a timeline on the projectLay the tasks out, set the dates, and see what a slip does to everything after it. The programme and the timeline are here and they do what you expect. The useful part sits underneath them: a date that moved keeps the reason it moved, instead of being written over.
Variations
Variations raised on the jobRaise it, price it, send it for a decision, and it stays on the job beside the defect or the request that caused it. The date it was raised gets written down on the day rather than reconstructed afterwards.
Requests for information
RFIs on the job: raised, answered, closedAsk the question that's holding the work up, get it answered against the job, and leave the answer where the next person will look for it. Reasons don't survive a group chat.
Daily log, photos and defects
Daily log, photos and the defect listLog the day. Attach the photos. Work the defect list down to closed. What was found and what was fixed is on the job, so a query later has somewhere to land.
Milestones and status reports
Milestones and period status reportsBreak the job into milestones and draft the period report off what's already on the record. This is the state of a claim, written down: what is held, when it releases. None of it moves money, and a release is authorised by a person rather than by a screen.
The activity trail
Activity on the projectEvery change leaves a line: who did it, what changed, when. At the end the client is handed something that reads in order, instead of a folder of loose PDFs and a promise that it was all agreed at the time.
What does not turn up here on its own
Nothing flows into a project by itself. A project shows the awarded contractor's name. It does not show your planning pack and it does not show the documents you sent for signature, because those live where you made them. There is no one screen that puts the three of them side by side. What is here is the job's own record, and it's here because somebody put it there while the work was going on.
Running the job, answered
What does Project Management actually hold?
Tasks and a timeline, the quotes that were accepted, milestones, a daily log, photos, defects, RFIs, variations, status reports and an activity trail. That's the lot. It is the job's own record of what was agreed, what changed, and who raised it when.
Is this a Gantt tool?
There's a programme and a timeline, and they do what you expect. They're contents on the page, not the promise on it. Nobody has ever settled an argument on site by showing a nicer bar, so what matters here is that a date which moved kept the reason it moved.
How are variations handled?
Each one's raised on the job and stays there, beside the defects and RFIs it relates to, so the sequence holds together instead of scattering across email. When one is disputed later, the date it was raised is already written down rather than being a matter of who remembers what.
Does anything arrive here from elsewhere on the platform?
No. A project shows the awarded contractor's name and that's the extent of it. Your planning pack isn't here, the documents you sent for signature aren't here, and there is no single screen that shows the three together. They live where you made them.
Does Project Management move money?
No. Milestones and retention are modelled on the job, so you can read the state of a claim and what's being held. None of that moves money, and a release is authorised by a person. A rate on a project is a planning figure, not a payment instruction.
Run it on one record
All of this is live on the network today. These screens record and organise the state of a build; they do not move money. The acts a professional has to sign, like certifying a milestone or signing off a large variation, stay with a person.
Urban Pulse is an Australian construction platform: site intelligence, town planning, contractor marketplace, Send & Sign, and project management in one workspace.