Services / 04
Service 04 · At project end
Acceptance and handover planning
Agree in advance how you will verify that the delivered system does what was requested.
Helps you decide when a system can be accepted, what the vendor must deliver, and who takes over its management.


3deliverables
Typical situations
01
The vendor says the project is finished but there is no internal agreement.
02
You are about to sign a contract and want written acceptance criteria.
03
The person who ran the project is leaving and documentation is scattered.
You
What you provide
- Requirements or the relevant parts of the vendor contract
- List of key users who will take part in acceptance
- Documentation already delivered by the vendor
Us
What we do
- 1.Translation of requirements into test cases
- 2.Definition of acceptance criteria and defect severity
- 3.List of documentation to receive at handover
- 4.Definition of post-release management roles
What you receive
- Acceptance plan with cases, dummy test data and expected results
- Acceptance criteria and defect classification
- Handover checklist (documents, access, contacts)
How the work is checked
- Every mandatory requirement is covered by at least one test case
- Acceptance criteria are agreed in writing before execution
- One written review round included
Not included
- Software development, configuration or go-live of the systems
- Hosting, ongoing operations or support with guaranteed response times
- Security certifications or compliance audits
- Running the tests or signing acceptance on the client's behalf
Quote factors
Written quote on request, no list prices.
- Number of requirements to cover
- Number of user roles
- State of existing documentation
Other services
Want a quote for this service?
The form pre-selects this service. Describe systems, goal and timing.



