Sequencing building, health and fire approvals for a new location (DC example)

Why approvals, not carpentry, often decide the opening date

Ask owners what was most frustrating about a buildout and permits come up again and again. In a recent thread on the most annoying part of building a new restaurant or shop, replies included "permits and the fire marshal," paying rent on empty space while approvals worked through, a fire alarm plan held up because only a few companies did that work locally, and frustration with "waiting for one department to move paperwork to the next." We have controller-supplied excerpts of that thread, not a verified complete copy. The replies are complaints from different places, not measurements of any agency's speed.

The practical lesson comes from a post by a contractor with a restaurant background, 10 Things, In No Particular Order, I Would Keep In Mind Before My Buildout. It recommends a permit and inspection calendar kept separately from the construction schedule, with float built in. That is the method here. Construction tasks are under your contractor's control. Approval steps depend on agencies, their reviewers and inspectors. They need their own tracking because you cannot speed them up by adding a crew.

Agency map for a restaurant in Washington, DC

The District is used here as a precise example, because each agency describes its role on a public page. Other cities divide the same work differently. DC's Department of Buildings says on its Permitting in the District of Columbia page that it receives permit applications, reviews construction documents for building code and zoning compliance, inspects construction, and renders buildings safe for occupancy. Plan drawings are reviewed online through ProjectDox. The same page describes a 30-minute Concept Review meeting for owners and developers of large projects to discuss preliminary design, code, inspection or zoning questions before applying. Ask whether your project qualifies before assuming it does.

DOB's Certificate of Occupancy page says applications go through the Certifi platform. Eating establishments must include a completed Eating Establishment Questionnaire and a menu. The page estimates about seven business days for approval. That is DOB's estimate for processing the C of O application, not for your buildout or overall opening. DC Health's Food Establishment Plan Review Guidance Packet (Dec 2019, ver. 8) asks for a proposed menu, manufacturer specification sheets, an equipment schedule, and scaled plans showing equipment, plumbing, electrical services and mechanical ventilation. It also states that a pre-opening inspection with equipment in place and operational is needed. FEMS's Office of the Fire Marshal page describes issuing operational permits required by the fire code and conducting inspections. Confirm with DOB and FEMS where your hood suppression and fire alarm reviews and acceptance tests fall. DC Water's Food Service Establishments & Compliance page says that, unless DC Water approves otherwise, food service establishments must install and maintain a grease interceptor in line with the DC Plumbing Code, and must register through its FOG BMP portal.

Building, health and fire sign-offs are not the whole permission to operate. DLCP's Food Services licensing page covers restaurants and lists what applicants need before licensure: a Certificate of Occupancy, corporate registration if applicable, a DC Health Food Manager's Certificate, a DC Health inspection report, and tax registration with Clean Hands certification. Applications go through BOSS. That makes the business license a gate after the C of O and the health inspection, not something to file in parallel at the start. If you plan to serve alcohol, the Alcoholic Beverage and Cannabis Administration runs a separate application process, listed on its alcohol applications page. That page does not give a duration, so ask ABCA and an advisor early how long your license type is likely to take, and put it on the calendar as its own path.

Building the critical path: what must finish before what

List every approval, then ask of each one: what has to exist before I can apply or schedule it? A building permit needs complete drawings. Complete drawings need settled equipment, because the equipment drives hood length, gas load, electrical circuits and floor sinks. The DC Health pre-opening inspection needs installed and operating equipment, which needs power, gas, water and a working hood. The C of O needs the work finished and passed. The longest unbroken chain of these dependencies is your critical path. Any delay on it moves the opening date unless float absorbs it.

Check which code edition applies. DOB's DC Construction Codes page identifies the 2017 DC Construction Codes, based on the 2015 ICC family and the 2014 National Electrical Code, effective May 29, 2020. It says Title 12 DCMR governs later amendments and transition provisions. DOB has announced that a code update is under way, so your architect should confirm which edition governs your application date rather than assuming.

Hypothetical worked example: a 40-week approvals chain against a week-42 target

All durations below are hypothetical planning assumptions, not agency processing times, except the C of O estimate, which comes from DOB's page. A group signs a lease with rent starting so that it wants to open by week 42. The construction and inspection chain runs: site survey and records pull (2 weeks), design and drawings (8), DOB permit review including one round of comments (8), construction (16), fire suppression and alarm testing (1), final building inspections (1), C of O processing (2, allowing for DOB's seven-business-day estimate plus scheduling), and DC Health pre-opening inspection with staff training (2). That adds up to 2 + 8 + 8 + 16 + 1 + 1 + 2 + 2 = 40 weeks.

The 2 weeks between that subtotal and the target are not free float. The DLCP food services license can only be completed after the C of O and an approved health inspection report, and its processing time is not stated on the page used here. Those 2 weeks must cover license completion and any other remaining gate. If alcohol is part of opening day, the ABCA path has to be tracked separately and may control the date on its own. The honest statement is that the chain is 40 weeks plus an unconfirmed licensing interval. The owner should confirm that interval with DLCP before promising staff or guests an opening date.

