Cancellation & refunds

1.1Either party, by written notice

You may end an engagement at any time by telling us in writing. So may we — and if we ever do, you will hear the reason and get a handover of whatever exists at that point. Email is writing; a passing remark on a call is not.

1.2What happens on the day notice arrives

Work stops at an agreed point rather than mid-edit, we reconcile what has been completed, and a final invoice follows. Nothing new is started after notice unless you ask for it in writing.

2.1Work completed to the termination date

Work performed up to the termination date is billed pro-rata against the affected milestone. The reconciliation is itemised: what was completed, and what share of the milestone it represents.

2.2Milestones already invoiced

A milestone that has already been invoiced remains payable in full, whether or not it has been paid at the point of termination.

3.1Non-refundable, and what it paid for

4.1Payments made are non-refundable

Payments already made are not refunded. What you have paid for, you keep — see section 5 — and what you have not yet been invoiced for, you will not be.

4.2Where a defect is the reason

If you are cancelling because something in scope does not work, that is a defect, and the answer is that we fix it under the warranty terms rather than that you pay for something broken. Raise it as a defect first; the fix is faster than the cancellation.

5.1Released once the final invoice is settled

Everything completed and paid for is released to you: the repository as it stands, whatever documentation exists at that point, and the configuration needed to run it. Partial work is handed over as partial work, described honestly rather than presented as finished.

5.2IP follows the same rule as the terms

Formal assignment of the deliverables completes on full payment for them, exactly as clause 13.2 of the terms of service says. Termination does not change the rule; it only fixes the amount.

5.3Our access ends too

Every credential, key and account we hold on your systems is revoked at the same time, and listed so you can verify it. That happens on termination, not only on a successful completion.

6.1A pause you asked for

Tell us the project needs to stop for a while and we will agree a resumption point. Work already completed is invoiced at the pause; the remaining milestones keep their prices for the validity period on your quotation, and may be re-quoted after it.

6.2A pause caused by an unpaid invoice

An unpaid invoice may pause the engagement until it is settled, and the timeline moves by at least the length of the pause. A pause is not a cancellation, and neither side has terminated anything by causing one.

6.3A delay on your side is not a cancellation

Waiting on your approval, your access grant or your API extends the timeline automatically and without penalty. It does not cancel anything, it does not cost you extra, and it does not need a notice.

6.4Cancelling a monthly retainer

A monthly retainer ends by written notice from either side, exactly as section 1 describes. The notice period that applies to yours is the one stated in your retainer agreement.

7.1One email

Write to contact@awiztec.com saying that you want to end the engagement, and name the project. You will get an acknowledgement, an agreed stopping point, the reconciliation, and the final invoice. No form, no retention call, and nobody will try to talk you out of it.