Hypothetical example
Put the decision in context.
An integration shows data in a demo but has no agreed failure handling. Define fields, errors and reconciliation before accepting its scope.
Take these points into your brief.
Use this checklist to record what is agreed and what still needs confirmation.
- Build and CMS scope
- Integration behaviour and failure handling
- Migration and recurring services
For each item, keep the requirement, the supporting file or observation, and the person responsible for confirming it together.
Compare scope and costs: your next step
Ask each supplier to respond to the same written scope, with inclusions, exclusions and optional work identified. Keep one-time work separate from recurring charges and third-party costs. Where a price depends on inspection or eligibility, record that dependency. Compare the total agreed work and responsibilities before choosing a proposal; the lowest headline figure may describe a different deliverable.
Sources and further reading
Source review: 11 September 2026. Confirm current requirements for your application. Platform features, eligibility and policies can change; check the requirements for your business and implementation.
