For customers
Start with the kind of outdoor work.
Customers should be able to choose maintenance, landscaping, patio or paving, fencing, or drainage before answering detail questions.
Garden and outdoor work
Garden work needs branches, not one vague form.
Gardening maintenance and landscaping projects sound related, but they need different questions. ScopeBeam should keep them under one outdoor group while routing each job into the right branch.
For tradespersons
Do not treat a garden tidy-up like a patio build.
A tidy-up request needs frequency and waste questions. A landscaping or paving job needs measurements, levels, materials, groundwork, access, and risk flags.
Template branches
Keep related outdoor work together without forcing one form to fit every job.
Live intake branches
These branches have structured customer forms now.
Candidate branches
These stay separate so outdoor jobs can route correctly as their forms are shaped.
Landscaping project
Candidate
Project work needs design intent, levels, materials, groundwork, access, and site constraints.
Fencing
Candidate
Fence work needs run length, height, posts, boundary notes, disposal, and access.
Drainage
Candidate
Drainage needs symptoms, standing water, falls, existing gullies, and urgency without guessing the fix.
What it captures
Useful job details without turning the customer into a surveyor.
Outdoor parent category before detailed trade questions
Gardening maintenance, landscaping project, patio/paving, fencing, and drainage branches
Shared details like access, parking, photos, garden size, waste, and customer expectations
Separate future route for tree and hedge work if it needs specialist safety wording
Product shape
Template-specific, but still one durable platform.
Gardening is not a subset of landscaping; both sit under Garden & outdoor.
Patios, drainage, fencing, retaining walls, and groundwork should not be bundled into ordinary maintenance by default.