Acceptance matrix
For each requirement, record the corresponding project, checking method, result, and owner, distinguishing verification methods such as inspection, analysis, demonstration, and testing.
Acceptance & Handover
Acceptance relies on reproducibility and checklists, rather than an improvised live demonstration
Hand over everything needed to open, build, and rerun the project, with ownership clarified.
Answer
What we provide
New Horizon uses a checklist for acceptance and handover: are all agreed artifacts present, can critical workflows be reproduced, and are documentation and source-code deliverables complete within scope? After acceptance, freeze the baseline and complete sign-off. Further development requires a separate scope.
Last updated: 2026-10-12 · New Horizon Digital Outsourcing Team
Key points
- 01Checklist verification
- 02Rerun critical workflows
- 03Hand over source code and assets as agreed
Outputs of this step
- 01Acceptance checklist
- 02Reproduction guide
- 03Baseline package
- 04Sign-off record
Path
How it works
- 01 Self-check and package
- 02 Client reproduction
- 03 Issue closure
- 04 Sign off and archive
Frequently asked questions
What happens if acceptance fails?
Resolve each issue against the scope statement and acceptance criteria. Handle out-of-scope requirements as separate work, rather than including them in this round of rework.
Other Delivery Approach topics
Engineering Notes
Complete acceptance against requirements, evidence, and the engineering baseline
Issue closure
Record the causes of deviations and corrective results. For unresolved items, state their impact and agreed handling. An overall acceptance statement must not conceal unverified critical workflows.
Continued usability
Organize version inventories, startup steps, configuration and maintenance instructions, and complete a rerun in the receiving environment. Use the same version identifier for documentation and delivered software.
Have the Receiving Team Complete a Workflow Independently
At handover, the receiving team should open the frozen model, locate a requirement, inspect its evidence, and regenerate an agreed report. For collaborative environments, also check permissions, updates, and recovery. Record actual results and failures, and transfer credentials through the agreed secure channel rather than public reports.
Include the Checking Tool in Acceptance
Deliver minimal models with known expected outcomes to check rule execution, unlinking, and element deletion. The recipient should check, undo, save, and reopen a copy while inspecting consistency across views. Zero findings or a normal-looking UI alone do not establish acceptance.
Deliver Loss Registers and Execution Preconditions
When handing over models or requirements data, include exchange mappings, unsupported content, and recipient reconciliation records. For executable behavior, add initial context, input events, and stop conditions. The recipient should independently check agreed samples, preserving the status and reason for unverified areas rather than treating opened files or playing animations as acceptance.
Further Reading and Technical References
Related standards and technical documentation for solution selection and implementation.
Align the collaboration through Acceptance and Handover
Describe your phase objectives and constraints without classified details, and we will provide scope recommendations.