The Permit Is on the Critical Path: A UK Founder’s Six-Week Launch Countdown

Most launch plans have a tidy row of dependencies: copy, build, QA, press, waitlist. Then someone asks where the demo is actually happening, and the plan quietly grows a new branch. Permits are not paperwork that happens after the product is ready. They are part of the product’s route to market.

A pop-up demo in a shopping centre, a street-team handing out samples, a launch party with a DJ, a drone shot for the hero video — each one can trigger a different permission. None of them is exotic. All of them can slip if you treat them as admin.

The permit is a dependency, not a chore

Founders tend to plan launches in product time: sprints, QA cycles, staging environments. Councils plan in notice periods: working days, consultation windows, committee dates. Those clocks do not sync automatically. If your launch date is fixed and your permit date is not, the permit wins.

The practical fix is to put permissions on the same board as engineering. Give them an owner, a deadline and a status. A permit that is waiting on a council email is not a side quest. It is a blocker with a reference number.

What actually needs a permission slip?

The answer depends on where you are, what you are doing and who owns the land. But these are the usual suspects for UK launch activity.

• Pop-up demos and temporary events. A private venue still has its own rules. A council-owned square, park or pavement brings the council’s events team, highways team or licensing team into the room. Some sites need an event application weeks or months ahead.
• Street trading. Selling or sampling on a public street or market pitch usually needs a street trading licence or consent from the local authority. Rules vary by borough and council. Ask early, because the answer is often ‘yes, but not there’ or ‘yes, but not that day’.
• Food sampling. Free samples still count as food activity. Check whether your sampling needs food business registration, allergen information and a food safety plan. Many councils ask for registration at least 28 days before activity, so do not leave this to launch week.
• Amplified music and alcohol. A launch party with a DJ, a bar or a late finish may need a premises licence, a club premises certificate or a temporary event notice. A standard TEN normally needs to reach the council at least 10 working days before the event — which means your real deadline is earlier than the form says.
• Drone footage. Commercial drone work needs the right CAA operator and flyer requirements, landowner permission, and a check on local byelaws and privacy. Insurance matters too. A nice aerial shot of your launch queue is not worth an unplanned conversation with the regulator.

This is not legal advice. It is a prompt to ask your council, your venue and your insurer before the date is locked.

The six-week reverse planner

Work backwards from go-live. If your launch is in six weeks, this is the shape of the conversation.

Six weeks out: map the permissions

Write down every physical thing that happens around launch: the demo, the queue, the samples, the sound system, the camera crew, the goodie bags, the road crossing. For each one, ask: whose land is it, who needs to approve it, and what proof will they want?

Call the council’s events or licensing team and describe the activity in plain English. Do not ask ‘do I need a licence?’ Ask ‘I am planning X on Y date at Z location — what do you need from me and when?’ That question gets a much more useful answer.

Check your insurance. Public liability cover is frequently requested by venues and councils; £5m is a common starting point, but read the requirement rather than guessing. If you have staff or contractors, check employers’ liability and whether your policy covers off-site events. If you are filming with a drone, check the operator’s cover separately.

Two weeks out: submit and confirm

This is the window for the forms that cannot be rushed. A standard TEN should be in well before the 10-working-day minimum. Food registration and allergen signage need to be settled. If you are using a council park or square, confirm site access times, power, waste and wet-weather contingency. If a road closure or parking suspension is involved, assume it needs longer than you think.

Get the venue’s paperwork in one place: risk assessment, method statement, insurance certificate, first-aid plan and a named contact who will actually answer the phone on the day. If the venue asks for a signed contract before it will release the loading bay, that is a launch dependency too.

48 hours out: pack the proof

Print the licence or consent. Print the insurance certificate. Print the risk assessment and the event contact sheet. Save a copy offline. Councils and venues do not want a link to your shared drive when they are standing at the gate.

Check the small stuff: signage, barriers, bin bags, accessible route, noise limits, sample allergens, drone flight window and a backup plan if the weather turns. Confirm that the person named on the permit will be on site. A permission that lives with someone who is not there is a permission with a gap.

The venue is part of your go-to-market

Founders often treat the venue as a backdrop. It is closer to a partner with a compliance team. A good venue will tell you what it needs and when. A bad one will tell you two days before. Either way, the conversation belongs in week six, not launch week.

Ask for the venue’s event pack. Ask who signs off on signage, sound and access. Ask what happens if you need to move the date. The answers will tell you whether the space is a launch asset or a hidden dependency.

Build in a permit buffer

A launch date is a promise to your waitlist. A permit date is a promise to a council. The two need breathing room between them.

If you can, leave a week of buffer after the last permission is confirmed. Use it for the things that always surface: a missing certificate, a changed contact, a noise condition you did not read, a venue that suddenly needs a different insurance wording. That buffer is not slack. It is launch insurance.

The landing page can go live in minutes. The permission to put a demo on the pavement cannot. Treat the paperwork as part of the product launch, and you are much less likely to spend go-live week refreshing a council inbox instead of welcoming early adopters.