What’s the Difference Between a Permit Runner and a Permit Expediter?

Imagine two project teams calling for permit help.

The first has a complete plan set, knows the jurisdiction, understands what needs to be submitted, and has dealt with the same department enough times to know what happens next. They do not need somebody to advise on the permit path. They need somebody to submit the package, retrieve comments when they come back, return revised documents, and keep the administrative work moving.

The second team also has plans, but the situation is less settled. The jurisdiction wants forms they were not expecting. Planning may need to review part of the project. One correction belongs with the architect, another needs the structural engineer, and somebody has to make sure the revised package comes back together properly before it goes into another review cycle.

Both teams might say they need someone to “handle the permit.”

They are asking for very different levels of help.

A permit runner generally works from an already-understood process. The client or design team knows what needs to happen, and the runner handles submission, retrieval, resubmittal, status work, and other assigned permit-processing tasks.

A permit expediter can handle those same administrative steps, but the role usually becomes broader. The expediter brings permitting experience into the process itself: understanding the jurisdiction, preparing or checking the submission package, coordinating the project team, tracking comments, communicating with reviewers, identifying likely requirements, and helping determine what needs to happen next.

There is some overlap between the titles. Permit runners and permit expediters are described differently across the industry, and some firms use the terms almost interchangeably. The safest way to hire either one is to look at the actual scope of work, not the title on the website.

What Does a Permit Runner Do?

The simplest permit-running assignment is highly execution-focused.

The architect, engineer, contractor, owner, or permit consultant already understands the project. Plans are ready. Required forms have been identified. The team knows which jurisdiction is handling the permit and knows how it plans to respond if corrections come back.

The runner's job may include submitting or uploading the application, delivering plans where physical copies are still required, retrieving permits or correction packages, tracking status, returning revised documents, processing routine clearances, and repeating those steps through the review cycle.

That work can be genuinely useful. Architects, engineers, contractors, and construction companies do not necessarily want experienced staff spending hours handling administrative permitting tasks when the technical decisions have already been made.

The word runner can sound outdated now because much of permitting has moved online.

A permit runner may be uploading files through a portal rather than physically carrying drawings across town. The underlying service can still be the same: the client provides the direction, and the runner executes it.

There is also no reason to assume every business using the title “permit runner” offers an identical service. Some permit-running companies provide application preparation, tracking, collaboration tools, correction-package handling, and multi-agency processing. That overlap is another reason the label alone does not tell you enough.

What Does a Permit Expediter Do?

Permit expediting usually involves more responsibility for the approval process itself.

An expediter may begin by looking at the jurisdiction, project type, code, current plans, forms, approval path, existing corrections, and departments likely to become involved. They may help assemble the submission package, confirm what is missing, communicate with the permitting authority, monitor review activity, coordinate responses, and keep the owner and project team aware of where the project stands.

The work becomes more valuable when the client cannot simply hand over a checklist and say, “Do these five things.”

An experienced expediter may know, from repeated work in a jurisdiction, that a particular project type commonly requires an additional form, clearance, supporting document, or review step. They may recognize that something in the package is likely to create a question during intake or plan check and bring it to the design team before the project enters the queue.

Los Angeles provides a good example of why this knowledge matters. LADBS publishes different permit applications, document requirements, correction lists, preliminary plan-check services, and separate approval requirements depending on the project. The Department specifically offers preliminary review to identify major site-specific and code-related issues before formal plan check, and notes that early identification can avoid later revisions and reduce processing time and project cost.

A good expediter learns to operate inside that kind of environment.

That does not mean the expediter knows what every reviewer will say before the plans are submitted. Plan review still belongs to the jurisdiction, and individual project conditions matter. The practical advantage is that someone who has handled similar projects and review cycles may see avoidable problems earlier than someone whose job begins only after being told what to submit.

For a broader explanation of the role, we covered this separately in What Is a Permit Expediter and When Do You Need One?.

Some of the Most Valuable Work Happens Before Submission

Permit expediting is easiest to underestimate when people only see the moments involving City Hall or an online portal.

A large part of the value can appear before the first submission.

The expediter can review what the team is preparing against the expected permit path. Are the right application forms being used? Is an owner authorization required? Are additional agency approvals likely? Is the package missing something the jurisdiction expects at intake? Does the project appear to involve a review path the client has not accounted for?

California law itself illustrates why local knowledge has value. State law establishes information required for building permit applications, while also allowing cities and counties to require additional information. Once you move into the actual local process, cities publish their own applications, instructions, correction sheets, and project-specific requirements.

