THE DIRECT ANSWER

Preserve the original booking and record the approved change to date, participant or delivery format. Review instructor, venue and material commitments separately from the customer's charge or credit. Keep the remaining delivery obligation visible so a postponed session does not appear completed simply because its initial calendar date has passed.

Understand the decision

A customer may replace an attendee shortly before delivery, while another cohort must move because minimum participation is not reached. The commercial consequences can differ by agreement. The workflow should show the accepted decision and affected resources without assuming a universal cancellation or refund rule.

Work through the requirements

  1. Classify the requested booking change.
  2. Review customer and supplier consequences separately.
  3. Update the remaining delivery obligation.
Information to bring to the review
Record or decisionWhy it matters
Change requestPreserves original and proposed booking details.
Resource commitmentShows affected instructor and venue obligations.
Commercial decisionRecords approved charge, credit or rescheduling treatment.
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

Deleting a cancelled calendar entry can erase obligations to both customers and suppliers. Preserve the change decision and remaining commitments, and have finance review each agreement before applying a charge, credit or replacement session.

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 Training providers 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: sales quotations and invoicing methods ↗Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