FAQ
The big yard questions, answered plainly.
These answers keep the example useful while staying careful about scheduling, pricing, chemicals, irrigation, safety, and property boundaries.
Common questions.
This FAQ uses careful language suitable for a landscaping company example.
Can this example promise exact landscaping prices?
No. The packages are demo starting points. Real pricing depends on property size, route fit, access, materials, weather, and reviewed risk items.
What photos are helpful?
Front and back yard views, beds, turf symptoms, gates, parking, irrigation heads, slopes, debris piles, and material areas are useful when safe to capture.
How are irrigation concerns handled?
The form captures symptoms such as dry patches, overspray, broken heads, timer issues, and suspected leaks. Damage, repair, or safety conclusions should be reviewed by a qualified person.
Can the form approve chemical or pesticide work?
No. Chemical, pesticide, fertilizer, environmental, safety, and compliance questions are flagged for human review.
Why does route zone matter?
Recurring landscaping depends on crew routes, cadence, parking, access, and timing. Route fit should be confirmed before promising dates.
Is this static-deployable?
Yes. The example content root can validate and build into a static artifact suitable for S3 and CloudFront handoff.
Still deciding what to request?
Start with the service lane and photos. The rest can be shaped during review.