This is one place where experience with only one jurisdiction can create a false sense of simplicity.

Someone who has submitted similar projects in the same city for fifteen years may genuinely find that permit process easy. Much of the difficulty has disappeared because they already know the forms, people, sequence, portal, common comments, and local expectations.

Move the same person into a jurisdiction they rarely work in, or into a larger project with unfamiliar approvals, and some of that invisible knowledge disappears.

We have seen this contribute to confusion over permit-expediting fees. A client may think the work should be inexpensive because permitting feels straightforward to them, when what actually feels straightforward is the particular process they already know extremely well.

The Difference Becomes Clear During Correction Cycles

The first submission is only one part of permitting.

Plan review can return comments that touch several disciplines.

Someone has to keep track of what came back, who owns each response, whether the revised documents are consistent, and when the package is ready to return.

This is where a permit expediter can become the coordination point between the jurisdiction and the project team.

The expediter may receive or organize comments, route the relevant items to the architect and engineer, follow up on outstanding responses, coordinate with other consultants, communicate with reviewers when clarification is needed, and make sure the next submission is not waiting because everybody assumed somebody else was handling one missing item.

There is useful real-world support for this role. In a San Diego Housing Commission ADU pilot, the project architect hired a permit expediter who submitted permits, monitored progress, and liaised with the architect over adjustments required during City review. The report also noted that timely progress depended partly on the architect responding to City requests for additional drawings and corrections.

That is much closer to how experienced permit coordination actually feels. The expediter does not replace the architect or engineer. They help keep the approval process connected while those professionals handle the work that belongs to their disciplines.

An architect can be excellent at design and still have no desire to spend the afternoon checking permit status, sorting comments, confirming which approval is still outstanding, and chasing a consultant for a revised sheet.

An engineer may be responsible for the technical response to a correction but have little reason to manage everything else surrounding the resubmittal.

The expediter keeps those pieces from becoming separate conversations with no one watching the whole permit path.

A Permit Expediter Does Not Replace the Architect or Engineer

This boundary is worth keeping clear because knowledgeable permit expediters often become very familiar with code requirements and plan-check comments.

Familiarity is useful. It does not automatically turn permit coordination into licensed design work.

An expediter may look at a plan set and recognize a condition that has caused corrections on similar projects. They can flag it for the appropriate professional. They may understand what a plan checker is asking and help coordinate the response. They may know which documents typically accompany that response.

If the solution requires structural calculations, engineering judgment, redesign, or other professional work that California reserves for licensed practitioners, the appropriate architect or engineer needs to handle that work. California regulates the practice of civil, electrical, and mechanical engineering, and structural design requirements can require licensed professional involvement depending on the structure and scope.

The useful arrangement is collaborative.

The expediter owns coordination of the permit path.

The architect owns architectural work.

The engineer owns the engineering work within their discipline.

The contractor owns construction execution.

Depending on the project, consultants may own additional pieces.

A strong expediter helps those people respond to the same approval process without pretending to be all of them.

Why Jurisdiction Experience Can Change the Value of the Service

California permitting is local in practice.

Even where statewide codes and statutes provide a common foundation, applicants still deal with city and county processes, local application requirements, different portals, separate departments, project-specific clearances, and locally administered review.

LADBS, for example, distinguishes among express permits, counter plan check, regular plan check, preliminary plan check, and other processes. It maintains separate correction lists for different types of residential, structural, mechanical, electrical, and specialty work, and notes that projects can require approvals from other departments and agencies depending on scope.

That does not mean a permit expediter has some secret ability to bypass the system.

It means experience reduces the amount of the system they have to learn from scratch on each project.

A team entering an unfamiliar jurisdiction may need to determine which department owns the application, which forms are current, what the intake process looks like, which clearances can run in parallel, whether an appointment is required, how comments are returned, and what reviewers expect in a resubmittal.

For someone who works with that jurisdiction regularly, much of that knowledge is already there.

When Is a Permit Runner Enough?

There are plenty of situations where the broader expediting scope is unnecessary.

Suppose an architect has spent years working in the same city. The firm knows the department, has the correct plans and forms ready, understands the submission process, and can handle technical comments internally. The only reason the architect is outsourcing permit work is that they do not want a project manager or designer spending time on uploads, pickups, routine status checks, or document movement.

A permit runner may be exactly what that firm needs.

The same can apply to an experienced contractor or development team with an internal permit process. If the team already knows what to submit, how to respond, who owns every correction, and how the jurisdiction operates, paying for additional advisory or coordination work may add very little.

