Project Delivery and Revision Policy
Last updated: July 13, 2026
This Project Delivery and Revision Policy explains how Xylentor Systems delivers completed work, how we handle reviews and revisions, and what you can expect at each stage of a project. Clear delivery expectations are part of how we keep engagements calm and predictable, so this policy sets out the practical rhythm of starting, reviewing, and finalizing your work.
01From proposal to kickoff
Every project begins with a written proposal or blueprint that describes the deliverables, the estimated timeline, and the agreed price. Once you accept the proposal and any initial payment is arranged, we schedule the work and confirm the information and access we need to begin.
02Delivery timelines
We provide an estimated timeline in each proposal. These estimates are made in good faith based on the agreed scope. Timelines can be affected by how quickly information and access are provided, by the responsiveness of feedback, and by the behaviour of any third-party platforms involved. If a timeline needs to shift, we will let you know promptly and explain why.
03How deliverables are handed over
Deliverables are provided digitally. Depending on the service, this may include a configured workspace, an organized file structure, a workflow diagram, a no-code automation, and written instructions. We aim to hand over work in a form that is easy to understand and easy to maintain after the project ends.
- Written instructions or a short guide accompany most deliverables.
- Where helpful, we include a brief walkthrough so your team feels confident using the new setup.
- All deliverables are handed over through your own accounts and tools wherever possible.
04Review period
After delivery, you have a review period, stated in your proposal, to check the work against what was agreed and to raise any concerns. We encourage you to review deliverables promptly so that any adjustments can be made while the details are still fresh for everyone.
05Revisions included
Each project includes a reasonable number of revisions to correct items that do not match the agreed scope or to refine details within that scope. The specific number of included revision rounds is noted in your proposal. Revisions are intended to align the deliverable with what was agreed, not to introduce new goals that were not part of the original engagement.
06Changes beyond the agreed scope
If, during a project or its review, you would like to add work that falls outside the original scope, we welcome it. Such additions are treated as new work and are quoted separately, so that the original project stays clear and the new work is priced fairly. This keeps expectations transparent and avoids surprises.
07Approval and completion
A project is considered complete when the deliverables have been handed over and either approved by you or the review period has passed without requested changes. On completion, ownership of the materials prepared for you transfers as described in our Intellectual Property Policy, subject to payment of the corresponding fees.
08Client responsibilities during delivery
Timely delivery depends partly on you. Providing prompt access, clear answers, and focused feedback helps us keep your project on schedule and ensures the final result closely fits your needs.
- Respond to questions and access requests without unnecessary delay.
- Consolidate feedback so revisions can be made efficiently.
- Confirm approval when a deliverable meets your expectations.
09Changes to this policy
We may update this Project Delivery and Revision Policy over time. The date at the top of this page shows the latest revision, and the version in effect when you accept a proposal applies to that project.
Questions about this policy?
If you have a question about how a specific deliverable was prepared or how revisions apply, contact us using the details below.