Describe the intended people, product task and desired output. Use high-level information rather than records or credentials.
What to prepare
The task and intended users
Named project and technical contacts
What to expect
An initial requirements conversation.
02Agree the scope
Define included work, required inputs, responsibilities and acceptance checks. Establish product and partner readiness before promising delivery.
What to prepare
Access and dependency requirements
Data ownership and content rights
What to expect
A proposed scope with assumptions and exclusions.
03Review the proposal
Confirm deliverables, commercial terms, dates, third-party costs and any support arrangements in a written proposal.
What to prepare
The decision-maker and approval process
Questions about scope or commercial terms
What to expect
A quotation for review; the website does not set prices or confirm capacity.
04Test the agreed work
Use the agreed test environment and acceptance tasks. Record issues, exceptions and changes before accepting the handover.
What to prepare
Authorised test data and reviewers
Agreed acceptance criteria
What to expect
A review record and an agreed list of outstanding items.
05Complete the handover
Confirm the agreed documentation, team guidance and responsibility for later changes. Any continuing support is separately scoped.
What to prepare
Named administrators and support contacts
Approval of the agreed deliverables
What to expect
The agreed outputs and handover record.
Commercial terms are agreed in writing.
The proposal should state the included work, exclusions, required inputs, acceptance process, fees, third-party costs, dates and any continuing support. Nothing on this website constitutes an accepted quotation, purchase or clinical suitability decision.
