THE DIRECT ANSWER

Carry the accepted equipment specification, installation inclusions and site assumptions into a controlled job record. Separate the replacement equipment from labour, disposal and optional work so dispatch can distinguish what was sold from what remains uncertain. Require a named owner to approve changes before they affect purchasing or billing.

Understand the decision

A rooftop replacement can involve a purchaser who never attends the site, restricted access hours and equipment choices that change after a survey. The handoff needs the latest accepted revision and practical access information, with specialist technical requirements retained in their approved documents.

Work through the requirements

  1. Identify the accepted equipment revision.
  2. Separate optional work from committed scope.
  3. Review site access with dispatch.
Information to bring to the review
Record or decisionWhy it matters
Accepted estimateDefines equipment and commercial inclusions.
Site briefRecords access and contact responsibilities.
Change registerPreserves later approvals and exclusions.
TRY THIS WITH YOUR TEAM

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.

0 of 3 marked

Watch for this failure

A copied quote attachment can become stale while technicians work from newer messages. Keep one accepted scope reference and require the delivery owner to check it whenever equipment, access or commercial assumptions change.

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 guide
FROM REQUIREMENTS TO A REAL SCOPE

Bring your workflow to the conversation.

Discuss requirements for HVAC contractors 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: helpdesk after-sales workflows ↗Odoo 19: sales quotations and invoicing methods ↗