A New Executive Hire Surfaced a Permit Problem Nobody Had Flagged

The situation

Linh and Kenneth had known each other since veterinary school, though only Linh had stayed in the profession full time. Kenneth trained as an accountant, worked a few years in practice, and then let himself get pulled into what started as a side project: helping Linh's clinic run a fundraising gala, then a second one for a friend's nonprofit, then enough weddings and corporate parties that the two of them incorporated an events company almost as an afterthought. Ten years later that afterthought was doing between five and twenty million dollars a year in revenue, Linh still practising part time and overseeing the creative side, Kenneth running the business full time and keeping the books the way an accountant keeps books, which is to say carefully, for everything except the parts of the business that did not look like accounting.

Permit compliance was one of those parts. The events company regularly served alcohol at private functions under special occasion permits, arranged event by event, each carrying its own conditions: hours, capacity, sometimes a requirement for a specific ratio of trained servers to guests. For years this had been handled by whichever staff member was available, with no single person responsible for confirming the conditions were actually met on the night, only for the paperwork being filed in advance.

The company had grown to the point where Linh and Kenneth had agreed, after a long conversation neither of them found easy, to bring in an outside executive for the first time: someone to run operations day to day so Kenneth could step back from parts of the business he had never really wanted to run alone. Wilson, the incoming candidate, before agreeing to terms, asked to see the company's compliance history as part of ordinary due diligence, a request neither Linh nor Kenneth had anticipated because nobody outside the two of them had ever asked.

What the review found was a large corporate event from the previous year where the permitted server ratio and closing hour had both been exceeded, undocumented at the time and unreported since. Nothing had gone wrong at the event itself. But the gap sat on the books, discoverable, at exactly the moment a future executive was deciding whether to tie their career to this company.

The problem

A special occasion permit is not a blanket licence to serve alcohol; it authorizes a specific event, on a specific date, under specific conditions attached to that permit alone. Exceeding the approved hours or falling short of required server ratios is a condition breach regardless of whether any harm resulted, and the licensing authority's response to a breach can range from a written warning to a suspension of the ability to obtain future permits, depending on how it becomes known and how the business responds once it does.

Linh and Kenneth's worry, once the gap surfaced, was not really about the single event. It was about what an unreported breach sitting on the books meant for a company that ran dozens of permitted events a year and depended on smooth, predictable access to permits to keep operating. They were direct about their priority in the first conversation: they did not need a guarantee of a perfect outcome, because they understood there might not be one. What they needed was to understand the range of what could happen and roughly what it would cost, in time and in restrictions on future events, so they could plan around it rather than be surprised by it.

That priority shaped the whole approach. A business that depends on a stream of permits, not one licence renewed annually, cares more about predictability than about winning every point, because an aggressive fight that produces an unpredictable result is worse for that business model than a modest, foreseeable concession.

There was a second layer to the problem. The incoming executive's due diligence had already surfaced the gap, which meant it could not simply be tightened quietly going forward and left in the past. Disclosing it themselves, before it surfaced any other way, mattered both for the licensing relationship and for the credibility of the hire itself, since bringing in an executive on the promise of a clean operation while sitting on an undisclosed compliance gap was not a foundation Linh and Kenneth wanted to build the next stage of the company on.

What we did

1. Assessed the breach on its own facts first. We confirmed exactly which conditions had been exceeded at the event in question, how significantly, and whether any complaint or incident report existed anywhere in the licensing authority's own records, so the disclosure we made would be accurate rather than either understated, which risked a worse outcome later, or unnecessarily alarming, which risked conceding more than the facts warranted.
2. Reviewed the company's permit history for other gaps. Rather than treat the one event as isolated, we checked records for the prior two years of permitted events, both to size the real pattern and to avoid a second surprise turning up later in the same due diligence process or, worse, during the licensing authority's own review of the disclosure.
3. Set realistic expectations before approaching the regulator. We explained plainly to Linh and Kenneth what outcomes were realistic given a self-disclosed, isolated breach with no incident attached, and what factors typically weighed toward a warning rather than a suspension, so their planning going into the hire could proceed on a grounded estimate rather than an optimistic guess that a bad turn would later blow up.
4. Made a voluntary disclosure to the licensing authority. We approached the regulator proactively rather than waiting to see whether the gap would be noticed independently, framing the disclosure around the company's decade-long compliance history and the corrective steps already underway, an approach that is treated materially better by regulators than a breach they discover on their own.
5. Negotiated the terms of the response. Once the authority indicated a warning with short-term restrictions was the likely outcome, we negotiated the specifics of those restrictions directly, pushing for conditions the business could actually absorb rather than accepting the first version proposed, keeping them narrow enough that the company's existing event bookings over the following months would not need to be cancelled, rescheduled, or substantially altered on short notice.
6. Rebuilt the internal permit compliance process. We worked with Kenneth to design a checklist assigning a named staff member, present at each event, responsible for confirming server ratios and closing hours against the specific permit conditions in real time, replacing the informal approach that had let the gap go unnoticed for a year without anyone owning the check.
7. Briefed Wilson directly. With Linh and Kenneth's agreement, we provided Wilson with a clear account of the breach, the disclosure made, and the new compliance process before the start date, so the hire proceeded on full information rather than a gap Wilson might otherwise have discovered independently after joining and taken as a sign of a company hiding problems.
8. Set a review date for the restriction period. Restrictions like these do not always lift themselves automatically once the trigger period ends, so we built a calendar reminder tied to the close of the four-event restriction window and gave Kenneth a short script for confirming with the licensing authority that normal permit conditions had resumed, rather than leaving the company operating under stricter terms longer than necessary out of simple oversight.

The outcome

The licensing authority accepted the voluntary disclosure and issued a formal warning along with a temporary restriction requiring additional advance notice and staffing documentation for the company's next four permitted events. No suspension was imposed, and no existing bookings had to be cancelled, though the restriction period did add administrative work and a small amount of lead time to those four events that the company had not budgeted for during an already busy season.

This was not a clean win, and Linh and Kenneth understood that going in. The company's compliance record now carries a formal warning that will be visible in any future review, and the restriction period, while manageable, was a real cost in staff time during a season the events calendar was already full. Had the breach not been self-disclosed, or had it involved any actual incident at the event itself, the range of outcomes would have looked considerably worse, closer to a suspension that could have disrupted bookings already under contract and put the incoming hire in an awkward position from day one.

Wilson's hire proceeded on the schedule Linh and Kenneth had planned, joining with full knowledge of the gap and the process built to close it, which both of them credited afterward as having strengthened rather than weakened Wilson's confidence in the company. Rather than discovering a hidden problem after signing on, Wilson arrived to a company that had already found its own gap, disclosed it, and fixed the underlying process, which set a different tone for the working relationship than a concealed issue would have.

The new permit compliance checklist has been used at every event since without a further condition breach recorded, and the restriction period closed on schedule with the licensing authority confirming normal terms had resumed. Kenneth now treats the annual review of permit procedures as a standing item on the same calendar as the company's financial reporting, rather than something handled only when a problem forces it.

What you can learn from this