A good way to think about it is to ask how many decisions still need to be made and if the project is feasible.

If nearly all of the permit decisions and feasibility have already been made and the remaining work is execution, a runner can make sense.

When Does a Permit Expediter Become More Valuable?

The expediter becomes more useful as uncertainty and coordination increase.

An unfamiliar jurisdiction is one obvious trigger. A project team that knows Pasadena extremely well may still benefit from help when taking on work in Los Angeles, Santa Monica, San Diego, or another jurisdiction with a different process.

Project complexity can create the same need. Entitlements, Commercial tenant improvements, changes of use, code-enforcement cases, larger additions, development work, projects involving several agencies, and permits already caught in repeated corrections can require much more coordination than a simple submission.

The need is especially clear when the client cannot confidently answer questions such as:

• Is the project feasible?

• Which forms are still missing?

• Which department needs to act next?

• Who is responsible for each correction?

• Does the architect need to revise something before the engineer responds?

• Are all required clearances accounted for?

• Can the revised package be submitted now, or is another document still outstanding?

Schedule pressure raises the value further.

Once permitting starts affecting contractor scheduling, lease obligations, financing, opening dates, equipment delivery, or other commitments, another unnecessary correction cycle is no longer just administrative inconvenience.

If the question becomes partly economic, our California permit expediter pricing guide goes deeper into why project scope and complexity affect what permit-expediting work costs.

Permit Runner vs. Permit Expediter - Typical Scope

Because the titles overlap in the market, this table should be read as a practical comparison rather than a universal definition.

Area	Permit Runner	Permit Expediter
Submit or upload documents	Common	Common
Retrieve permits or correction packages	Common	Common
Routine status tracking	Common	Common
Resubmit revised documents	Common	Common
Prepare or organize application packages	Sometimes	Common
Research jurisdiction requirements	Scope dependent	Common
Flag likely pre-submittal issues	Not usually core scope	Often part of broader scope
Communicate with reviewers	Limited or as directed	Common
Coordinate architect and engineer responses	Limited or as directed	Common
Manage multi-department approvals	May process assigned clearances	Common
Help determine the next permit step	Usually client-directed	Common
Perform licensed architectural or engineering work	No, unless separately qualified	No, unless separately qualified

The table is useful, but the hiring conversation is even more useful.

Instead of asking only, “Are you a permit runner or an expediter?” ask what the person will actually own.

• Will they preform any feasibility or due-diligence to confirm project code feasibility?

• Will they only submit what you provide?

• Will they review the package before submission?

• Will they identify required forms and clearances?

• Will they communicate with the jurisdiction and attend meetings when needed?

• Will they organize correction responses?

• Will they coordinate your architect and engineer?

• Will they track the project until issuance?

Those answers tell you much more than the title.

The Biggest Misconception About Permit Expediters

The misconception we have seen repeatedly is that a permit expediter simply drops plans off and picks them up.

Sometimes the visible part of the work really does look that simple.

The client sees a submission go in and a correction package come back. What they may not see is the jurisdiction research that happened beforehand, the missing form that was caught before intake, the conversations with the reviewer, the architect who had to update one sheet, the engineer who needed to respond to another comment, the outstanding clearance being tracked separately, or the coordination required to get everything back into one complete resubmittal.

People who are new to permitting can miss that because they have never seen the approval process from inside.

People who have only completed small projects can miss it because their previous permits did not require much coordination.

Experienced professionals can miss it for the opposite reason: after fifteen years in one jurisdiction, so much local knowledge has become automatic that they no longer notice how much they know.

That is why the practical difference between a runner and an expediter becomes clearer when the project becomes unfamiliar.

If you already know the route, someone can run it for you.

If the route itself still needs to be understood, coordinated, and managed, you are usually asking for permit expediting.

Conclusion

A permit runner can be a very good solution when the project team already understands the approval process and mainly needs reliable execution. There is no benefit in paying for layers of guidance that an experienced architect, engineer, contractor, or internal permit team does not need.

A permit expediter becomes more valuable when the approval path itself requires feasibility and attention. That can mean making sure that the project is feasible to begin with, identifying requirements before submission, dealing with an unfamiliar jurisdiction, coordinating comments between architects and engineers, managing multiple departments, keeping corrections organized, or making sure the project team knows what has to happen before the next review cycle.

The titles overlap enough that choosing solely by name is risky. Look at the scope, the experience behind it, the jurisdiction knowledge, and who will actually own the coordination.

For a straightforward permit, execution may be enough.

For a project with moving parts, the person managing those moving parts can be where much of the value sits.