Direct answer
Map polygon editor connects proposed turf boundary to operator-reviewed areas that can feed pricing, with explicit operator review before downstream actions. It is designed to keep the customer, property, scope, work, and financial context connected without pretending that automation removes operator responsibility.
Input and output
| Stage | Record | Required review |
|---|---|---|
| Input | proposed turf boundary | Confirm identity, completeness, and permission |
| Feature action | Map polygon editor | trim beds, buildings, pavement, water, and ambiguous edges |
| Output | operator-reviewed areas that can feed pricing | Approve before it affects the customer, crew, invoice, or books |
How the workflow should run
- Open the correct customer and property context.
- Review the proposed turf boundary; correct missing or uncertain information.
- Use map polygon editor to produce operator-reviewed areas that can feed pricing.
- Before release, trim beds, buildings, pavement, water, and ambiguous edges.
- Record the result and any exception on the same operational chain.
What this feature does not decide
- Whether remote information is sufficient for a specific property.
- The operator's prices, margin, tax, legal terms, or accounting policy.
- Whether a customer change is inside the accepted scope.
- Whether an exception is safe, compliant, or ready to release.
Where it connects
LawnVex connects an operator-reviewed property measurement to three-tier quoting, scheduling, routing, invoicing, Stripe payments, and supported QuickBooks Online synchronization. The operator remains responsible for boundaries, scope, rates, job conditions, completion, payment exceptions, and accounting reconciliation. Each handoff should retain the source record, the person who approved the change, unresolved exceptions, and the next accountable owner so another team member can continue without guessing.
Evaluation scenarios
- Normal case: complete proposed turf boundary produces operator-reviewed areas that can feed pricing.
- Correction case: an operator changes an assumption before release.
- Exception case: missing information stops the workflow instead of guessing.
- Audit case: a manager can identify who approved the output and what changed.