What customers should expect to receive
Exact artefacts depend on the job, but the objective is straightforward: after agreed testing and final payment, the customer should leave with the material needed to understand what was delivered, how it runs, how it can be supported, and how it can be handed over cleanly.
- Scope summary, assumptions, and any approved variations
- Repository or file structure used for the project where applicable
- Source or configuration repositories where applicable
- Design files and manufacturing data where relevant to the engagement
- As-built notes, diagrams, labels, or network maps as appropriate
- Access and credential handover steps for customer-owned systems
- Exit strategy documentation as part of the delivery pack
- Outstanding risks, dependencies, and recommended next actions
Support after delivery
Support tiers are optional. They are mainly for environments where IATRT continues to manage domains, hosting, ongoing hardware support, monitoring, or similar operational responsibilities. End users can request support directly from IATRT where the selected support tier allows it.
Customers can also return later and purchase support after delivery, provided the delivered system remains substantially as handed over and has not already been taken over by another maintainer.
Frequently Asked
When does IP transfer happen?
Initial project scope determines cost. After agreed testing is complete and final payment is settled, final handoff is completed with the project documentation pack. If IP assignment or transfer is part of the project, it happens at that handoff or under the already-agreed contract position. Third-party licensed components keep their own licence conditions.
What is included in the handoff pack?
It depends on the project, but the intent is straightforward: clear repo or file structure, relevant source and design artefacts, as-built notes, access handover information, and an exit strategy document so the customer is not left guessing how the system should be maintained or transferred later.
Are support tiers mandatory after delivery?
No. Support tiers are optional. They are mainly used where IATRT continues to manage hosting, domains, ongoing hardware support, or similar operational work. End users can request support directly from IATRT where the selected support tier includes it, but customers can pause or leave at any time and there are no lock-in contract periods.
Can we add support later or move to another maintainer?
Yes. The delivery model is meant to allow maintenance and migration, not trap clients. Support can be added later if the delivered system remains substantially as handed over and has not already moved to another maintainer. Clients can also transition support to an internal team or another provider when needed.
How do you handle underestimated scope or variations?
The stated approach is to surface the change early, explain the technical reason, and obtain approval before substantial out-of-scope work continues. That keeps the commercial mechanism visible instead of turning it into a surprise after the fact.