Working with a DOB expediter: what they actually do

An expediter's job is to move a filing through the Department of Buildings efficiently. The term covers a wide range of actual involvement, though, and the difference between them is worth understanding before you hire one — or before you accept that your architect has already engaged one on your behalf.

Here is what the role genuinely covers, what it does not, and why we do it inside the same team that draws the set.

At its core, the job is the administration and advocacy of a filing: assembling the application package, submitting it through the department's systems, tracking where it sits, responding to plan-examiner objections, and scheduling the inspections and sign-offs that follow approval.

A good one does more than administer. They know which filing type fits your scope, which supporting documents an examiner will ask for before the examiner asks, and where the current queues actually are. That knowledge is genuinely valuable, and it is not something you can look up.

An expediter does not design your project and cannot make an unapprovable set approvable. If the drawings do not satisfy the code, no amount of filing skill fixes that — it goes back to the architect or engineer, and the round trip is where the weeks go.

They also cannot skip a queue. The word 'expediter' unhelpfully implies otherwise, and it is worth being direct: what a good one compresses is the number of times your application has to go around, not the department's review time itself.

Most owners assume the clock is the department's review. In practice, the elapsed time on a difficult filing is dominated by objection cycles: the set goes in, comes back with comments, gets corrected, goes back in, and waits again.

Each round is not just the correction — it is the correction plus the wait. Which is why the single biggest lever on your permit timeline is the quality of the set that goes in the first time, and the second biggest is how quickly and correctly an objection gets answered.

That reframes what you should be asking a prospective expediter. Not 'how fast are you', which nobody controls, but 'who answers the objections, and how quickly do they turn around'.

The common arrangement is three separate parties: an architect who drew the set, an expediter who files it, and a builder who will eventually build it. When an objection arrives, the expediter often cannot answer it alone — it goes to the architect, who explains the intent, who sends back a revision, which the expediter resubmits.

Every one of those steps is a translation, and every translation costs days. Worse, the person answering is frequently reading the drawing cold, so the answer sometimes satisfies the objection while quietly breaking something the builder needed.

This is not an argument that separate consultants are bad. It is an argument that the seams between them are where projects lose time, and that somebody has to own those seams deliberately.

Our team files what our team designed. When an objection comes back, it is answered by someone who was in the room when the decision behind the drawing was made — so the response is faster and it does not accidentally contradict the build.

It also changes what happens earlier. Because the person who will defend the set at the counter is involved while it is being drawn, filing problems get designed out rather than discovered. That is a much cheaper place to solve them.

And when the permit is issued, the same team schedules the inspections and carries the file to sign-off, so nothing sits in a gap between two companies each assuming the other has it.

Whether the filing sits with us, with your architect, or with a specialist you engage directly, the same questions separate a smooth permit from a slow one.