Two side paths matter. DC Health plan review is submitted at week 10, alongside the permit. With an assumed 4-week review it finishes at week 14, well before construction, so it has slack. The hood and makeup air package is a long-lead item. Ordering at week 11, before the permit issues, is an owner-approved procurement risk, not a regulatory approval. The owner first confirms the equipment and specifications with the designer and gets the supplier's cancellation and change terms in writing, in case plan review comments change the hood. With an assumed 10-week lead time, it arrives at week 21, while installation is planned for week 26, giving it 5 weeks of float. If the owner waits until the permit issues at week 18, it arrives at week 28, two weeks after it is needed. That would consume the entire 2-week margin before licensing even starts.

Now suppose DOB comments require a second resubmission that adds 3 weeks. The chain becomes 43 weeks, already past the target before any licensing time. At a hypothetical rent of $15,000 a month, one week of rent is about $3,460 (15,000 × 12 ÷ 52 = $3,461.54), before payroll for staff already hired. That is why the tracker exists: the resubmission shows up the week it happens, and the owner can respond, for example by adding a second shift to finishes or talking with the landlord about rent commencement, instead of discovering the slip at the end.

Float and the weekly approvals meeting

Float belongs to the project, not to whichever party slips first. Show it as a separate line on the calendar so everyone can see when it is being used. Hold a short weekly review with the architect, GC and whoever handles filings. For each approval, record status, the next action, who owns it and the date it is due. Approval steps tend to stall quietly. A comment letter sits in an inbox, an inspection request is never submitted, or a portal account belongs to someone who left the project.

Record every agency interaction in a log: application numbers, dates submitted, comments received, resubmissions and inspection results. If a reviewer's comment conflicts with another agency's requirement, write it down and ask both for direction in writing. Do not let the contractor resolve it informally on site. The same log is your evidence if you later ask the landlord for a rent-commencement extension or need to explain a delay to investors.

• Every approval as a line item with owner, next action and due date
• Float shown separately and drawn down only with an explanation
• Agency log: application numbers, comment letters, resubmissions, inspection results
• Long-lead orders placed at design freeze only with owner sign-off on the procurement risk and written cancellation terms
• Licensing gates (DLCP, and ABCA if applicable) tracked as their own lines with confirmed lead times
• A check that portal accounts (ProjectDox, Certifi, FOG BMP) belong to the right people

Who submits what

Responsibility gaps cause many approval delays. Decide in writing who prepares and files each submission. Typically the architect or engineer handles permit drawings and responses to plan review comments. The owner or an expediter handles the health plan review packet, because it includes the menu, operating hours and food-handling answers only the operator can give. The GC and its trades schedule construction inspections and system tests. The owner or tenant applies for the C of O, which on DOB's page requires a lease or owner permission and, for an agent filing, a notarized authorization form. The operator then files the DLCP business license in BOSS once the C of O, health inspection report, food manager certificate and Clean Hands certification are in hand.

Put these assignments in the design and construction contracts, and include the duty to respond to comments within a set number of days. For a restaurant group, the operator side should keep a reusable packet: menu, equipment schedule with make and model numbers, specification sheets and food-safety answers. DC Health's packet asks for an equipment schedule with make and model numbers, so a stable prototype equipment list saves real time at each new site.

The inspections that stack up at the end

The last few weeks are the most crowded. Fire suppression and alarm tests, final building inspections, the health pre-opening inspection and the C of O all depend on everything being finished at once. Small incomplete items can hold up a final sign-off. One owner in a thread about what costs multi-unit operators the most described a final certification held up over a dripping faucet and dim light bulbs. That is one search excerpt, and it is the owner's characterization, but the lesson holds: do your own pre-inspection walk a week before each final.

Confirm the required order with the agencies rather than assuming it. For example, ask whether DC Health expects the C of O first or schedules its pre-opening inspection in parallel, and what DOB's C of O inspection checklist requires. DOB's C of O page links separate inspection checklists for jobs with and without building permits. Our article on punch lists and closeout covers the small items that block finals.

Outside DC: the same logic with different agencies

The DC agency names and portals do not carry over to other places. In another city, the health department may approve plans before the building permit is issued, the fire marshal may review hood suppression drawings directly, or the sewer utility may issue its own permit. Some counties combine these roles into one office. For each new jurisdiction, build the agency map first: who reviews, in what order, what each needs, and which steps can run in parallel. Call or email each office early and record the answers.

Keep the method even when the details change. Map dependencies, find the critical path, protect float, start long-lead orders when the design is stable, and track approvals weekly in their own log. A multi-site group that keeps one calendar template per jurisdiction will see each new site's risks sooner than one that rebuilds the plan every time.