FAQ

Do I need permits, approvals or compliance checks before website development starts?

Most standard business websites do not require a formal permit before development starts, but approvals and compliance checks still matter. Dobble typically needs approved content, branding, access credentials, domain details and stakeholder sign-off. Legal, privacy, industry or regulatory requirements should be reviewed by the client’s advisers before launch, especially for healthcare, legal, finance or e-commerce websites.

Most standard business websites do not require a government permit before development can begin, but that does not mean approvals and compliance can be ignored. A website is a public business asset, so the information it displays, the data it collects, the third-party systems it connects to and the way it represents your business all need to be considered before launch.

Dobble’s website development process is structured to reduce risk before work goes live. This usually starts with an initial consultation, proposal acceptance, a client questionnaire, collection of required assets and access credentials, and technical review where applicable. From there, Dobble plans the site architecture, conversion pathways, technical foundations and development approach before building in a secure staging environment.

For most projects, the main approvals are business approvals rather than formal permits. These may include approval of your logo and brand assets, written content, service descriptions, product information, imagery, calls-to-action, privacy or terms links, contact details, location information and any claims made on the website. If multiple directors, managers or stakeholders need to approve content, it is best to identify them early so feedback does not delay the project.

Clients are also responsible for ensuring they have the right to use the material they supply. This includes logos, photographs, written content, videos, product data, testimonials, trade marks and any third-party assets. Dobble can work with supplied content and can provide professional website copywriting where it aligns with the project, but it cannot verify every legal right or regulatory claim unless that has been specifically reviewed by the client’s qualified advisers.

Compliance considerations vary by industry. A trade business website may mainly need accurate service descriptions, correct contact details and safe use of project images. A healthcare, legal, financial, e-commerce or regulated-industry website may need stricter review around professional claims, disclaimers, privacy obligations, advertising rules, payment terms, product statements or industry-specific requirements. Dobble does not provide legal advice, so clients should obtain independent legal, regulatory or compliance advice where required.

Privacy and data collection should also be reviewed before launch. If a website includes contact forms, enquiry forms, analytics, advertising tracking, newsletter sign-ups, customer accounts, bookings or e-commerce functionality, the business should consider whether its Privacy Policy, Terms and Conditions, cookie notices or other legal documents are current and suitable. Dobble can implement supplied policies and technical configurations, but any policy summary or legal wording should be checked against the full legal documents.

Technical approvals are also important. Dobble may need access to domains, DNS, hosting, email, analytics, payment gateways, CRMs, booking platforms or other third-party systems. Before migration or launch, Dobble plans changes carefully, takes backups where possible, prepares the new environment and coordinates DNS updates to minimise disruption. Temporary interruptions can still occur because DNS propagation, third-party providers and internet caching are outside Dobble’s complete control.

For websites built on Dobble’s proprietary Genesis CMS, clients may request content management access, with permissions assigned at Dobble’s discretion to protect website integrity, security and functionality. Laravel is used for larger bespoke systems, business applications and complex integrations. In both cases, development is tested in a secure staging environment before deployment, with client review and approval before launch where possible.

Before your website goes live, Dobble will typically seek confirmation that the required content, design direction, functionality and staging website have been reviewed and approved. This sign-off helps ensure the site reflects the agreed scope and is ready for deployment. Any legal, regulatory, privacy, accessibility or industry compliance obligations remain the client’s responsibility unless a specific adviser or agreement states otherwise.

If you are unsure what approvals your project may need, Dobble can help identify the practical website, technical and content items that should be prepared before development begins. For legal, regulatory or industry-specific compliance questions, you should seek advice from the appropriate professional before launch.

Ready to start?

Let's build something that works for your business.

Get a tailored quote or send us your question — the team is here to help.

Get started Ask a question

Keep exploring

Tap to call
Enquire now

Ask Dobble

Ask a question

Send us your question and the Dobble team will get back to you.

Prefer to talk to us directly?

Get in touch

Contact us

Tell us about your project and the Dobble team will be in touch shortly.

Prefer to talk to us directly?