Delivery policy
1. Intro
This Delivery Policy explains how South Digital Ltd (“South Digital”, “we”, “us”, “our”) delivers its services and project work.
It should be read alongside our Terms and Conditions, Privacy Policy, and Refund / Cancellation Policy.
We provide digital services only. There is no physical shipping.
1. Intro
This Delivery Policy explains how South Digital Ltd (“South Digital”, “we”, “us”, “our”) delivers its services and project work.
It should be read alongside our Terms and Conditions, Privacy Policy, and Refund / Cancellation Policy.
We provide digital services only. There is no physical shipping.
1. Intro
This Delivery Policy explains how South Digital Ltd (“South Digital”, “we”, “us”, “our”) delivers its services and project work.
It should be read alongside our Terms and Conditions, Privacy Policy, and Refund / Cancellation Policy.
We provide digital services only. There is no physical shipping.
2. Who we are
South Digital Ltd is a web design and development studio.
Legal entity: South Digital Ltd
Registered in: United Kingdom
Registered office: 1 Pirelli Way, Eastleigh, England, SO50 5GE
Email: hello@south.digital
2. Who we are
South Digital Ltd is a web design and development studio.
Legal entity: South Digital Ltd
Registered in: United Kingdom
Registered office: 1 Pirelli Way, Eastleigh, England, SO50 5GE
Email: hello@south.digital
2. Who we are
South Digital Ltd is a web design and development studio.
Legal entity: South Digital Ltd
Registered in: United Kingdom
Registered office: 1 Pirelli Way, Eastleigh, England, SO50 5GE
Email: hello@south.digital
3. What “delivery” means for our services
Because we work digitally, “delivery” usually means one or more of the following:
Access to a live or staging website (for example, a Webflow, Framer, or WordPress install)
Access to design files (for example, Figma links)
Access to documents and assets (for example, copy docs, site maps, content plans, or exports)
Access to automation and AI flows (for example, in Zapier, Make, or other tools)
Access to project documentation (for example, notes, diagrams, or Loom walkthroughs)
The exact form of delivery will be set out in your proposal, scope of work, or agreement.
We do not physically ship any goods.
3. What “delivery” means for our services
Because we work digitally, “delivery” usually means one or more of the following:
Access to a live or staging website (for example, a Webflow, Framer, or WordPress install)
Access to design files (for example, Figma links)
Access to documents and assets (for example, copy docs, site maps, content plans, or exports)
Access to automation and AI flows (for example, in Zapier, Make, or other tools)
Access to project documentation (for example, notes, diagrams, or Loom walkthroughs)
The exact form of delivery will be set out in your proposal, scope of work, or agreement.
We do not physically ship any goods.
3. What “delivery” means for our services
Because we work digitally, “delivery” usually means one or more of the following:
Access to a live or staging website (for example, a Webflow, Framer, or WordPress install)
Access to design files (for example, Figma links)
Access to documents and assets (for example, copy docs, site maps, content plans, or exports)
Access to automation and AI flows (for example, in Zapier, Make, or other tools)
Access to project documentation (for example, notes, diagrams, or Loom walkthroughs)
The exact form of delivery will be set out in your proposal, scope of work, or agreement.
We do not physically ship any goods.
4. How we deliver project work
4.1 Design work
Design deliverables are typically provided as:
Figma files or links
Prototypes or previews
Exports or screenshots where needed for reference
You will usually be invited into the design file for reviews and comments.
4.2 Development work
Development deliverables are usually provided as:
Your finished website (in your or our account, depending on the agreement)
A staging environment for review and testing
A live deployment to your chosen domain, once approved
We will agree whether projects are created and hosted in your accounts or ours, and how and when ownership is transferred.
4.3 Copywriting and SEO work
Copy and SEO work is typically delivered as:
Documents or spreadsheets (for example, Google Docs or Sheets)
Updates made directly in your CMS, where agreed
Short summaries, audits, or recommendations in document format
We will clearly label drafts versus final versions.
3.4 AI and automation work
AI and automation deliverables are usually:
Flows or scenarios configured in your tools (for example, Zapier, Make, or similar)
Diagrams and notes that explain the flows
Configuration inside your website (for example, chat widgets, scripts, or integrations)
Where possible, we will give you access so you can see and manage these flows.
4. How we deliver project work
4.1 Design work
Design deliverables are typically provided as:
Figma files or links
Prototypes or previews
Exports or screenshots where needed for reference
You will usually be invited into the design file for reviews and comments.
4.2 Development work
Development deliverables are usually provided as:
Your finished website (in your or our account, depending on the agreement)
A staging environment for review and testing
A live deployment to your chosen domain, once approved
We will agree whether projects are created and hosted in your accounts or ours, and how and when ownership is transferred.
4.3 Copywriting and SEO work
Copy and SEO work is typically delivered as:
Documents or spreadsheets (for example, Google Docs or Sheets)
Updates made directly in your CMS, where agreed
Short summaries, audits, or recommendations in document format
We will clearly label drafts versus final versions.
3.4 AI and automation work
AI and automation deliverables are usually:
Flows or scenarios configured in your tools (for example, Zapier, Make, or similar)
Diagrams and notes that explain the flows
Configuration inside your website (for example, chat widgets, scripts, or integrations)
Where possible, we will give you access so you can see and manage these flows.
4. How we deliver project work
4.1 Design work
Design deliverables are typically provided as:
Figma files or links
Prototypes or previews
Exports or screenshots where needed for reference
You will usually be invited into the design file for reviews and comments.
4.2 Development work
Development deliverables are usually provided as:
Your finished website (in your or our account, depending on the agreement)
A staging environment for review and testing
A live deployment to your chosen domain, once approved
We will agree whether projects are created and hosted in your accounts or ours, and how and when ownership is transferred.
4.3 Copywriting and SEO work
Copy and SEO work is typically delivered as:
Documents or spreadsheets (for example, Google Docs or Sheets)
Updates made directly in your CMS, where agreed
Short summaries, audits, or recommendations in document format
We will clearly label drafts versus final versions.
3.4 AI and automation work
AI and automation deliverables are usually:
Flows or scenarios configured in your tools (for example, Zapier, Make, or similar)
Diagrams and notes that explain the flows
Configuration inside your website (for example, chat widgets, scripts, or integrations)
Where possible, we will give you access so you can see and manage these flows.
5. Timelines and scheduling
5.1 Estimated timelines
Project start dates, milestone dates, and launch windows are agreed in advance and set out in your proposal or project plan.
These are estimates, not guarantees. They depend on:
The agreed scope
Timely feedback, approvals, and content from your side
No major unplanned changes
5.2 Delays
If delays arise due to factors outside our control (for example, platform issues, illness, or delayed feedback):
We will inform you as soon as reasonably possible
We will propose a revised timeline
If you delay feedback or content for an extended period, we may need to:
Replan the project schedule, and/or
Adjust fees if the scope or context has materially changed
5. Timelines and scheduling
5.1 Estimated timelines
Project start dates, milestone dates, and launch windows are agreed in advance and set out in your proposal or project plan.
These are estimates, not guarantees. They depend on:
The agreed scope
Timely feedback, approvals, and content from your side
No major unplanned changes
5.2 Delays
If delays arise due to factors outside our control (for example, platform issues, illness, or delayed feedback):
We will inform you as soon as reasonably possible
We will propose a revised timeline
If you delay feedback or content for an extended period, we may need to:
Replan the project schedule, and/or
Adjust fees if the scope or context has materially changed
5. Timelines and scheduling
5.1 Estimated timelines
Project start dates, milestone dates, and launch windows are agreed in advance and set out in your proposal or project plan.
These are estimates, not guarantees. They depend on:
The agreed scope
Timely feedback, approvals, and content from your side
No major unplanned changes
5.2 Delays
If delays arise due to factors outside our control (for example, platform issues, illness, or delayed feedback):
We will inform you as soon as reasonably possible
We will propose a revised timeline
If you delay feedback or content for an extended period, we may need to:
Replan the project schedule, and/or
Adjust fees if the scope or context has materially changed
6. Your responsibilities for delivery
To help us deliver work smoothly, you agree to:
Provide access to required tools and accounts (for example, hosting, DNS, Webflow/Framer/WordPress, email tools, CRMs)
Share content and assets (for example, copy, images, brand guidelines, legal text) that are your responsibility
Review and approve key milestones (for example, wireframes, designs, copy, staging builds) within agreed time frames
Confirm sign off when you are happy for us to proceed to the next stage or go live
Delays or missing inputs on your side may delay delivery.
6. Your responsibilities for delivery
To help us deliver work smoothly, you agree to:
Provide access to required tools and accounts (for example, hosting, DNS, Webflow/Framer/WordPress, email tools, CRMs)
Share content and assets (for example, copy, images, brand guidelines, legal text) that are your responsibility
Review and approve key milestones (for example, wireframes, designs, copy, staging builds) within agreed time frames
Confirm sign off when you are happy for us to proceed to the next stage or go live
Delays or missing inputs on your side may delay delivery.
6. Your responsibilities for delivery
To help us deliver work smoothly, you agree to:
Provide access to required tools and accounts (for example, hosting, DNS, Webflow/Framer/WordPress, email tools, CRMs)
Share content and assets (for example, copy, images, brand guidelines, legal text) that are your responsibility
Review and approve key milestones (for example, wireframes, designs, copy, staging builds) within agreed time frames
Confirm sign off when you are happy for us to proceed to the next stage or go live
Delays or missing inputs on your side may delay delivery.
7. Review, revisions, and acceptance
7.1 Review rounds
Most projects include one or more rounds of review and refinement. These will be set out in your proposal and may include:
Design review rounds
Copy review rounds
Development or staging review rounds
7.2 Sign off
Work is considered delivered and accepted when:
We have provided the agreed deliverables (for example, Figma file, staging URL, live site, documents), and
You have either:
Confirmed in writing (email is fine) that you are happy, or
Used the deliverables in a live environment without raising issues within a reasonable period
Once a stage is signed off, further changes may be treated as new work and quoted separately.
7.3 Bug fixes and small issues
If you find genuine bugs or errors in our work (for example, broken layout, non-working form) within a reasonable period after delivery or launch:
We will fix those issues as part of the original scope, within a fair window (for example, 30 days from go live, unless otherwise agreed)
This does not include new features, changes of mind, or scope creep
The exact bug fix period can be tailored in your proposal.
7. Review, revisions, and acceptance
7.1 Review rounds
Most projects include one or more rounds of review and refinement. These will be set out in your proposal and may include:
Design review rounds
Copy review rounds
Development or staging review rounds
7.2 Sign off
Work is considered delivered and accepted when:
We have provided the agreed deliverables (for example, Figma file, staging URL, live site, documents), and
You have either:
Confirmed in writing (email is fine) that you are happy, or
Used the deliverables in a live environment without raising issues within a reasonable period
Once a stage is signed off, further changes may be treated as new work and quoted separately.
7.3 Bug fixes and small issues
If you find genuine bugs or errors in our work (for example, broken layout, non-working form) within a reasonable period after delivery or launch:
We will fix those issues as part of the original scope, within a fair window (for example, 30 days from go live, unless otherwise agreed)
This does not include new features, changes of mind, or scope creep
The exact bug fix period can be tailored in your proposal.
7. Review, revisions, and acceptance
7.1 Review rounds
Most projects include one or more rounds of review and refinement. These will be set out in your proposal and may include:
Design review rounds
Copy review rounds
Development or staging review rounds
7.2 Sign off
Work is considered delivered and accepted when:
We have provided the agreed deliverables (for example, Figma file, staging URL, live site, documents), and
You have either:
Confirmed in writing (email is fine) that you are happy, or
Used the deliverables in a live environment without raising issues within a reasonable period
Once a stage is signed off, further changes may be treated as new work and quoted separately.
7.3 Bug fixes and small issues
If you find genuine bugs or errors in our work (for example, broken layout, non-working form) within a reasonable period after delivery or launch:
We will fix those issues as part of the original scope, within a fair window (for example, 30 days from go live, unless otherwise agreed)
This does not include new features, changes of mind, or scope creep
The exact bug fix period can be tailored in your proposal.
8. Launch and go live
Where we are responsible for launching a website or change:
We will agree a launch window with you
We will take reasonable steps to test before and after launch (for example, basic functionality, key pages, forms)
We may ask you to perform your own checks and confirm you are happy
You are ultimately responsible for:
The content that is live on your website (including legal and regulatory content)
Deciding when to launch and communicating any high risk or sensitive requirements
If you prefer to handle launch yourself, we will provide the necessary files, access, or instructions.
8. Launch and go live
Where we are responsible for launching a website or change:
We will agree a launch window with you
We will take reasonable steps to test before and after launch (for example, basic functionality, key pages, forms)
We may ask you to perform your own checks and confirm you are happy
You are ultimately responsible for:
The content that is live on your website (including legal and regulatory content)
Deciding when to launch and communicating any high risk or sensitive requirements
If you prefer to handle launch yourself, we will provide the necessary files, access, or instructions.
8. Launch and go live
Where we are responsible for launching a website or change:
We will agree a launch window with you
We will take reasonable steps to test before and after launch (for example, basic functionality, key pages, forms)
We may ask you to perform your own checks and confirm you are happy
You are ultimately responsible for:
The content that is live on your website (including legal and regulatory content)
Deciding when to launch and communicating any high risk or sensitive requirements
If you prefer to handle launch yourself, we will provide the necessary files, access, or instructions.
9. Ongoing services and maintenance delivery
For ongoing support (for example, maintenance, small tasks, or flexible hours):
We will agree how you submit requests (for example, email, task system, shared list)
We will agree typical response times or windows for small jobs
We will keep you updated on what has been done and what is in progress
Unless a formal SLA is in place, these arrangements are based on reasonable efforts and standard business hours.
9. Ongoing services and maintenance delivery
For ongoing support (for example, maintenance, small tasks, or flexible hours):
We will agree how you submit requests (for example, email, task system, shared list)
We will agree typical response times or windows for small jobs
We will keep you updated on what has been done and what is in progress
Unless a formal SLA is in place, these arrangements are based on reasonable efforts and standard business hours.
9. Ongoing services and maintenance delivery
For ongoing support (for example, maintenance, small tasks, or flexible hours):
We will agree how you submit requests (for example, email, task system, shared list)
We will agree typical response times or windows for small jobs
We will keep you updated on what has been done and what is in progress
Unless a formal SLA is in place, these arrangements are based on reasonable efforts and standard business hours.
10. Digital delivery only (no shipping)
We do not supply or ship physical products.
There are no shipping or postage charges
All delivery is via digital means (for example, links, logins, files, or access rights)
Any references to “delivery”, “dispatch”, or “completion” on invoices, proposals, or emails refer to digital project milestones or access being provided.
10. Digital delivery only (no shipping)
We do not supply or ship physical products.
There are no shipping or postage charges
All delivery is via digital means (for example, links, logins, files, or access rights)
Any references to “delivery”, “dispatch”, or “completion” on invoices, proposals, or emails refer to digital project milestones or access being provided.
10. Digital delivery only (no shipping)
We do not supply or ship physical products.
There are no shipping or postage charges
All delivery is via digital means (for example, links, logins, files, or access rights)
Any references to “delivery”, “dispatch”, or “completion” on invoices, proposals, or emails refer to digital project milestones or access being provided.
11. If you do not receive what you expect
If you believe that:
A deliverable has not been provided as agreed, or
Access to a site, file, or tool has not been correctly granted, or
There is a significant issue preventing you from using the work,
please contact us at hello@south.digital as soon as possible with:
Your name and company
The project or invoice reference (if available)
A short description of the problem
We will review and:
Clarify what has already been delivered
Fix genuine delivery issues where something is missing or misconfigured
Explain if a requested change is out of scope and needs new approval
Any refunds or credits will be handled under our Refund and Cancellation Policy and Terms and Conditions.
11. If you do not receive what you expect
If you believe that:
A deliverable has not been provided as agreed, or
Access to a site, file, or tool has not been correctly granted, or
There is a significant issue preventing you from using the work,
please contact us at hello@south.digital as soon as possible with:
Your name and company
The project or invoice reference (if available)
A short description of the problem
We will review and:
Clarify what has already been delivered
Fix genuine delivery issues where something is missing or misconfigured
Explain if a requested change is out of scope and needs new approval
Any refunds or credits will be handled under our Refund and Cancellation Policy and Terms and Conditions.
11. If you do not receive what you expect
If you believe that:
A deliverable has not been provided as agreed, or
Access to a site, file, or tool has not been correctly granted, or
There is a significant issue preventing you from using the work,
please contact us at hello@south.digital as soon as possible with:
Your name and company
The project or invoice reference (if available)
A short description of the problem
We will review and:
Clarify what has already been delivered
Fix genuine delivery issues where something is missing or misconfigured
Explain if a requested change is out of scope and needs new approval
Any refunds or credits will be handled under our Refund and Cancellation Policy and Terms and Conditions.
12. Changes to this delivery policy
We may update this Delivery Policy from time to time.
We may highlight significant changes on our website.
If you have an active project, we will normally apply the version of the policy in place at the time your proposal was accepted, unless we mutually agree otherwise.
12. Changes to this delivery policy
We may update this Delivery Policy from time to time.
We may highlight significant changes on our website.
If you have an active project, we will normally apply the version of the policy in place at the time your proposal was accepted, unless we mutually agree otherwise.
12. Changes to this delivery policy
We may update this Delivery Policy from time to time.
We may highlight significant changes on our website.
If you have an active project, we will normally apply the version of the policy in place at the time your proposal was accepted, unless we mutually agree otherwise.
13. Contact
If you have any questions about this Delivery Policy or how we handle delivery for your project, you can contact us at:
Email: hello@south.digital
13. Contact
If you have any questions about this Delivery Policy or how we handle delivery for your project, you can contact us at:
Email: hello@south.digital
13. Contact
If you have any questions about this Delivery Policy or how we handle delivery for your project, you can contact us at:
Email: hello@south.digital
Leading your website to success
Leading your website to success
Leading your website to success
South Digital is a web design and development agency based in the UK, partnering with teams across the US, UK, and beyond.
South Digital is a web design and development agency based in the UK, partnering with teams across the US, UK, and beyond.
South Digital is a web design and development agency based in the UK, partnering with teams across the US, UK, and beyond.