Delivery Policy
How delivery windows are calculated, what pauses the clock, how feedback and approval work, what happens at launch, and what a delivery does not include.
- Document reference
- ND-LGL-002
- Last reviewed
1. How a delivery window is calculated
Every package states a delivery window in working days: five to seven working days for a Landing Page, seven to twelve for a Starter Website, twelve to twenty for a Business Website, fifteen to twenty-five for an E-commerce Website, and a window scoped during discovery for a Premium Custom build.
- A working day is Monday to Friday, excluding public holidays observed in Pakistan. Saturdays and Sundays are not counted unless we agree otherwise in writing.
- The clock starts on the first working day after the deposit has cleared and discovery can begin. It does not start while we are waiting for payment to land.
- The window covers design, development, testing and launch preparation on our side. It assumes a client who responds as described in section 3.
- A window is a considered estimate, not a guarantee of a particular calendar date. Where we can see a date moving, we will tell you the same day rather than on the due date.
If the scope changes in a way that materially affects the work, we issue a revised window in writing alongside the revised quotation. Both are approved before the change starts.
2. What pauses the clock
A delivery window is a shared commitment, so it stops whenever the next step genuinely depends on somebody else. We will tell you when a pause starts and again when it ends. Time spent paused is added back to the window, day for day.
- Waiting for your feedback or your written approval of a deliverable.
- Waiting for content, images, copy, product data, brand assets or access to existing systems.
- Waiting for access to third-party accounts, such as a registrar, hosting, content system, analytics or gateway.
- Waiting for a decision that only you can make, including decisions on scope and cost.
- Waiting for a third-party service to complete an action, such as domain verification, DNS propagation or merchant account approval.
- Working on anything that turns out to sit outside the agreed scope.
- Any event outside our reasonable control, which is treated under the liability terms in the Service Agreement.
3. Feedback and approval
We send one consolidated feedback request per deliverable, so you always know what is being asked of you and by when. Please reply within three working days with one consolidated set of changes, and we will acknowledge it and confirm what we are changing and what we are not.
Written approval of a specific deliverable is what counts as approval. An email that says the design or the copy is approved, against a named deliverable, is what unlocks the next milestone and starts the next stage. We will act on a decision given in a meeting or a call, but we will not record a milestone as approved on your behalf, because it affects your invoice and your launch date.
- If we have not heard back within five working days of a feedback request, we send a follow-up.
- If there is still no response after ten working days, the project pauses and the delivery window stops until you reply. We will not proceed on your behalf, and we will not assume approval.
- Approval of the design stage unlocks the design milestone payment and the start of development.
- Approval of the final review unlocks the launch, which is explained in section 5.
4. When a delay comes from your side
If a stage is delayed by something we are waiting on, the delivery date moves by the same number of working days. That is not a penalty and it does not affect the price; it simply keeps the plan honest.
If a stage stays paused for more than ten working days, we will contact you and propose one of three options: restart the stage, close the project at that point, or move the remaining work to a new schedule. If none of those is agreed, we may close the project at that stage, hand over the work completed and paid for, and issue a final invoice for the completed work.
5. Launch and handover
Launch is the point at which your site goes live and the work becomes yours. The steps are the same on every project, in this order.
- 01 Final review on the staging link, with a single consolidated list of any last fixes.
- 02 Your written approval to launch.
- 03 Deployment of the production build, and the DNS cutover that points your domain at it. We will give you a checklist to make the change yourself if you would rather own that step.
- 04 Verification: pages loading, forms submitting, redirects resolving, analytics recording, SSL active, and the core journeys working end to end.
- 05 Handover: repository access, content system admin access, domain and hosting accounts in your name, the documentation, and a training session.
- 06 Final invoice issued. The post-launch support window starts on the launch date.
Launch requires four things from you: the final milestone payment cleared, access to the domain, final content approval, and any payment or merchant accounts approved by the provider. Where a provider takes time to approve an account, that wait is treated as a pause rather than a delay caused by us.
6. What a delivery does not include
It is easier to say this plainly than to let it surface later. A delivery covers the scope in your quotation. The following are separate.
- Hosting and domain costs. These are third-party charges billed separately, at cost, and are described in the Payment Policy.
- Writing the content. We can write it, as a quoted add-on, but it is not included in the build fee.
- Photography, video, product imagery and stock media.
- Paid plugins, fonts, stock licences and commercial usage rights.
- Sending email or SMS campaigns, paid advertising, and any marketing activity.
- Native iOS or Android applications.
- Search-engine ranking. We set up the technical foundations; we do not control what any search engine does with them afterwards.
- Ongoing updates, backups, security patching and content changes once the support window has closed, which are available as a maintenance plan.
- New pages, new sections or a second language added after launch, which are quoted as additional work.
7. Changing the scope mid-project
Change requests are priced and scheduled in writing before they begin. A change that touches the architecture, the content model or the number of pages gets a revised delivery window, not a hopeful one.
If a change means the original quotation no longer describes the project, we reissue the quotation with the revised price and, where relevant, the revised milestone split. Work on the change does not begin until you have accepted it.
8. Support after launch
Every package carries a post-launch support window, and the length is stated on your quotation: thirty days for the Starter Website, forty-five days for the Business Website and the E-commerce Website, and a bespoke arrangement for a Premium Custom build. The Landing Page package carries no support window.
Support means fixing defects in what we delivered: a broken layout, a form that does not submit, a link that goes nowhere, an error in a page, a problem on a device we did not test on. It does not mean new features, new content, content edits, or a problem caused by a third-party provider or by somebody else editing the site.
After the window closes, we still answer you. Anything beyond the window is quoted as ongoing maintenance, and we will tell you honestly if it is not worth doing.