Sold Job Queue
Every signed contract appears with its locate, HOA and material status, so production schedules only what is truly ready.
SIZ Group builds a patio contractor management app that shows the general manager every sold job waiting to start, which crew and machine is on which backyard, and how each install is tracking against the hours it was bid at.
A patio install is not a two-hour service call. Each job runs several days, depends on a utility locate clearing, needs pavers from one supplier and base stone from a quarry, and often competes with another crew for the only skid steer or mini excavator. A single rain day can push three jobs at once.
Profit lives in labor hours. A bid priced on square footage assumes a certain number of crew days, and a job with heavy clay, tight gate access or a surprise slab under the sod can quietly eat the margin. Most general managers only find out when the invoice goes out and the numbers do not match.
A generic task app does not understand any of that. Oversight for a hardscape company has to show sold backlog, machine availability, weather exposure and hours against estimate in one place.
Once a homeowner signs, the salesperson hands the contract to production, where someone puts it on a whiteboard or a shared calendar. The production lead requests the locate, orders material, books a dumpster or plans dump runs for the spoils, and assigns a crew leader when the start date gets close.
Breakdowns happen at each step. Contracts sit in a sales folder for days before production sees them, the skid steer is booked twice for the same Tuesday, and nobody knows a wall job has run two extra days until the crew leader mentions it at the shop. The general manager ends up making phone calls to piece together a picture that should already exist.
The general manager opens the app with a coffee at the yard. The sold queue shows nine contracts waiting, four with locates cleared and materials confirmed, so those are the ones ready to schedule. A flag on one job notes that the HOA approval letter has not come back yet.
The in-progress board shows three active installs. One retaining wall job is at well over its estimated crew hours, with a note from the crew leader about buried concrete footings. The manager approves a change order request and moves the mini excavator from a job that finished early to help.
Rain is forecast for Thursday, so two Thursday starts slide to the following week with one drag on the calendar, and the affected crews see the change on their phones. On Friday the weekly report lands: jobs completed, hours against bid by crew, and backlog by sold date.
Every signed contract appears with its locate, HOA and material status, so production schedules only what is truly ready.
Drag a job to a crew and a start date, and the crew leader's phone updates at once.
Skid steers, excavators, compactors and trailers are booked against jobs, with a warning when two crews claim the same machine.
Clocked crew time is compared to the estimated hours on each job while it is still running, not after invoicing.
Move a rained-out day and every dependent start shifts with it, with notices to the affected crews.
Completed jobs, backlog age and crew performance against bid, delivered to the GM's inbox each Friday.
Most hardscape companies already estimate and invoice in a platform such as LMN, Aspire or Jobber, with accounting in QuickBooks. The oversight app should read sold jobs and estimated hours from those systems rather than ask anyone to retype them.
Where an API exists we connect directly, and where it does not we use scheduled exports for the fields that matter. Crew hours can come from the time clock you already use or from a simple clock-in inside the app, and we would decide which during scoping.
The first is building thirty charts. A general manager needs perhaps four numbers each morning, and a crowded dashboard hides the one job that is going sideways. We would start with backlog, active jobs, equipment conflicts and hours against bid.
The second is reporting on data that crews never enter. If the hours report relies on crew leaders typing times at the end of a hot day, it will be wrong. Capture has to be one tap or automatic. The third is copying the whiteboard exactly instead of fixing the parts of it that already cause double bookings.
Mobile apps at SIZ Group start at $4,500, and an oversight build grows from there based on a few clear factors. The biggest are the number of systems we connect to, how many user roles need different views, and whether crews need full offline use.
The surest way to control scope is to agree on the three reports the general manager will actually read every week, build those well, and add the rest once real data is flowing. Scope and price are confirmed in writing before any build begins, so additions are a decision, not a surprise.
Both. Managers get a web dashboard for planning and an iOS and Android app for checking jobs from the truck, while crew leaders use a simpler mobile view.
It can, but we usually advise against it at first. Reading from your existing estimating and scheduling platform is cheaper and less disruptive, and the oversight layer adds what that platform lacks.
They are only as good as the time capture behind them. We design clock-in to be one tap or pulled from your existing time clock so the numbers reflect what actually happened on site.
Yes. Subcontractors can receive assignments and report progress with restricted access, and the general manager sees their jobs on the same board as in-house crews.
SIZ Group offers post-launch support for fixes, updates and new reports. Many companies add features after their first full season, once they know which numbers matter most.
Book a free scoping call to walk through your production board and the reports you need, and leave with a written scope and price.