Slab approval record
The approved slab photo, slab ID and edge profile are stored together and time-stamped.
A customer portal website for countertop fabricators gives homeowners and builders one login for slab approvals, install dates, priced changes and care papers. We build it around the way a stone job moves from slab selection through template and fabrication to install day, so the office stops answering the same status questions.
Approvals drive stone work, so homeowner slab approval online must leave a record the office can retrieve on demand. A customer picks a slab from a photo or a yard visit, approves the edge profile and the sink cutout, then waits while the shop fabricates. Each approval changes the look or the price, so each one matters.
The waiting period is where the calls start. Customers ask whether the slab has been cut, when the template is done and whether the install date still holds. A countertop project status page that shows the stage a job is in, with the next step highlighted, answers those questions before the phone rings.
Changes are common in stone. An added cooktop cutout, an extra seam or a taller backsplash can arrive partway through, and each has to be priced and approved. The portal gives every change one record instead of a text thread that nobody can find.
The operations manager is looking for fewer status calls without any extra admin. Before sign-off, have the agency demonstrate three things on a live record: a homeowner locating the signed slab photo quickly, a planned install date that agrees with the shop calendar, and a priced addition that shows up without a second round of data entry.
Use a completed job from last season as the test case, including its slab ID, template notes, change orders and final invoice. If the customer must click through several menus to reach any one of them, the navigation needs another pass.
Permissions need the same scrutiny. Clients should be fenced off from one another's jobs, installers should see logistics only, and bookkeeping should be able to close out payment with no access to the production schedule.
The first release should cover the slab approval record, the production stage view, priced changes and a document library, with stone order tracking for customers built into the stage view. Those four cover most of the calls. Each approval is time-stamped and tied to the slab ID and the edge profile.
Integrations come after the core works: a link from the job-costing tool, invoices pushed to the accounting package and template photos pulled from the phone camera roll. Until a link exists, a nightly export does the job.
Some features can wait: online deposits, a sub-trade schedule for plumbers and electricians, and a review feed on the site. A later phase can add them once the team knows which records customers actually open.
The approved slab photo, slab ID and edge profile are stored together and time-stamped.
Each job shows whether it is templated, in fabrication, on the truck or installed.
Added cutouts or extra seams appear as priced changes the homeowner can accept or decline.
Care sheets for each stone type and the fabricator's warranty sit beside the job.
The confirmed install window and the crew's arrival details sit at the top of the job.
Stone demand climbs in spring and early summer, when kitchens get refreshed, and it climbs again before the holidays. Those rushes bring a flood of status questions in the same weeks the shop is busiest, so the status view matters most when the team has the least time.
Builder work follows its own calendar, with many units approved in batches. A builder account should hold several homes, each with its own slab approvals and install windows, so the batch does not become a stack of separate emails.
In quieter months the team can refresh the countertop warranty and care documents, check the care sheets and archive closed jobs. The portal is then clean before the next wave arrives.
A common error is signing off slabs from a monitor alone. Natural and engineered stone vary between slabs, and a homeowner who approved a photo may reject the piece on install day. Arrange an in-person or video check at the yard, and log the slab ID that the approval covers.
Another is treating the portal as an optional extra. If a change is agreed on the phone and never entered, the approval page describes a countertop that does not match the work in progress.
Hiding the stage is the third. When the record says nothing about cutting or delivery, the homeowner calls to ask, and the office loses time to status checks on jobs that are moving fine.
Count the calls that ask for a stage update, a slab photo or a warranty sheet, and compare them with the month before launch. A steady drop in those calls means the portal is answering questions the team used to answer by hand.
Track how long each job waits between slab approval and a set install date, and how many jobs reach final payment without a chase. Both show whether approvals are moving and whether customers can follow the work.
Look at page views too. A care guide that gets read while the approval page sits idle points to wording that needs attention before the next batch.
Websites range from $300 to $2,200, depending on scope. Stone portals with several job stages and a link to accounting usually fall in the upper half of that range. The written figure follows the scoping call.
They should see the actual slab first, in person or by video at the yard. The portal then records that the slab was viewed, the approval given and the slab ID chosen, so the record matches the piece that gets cut.
Not always. A builder account can see every unit, with its own approvals and dates, while each homeowner sees only their own kitchen. The office decides what each role may see before launch.
Care sheets and the fabricator's warranty stay on the account for the period the contract names. After that, the account can keep the signed approvals and final invoice, and the shop keeps its own archive.
A free scoping call comes first, then a written scope and price before any build.