Site measurements and notes returned to the estimate, with conflicts shown instead of overwritten.
Costing and commercial control. 5 questions answered below, each with the arithmetic behind it and the limits of what the tool decides. Open the Field Sync tool.
Measurements taken on site and estimates held in the office are the same numbers at different moments, and this is the mechanism that brings them together. A dimension recorded on a phone in a room syncs to the estimate it belongs to, with the direction of the change recorded rather than overwritten silently. The conflict rule is the part that matters. Where a synced figure disagrees with what is stored, the tool does not pick one. It shows both, with their sources and times, and the person decides. That is slower than automatic merging and it is the only approach that leaves a record of what happened, which is what a client query or a cost dispute eventually depends on.
A wall measured on site at two point six five metres is entered against an estimate that holds two point seven from the drawing. The sync does not replace either. It shows the drawing value and the site value, with times and sources, and the person chooses the site measurement and the reason is recorded. The blockwork quantity recalculates from the chosen figure, and the estimate's history shows that the change happened, when, and on what basis.
It brings a measurement taken on site into the estimate or takeoff it belongs to, recording where it came from and when. Where the figure differs from what is stored, it reports the conflict rather than choosing. The result is an estimate that reflects site reality and a history that shows how it got there.
It reports both and asks. The stored figure has a source, usually a drawing or an earlier measurement, and the synced one has a source too. Choosing automatically would discard one of them without a record, and the discarded one is often the evidence someone later needs. The resolution is a person's decision, recorded with its reason.
It queues the change and sends it when a connection returns, which is how a site actually works: basements and new builds have no signal. A queued record shows as pending rather than as sent, so nobody assumes a figure is in the office when it is still on a phone. That distinction is small and it is the difference between an estimate that is current and one that is quietly stale. A pending record is visible, so somebody can chase it; a silently lost one becomes a phone call from a site that has already ordered the wrong quantity.
No. It moves measurements between a site and an estimate, which is one specific flow of data. Scheduling, task assignment, progress tracking and document control are a project management system, and this is not one. Use it for the dimensions that decide quantities, and use the right tool for the rest.
The people on the job it belongs to, and the record keeps its source. A synced measurement is part of an estimate, so it is visible to whoever can see that estimate, which is the scope that makes sense: a site measurement is not public data, and it is not private to a phone either.