Separate recurring maintenance obligations from one-time installation and customer-requested extras. Define the property areas, expected visit pattern and included materials before creating crew work. Preserve exceptions such as customer-supplied plants or excluded disposal so a familiar site does not encourage staff to treat every request as part of the agreement.
Understand the decision
A commercial property can include lawn areas, planted beds and irrigation-related tasks with different frequencies. The customer may approve additional work during the season. Crews need concise instructions that preserve those boundaries while the office retains the accepted commercial terms and the record of approved changes.
Work through the requirements
- Map property areas and included work.
- Separate seasonal visits from installations.
- Record who approves requested extras.
| Record or decision | Why it matters |
|---|---|
| Property scope | Defines areas, frequencies and exclusions. |
| Seasonal agreement | Explains the accepted service boundary. |
| Extra-work approval | Connects additional tasks to customer decisions. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Repeating a generic task for every property can hide differences in the sold service. Keep area-specific scope and exclusions accessible, and review customer requests before allowing them to expand the recurring agreement informally.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Landscaping businesses in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: field service materials and warehouse configuration ↗Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