CUSTOM TECHNOLOGY / DELIVERY
From build and release
to handover and support.
Test the application against the task it needs to perform, deploy it and give the responsible team the code, configuration and operating knowledge agreed for the engagement.
RELEASE ACCEPTANCE
Test the application through the user’s task.
| Area | Example acceptance evidence |
|---|---|
| Data path | The selected source and period appear correctly in the application, including missing-input behaviour. |
| Analytical result | The returned calculation or finding can be checked against the agreed evidence and method. |
| User journey | The intended user can start, inspect, review and complete the task with the correct access. |
| System handoff | The destination receives the right result, and retries do not silently duplicate an action. |
| Operation | The team can see a failed step, identify its owner and use the documented recovery path. |
BUSINESS MEASUREMENT
Measure the difference in the day-to-day process.
For a reporting application, measure the time to an approved report and the review effort involved. For an integration, check whether the right data reaches the process and how the team handles exceptions.
Agree the baseline, target, measurement period and owner at the start. Technical acceptance confirms that the release works as specified; use in the business establishes whether it delivers the expected improvement.
HANDOVER
Agree the handover before the release.
| Deliverable | What it covers |
|---|---|
| Implementation and configuration | The agreed custom code, deployment setup and environment requirements. |
| System map | Services, data paths, external dependencies and access responsibilities. |
| Operating documentation | Monitoring, source refresh, incident diagnosis and recovery procedures. |
| Change process | How a subsequent source, prompt, workflow or software release is validated. |
| Ownership and support | The allocation of code rights, platform licences, infrastructure and ongoing support in the contract. |
AFTER RELEASE
Choose the support your team needs.
An engagement can finish with a handover or include ongoing support and development. We agree who maintains the application, source connections and platform dependencies, along with the service expectations.
Discuss the delivery requirementsPLATFORM AND CUSTOM SOFTWARE
Document how the foundation and application evolve.
The system map identifies reused Evidence OS services, customer-specific extensions and dependencies on other enterprise platforms. A change to an agent, workflow or data source should have an agreed validation and release path.
The contract sets out custom-code rights, platform licensing, deployment and support separately. Customer ownership of an application and an ongoing Whiteboxx operating service are distinct arrangements.
See the extension architecture