Asphalt paving software for a crew whose material has a clock on it.

Not as a quantity, and it is worth being straight about rather than letting you find out after you have moved. Placed quantities are not tracked — no tons placed, no square yards, no thickness on the log. What it does hold is the money and the labor: materials invoiced against materials committed in job costing, so the asphalt you were billed for sits against the job, and purchase orders per load or per release so committed cost shows up before the plant invoices you. The tonnage reconciliation itself stays in your takeoff and on the plant tickets. One habit that helps: put the day’s ticket count in that log’s narrative, which at least dates it.

By making the record while the crew is still standing there. The daily log for that day carries the hours per worker, the areas, the conditions and a delay with its cause from a fixed list — weather, material, labor, access, GC direction, inspection or other — plus photos of a lot full of other people’s trucks. If the GC directed the stand-down, that is also a change event logged the same morning, which is the thing a priced change request is built from later. For a half day already spent, a T&M tag priced off your own rate list and e-signed on site by whoever authorizes it is the cleanest version, because it is agreed in the hour rather than argued in the month.

As a change event the morning the proof-roll fails, with the areas and photographs, long before anybody writes a change order. That is exactly why the pack has you confirm who accepts and corrects the subgrade before you mobilize — the question with no written answer is the one that becomes your cost. Keep undercut and extra tonnage as unit-price lines in the schedule of values from the start, so the correction is a measured quantity at an agreed rate rather than a negotiation with your paver idling. Approved change orders are added to the schedule of values automatically.

Only if you can show the condition you left it in and the condition you came back to. The log entry with photographs on the day binder was placed establishes the first; a log entry with photographs before surface establishes the second. From there it is a T&M tag or a change request, and several tags can convert into one change order, so a season of dents does not become fifteen separate arguments. Put it on the schedule of values as a pre-surface repair unit price at contract time — by the time the damage exists, you are asking for a rate on work the GC would rather you simply paved over.

Yes, and for your trade it is the habit that pays best. Each day’s log records the weather, the areas worked, the hours per worker and a delay with its cause. A morning canceled because the surface temperature never came up, a day lost because the plant had no slot, a week lost because the season closed — each logged on the day, in its own words. A run of those is a dated account of a schedule that physics and a plant calendar wrote. It will not move the GC’s date; it is what makes the compression conversation something other than two people remembering differently.

With Area Tracking switched on in Settings, yes — it is not on by default. With it on, sub-grade, base, binder, surface, striping and seal hours stay distinct and you get budget versus actual per phase while there are still phases left to place. Left off, job costing is per job and grouped by cost type — labor, crew lump sum, materials invoiced, materials committed, QuickBooks costs and subcontractors — against your budget lines. Quantities are not tracked either way, so cost per ton or per square yard comes from your own takeoff put next to those hours.

Through the schedule of values first and the logs second. Every mobilization and its traffic control belongs on its own line, because the phasing plan the pack has you confirm is the thing that multiplies them — that is a contract conversation, and it is much cheaper than a claim. Then each phase has its own dated logs and its own crew assignments, so the iron you moved and the days you moved it are a record rather than a recollection. Crew Scheduling shows it from the other side: the men and the jobs they were not on.

Give it its own schedule-of-values line and its own date. The Draw Calendar holds each job’s billing cutoff and submission method, with reminders, and retainage is tracked against the draws you have submitted — what was certified, what is held and when the money landed. SubMark will not release retainage for you, chase the GC or schedule the return trip. What the separate line does is keep an open seal coat in front of you on every draw, instead of the common version of this, where a seal coat nobody scheduled sits unbilled for months while the retainage on an entire contract sits with it.

No. Keep submitting through whatever portal, template or email each GC requires. SubMark is where the schedule of values lives — binder split from surface, every mobilization on its own line, undercut and damage repair as unit prices — and where every draw you submit is logged against it. Procore, Textura and GCPay are recorded as the submission method on a job; nothing is sent on your behalf. SubMark is not a document generator.

Yes. Connect QuickBooks Online once and bills and purchases pull into job costing — hourly, if you switch auto-pull on — so a plant invoice and a hauling bill sit against the job they were placed on. Draws go across as QuickBooks invoices and POs as purchase orders, one at a time with a click. For your trade the habit worth keeping is a PO per mix release, per hauling contract and per traffic-control order, so committed cost shows against the budget before the plant and the trucking company invoice you. A coverage meter shows how much of the cost pulled from QuickBooks is coded to a job at all; it is company-wide rather than per job.

No. Field users are free and unlimited, and so are the subs you invite into a job. You pay one company subscription: $249 a month with your first 3 office users included, then $39 a month each. The whole breakdown is on the pricing page.