Concept review and approval
Clients comment on renderings and approve the concept in one place, with each version dated and kept.
A customer self-service app for landscape design firms lets homeowners and property managers review concepts, approve changes, book site visits and follow the install schedule without waiting for an email reply. SIZ Group builds it for iOS and Android, with a web view for clients who prefer a larger screen.
A landscape design client makes a large decision based on drawings they find hard to read. A homeowner may need to compare a planting plan, a material board and a budget before approving anything, and a generic portal rarely handles that kind of review. The app has to present the design as a set of decisions the client can make one at a time.
Trust matters as much as the drawings. A client who gets a clear approval trail, a dated change log and a straight answer about the install schedule will recommend the firm. A client who has to chase three emails for a plant list will not, however good the design looks on the page.
Most design firms send concept packages as PDF attachments, collect feedback by email and track approvals in a spreadsheet or a project tool such as Aspire or Jobber. The designer ends up as the messenger, forwarding markups between the client and the drafter. A revision agreed on a phone call often never reaches the drawing set.
The gaps show at install time. A plant substitution approved verbally is missing from the final plan, and the crew arrives with the wrong material. Site visit times move twice because the calendar lives in a different system from the approvals. A site visit booking app would stop most of that churn, because the visit, the approval and the plan would share one record.
The owner signs off when clients can review and approve a design without a call, and when the approval trail matches what the crew builds. The test is simple. Can a homeowner open a concept, complete a planting plan review and approve a change order from a phone? A client design approval portal should make those three steps work without help.
The second test is document control. The client should always see the current drawing set, and every superseded version should be clearly marked. A crew working from an old plan is an expensive mistake, so the app must make the latest revision the only one that looks final.
Clients comment on renderings and approve the concept in one place, with each version dated and kept.
Plant lists and substitutions appear as line items the client can accept or decline before the crew orders stock.
Clients pick an open visit window that matches the designer's calendar, and the visit is logged to the project.
Each phase shows its planned date, its status and the crew lead, so clients never have to ask where the job stands.
Changes to scope or price go out with the revised plan attached, and the approval is stored against the job.
Most landscape design firms draft in AutoCAD, SketchUp or Vectorworks and run jobs in Aspire or Jobber. The app can act as a landscape project status tracker, reading project stage and approved plans from those systems where an export or API exists, so staff do not upload the same drawing twice. Where no link is available, a scheduled export keeps the client copy aligned.
Contract approvals can run through DocuSign, while plans and plant lists live in Dropbox or Google Drive. The app works as the client's front door, so a homeowner never needs to know which tool holds which file. Each link is settled during scoping, before any build begins.
Design firms see a rush in late winter and early spring, when clients want plans approved before the planting window opens. Fall brings a second wave of installs before the ground freezes in colder regions. The app should show clients the real calendar of approval deadlines, so a late decision in March does not become a missed planting slot in April.
Quieter weeks are good for refreshing templates, updating plant lists for the season and clearing old drafts from the portal. Seasonal reminders can go out automatically, such as a note that spring install slots are filling, sent when the calendar suggests it.
Before design starts, the firm should gather the client list with project types and contract stages, the plant and material library used in recent jobs, the permit and HOA approval steps for each area served, and the approval rules for drawings and change orders. Missing pieces slow the first release and create manual work for the team.
Access rules need a decision too. Decide which clients can approve a change order, which can only comment, and which contacts, such as a spouse or property manager, should have their own login. Write those rules down during scoping so the portal matches how the firm already signs off work.
Yes. The portal always opens the latest approved set, and earlier versions stay visible but clearly marked as superseded. We confirm how revisions are numbered during scoping, so the crew and the client work from the same file.
Most clients approve their first concept within minutes, because the steps match a familiar shopping flow. We agree a short guide with your team, and the designer can walk the first few clients through it on a call.
Yes, if the role is set that way. A property manager can hold separate approvals for each property, and each approval is recorded against the correct site. Access is confirmed during scoping, before any client is invited.
A client list, a sample project from start to finish, your plant and material library and the approval rules you use today. With those, we can scope the first release and show a realistic price before any design work begins.
Every approval, comment and signed change order is stored against the job with the time and the person who acted. The latest version is the only one marked current, so nobody builds from an email attachment that has been superseded.
Share a recent job from concept to install, and we will show how the client portal would have handled it, with the price and scope agreed up front.