Applicant-paid review fees: how pass-through consultant costs work

Why the applicant pays for the review

A town that receives a complex application often needs expertise it does not keep on staff: a traffic engineer for a large subdivision, a hydrologist for a stormwater plan, an RF engineer for a tower. The usual answer is to hire an outside reviewer and pass the cost to the applicant. The logic is simple. The review exists because the project exists, and taxpayers should not subsidize the analysis of a private development. The mechanics are where towns get into trouble.

Pass-through fees fail in predictable ways. A deposit runs dry in the middle of a review and the consultant stops work. An applicant disputes an invoice nobody can explain line by line. A refund sits unpaid for a year after the project closes. Worst of all, an applicant argues in public that the reviewer is padding hours at the applicant's expense, and nobody can show otherwise.

Every one of those failures traces back to the setup, not to the review itself. Get the fee model, the agreement and the ledger right before the first application arrives, and the program runs quietly for years.

The legal frame: reasonable and tied to cost

Each state sets its own rules for local fees, and some states address consultant review costs directly by statute. The common thread across most of them is that a regulatory fee must bear a reasonable relationship to the cost of the service the town provides. A fee that raises general revenue, or that exceeds the cost of review, starts to look like a tax, and taxes carry different legal requirements. Read your own state's statute and case law with the town attorney before adopting anything. Nothing in this article substitutes for that.

Wireless review has an additional federal layer. In its 2018 order on small wireless facilities, the FCC said fees for those facilities must be a reasonable approximation of the town's costs, that the costs themselves must be reasonable, and that the fees must not discriminate among providers. The order also named fee levels it treats as presumptively reasonable: $500 in non-recurring fees for an application covering up to five small wireless facilities, $100 for each additional facility, $1,000 for a new pole, and $270 per facility per year in recurring charges. A town can charge more if it can show the higher amount reflects its actual, reasonable costs.

Those figures apply only to small wireless facilities, and state law may set lower caps. They still make a useful reference point for any program, because they show how a regulator thinks about review fees: tied to cost, documented, and the same for every applicant. A fee program that could pass that test is in good shape almost anywhere.

Three fee models and how they compare

Towns recover outside review costs in three basic ways, and many combine them. The right choice depends on how predictable the review is.

Model	How it works	Strengths	Weaknesses
Flat fee	A set amount per application type, adopted in the fee schedule	Predictable for applicants, simple to administer, no reconciliation	Must be justified by an actual cost study, and it undercharges the hard cases while overcharging the easy ones
Deposit with draw-down	The applicant posts a deposit, the town pays the reviewer's invoices from it, and the balance is refunded	Matches actual cost, protects the town from nonpayment, scales to complex projects	Requires a ledger per application, replenishment rules and timely refunds
Cost-recovery agreement	A signed agreement in which the applicant pays the reviewer's billed time at a published rate, usually alongside a deposit	Clear consent from the applicant, defined scope and dispute steps, strongest record	More paperwork up front, and it depends on staff to enforce the terms
Hybrid	A flat fee covers routine review, and a deposit is triggered when the application crosses a defined threshold	Keeps simple applications simple and recovers full cost on the hard ones	The trigger must be objective, or applicants will argue about which side of it they fall on

For specialized technical review, the deposit with a signed cost-recovery agreement is the most defensible arrangement. It recovers actual cost, it records the applicant's agreement to the terms before any work begins, and it produces an itemized ledger that answers the padding question with facts.

Sizing the deposit

Size the initial deposit from a realistic estimate of the review: the expected hours for each task, multiplied by the published rate, plus a margin for one round of resubmittal. An illustrative case: a review estimated at 30 hours at a $150 hourly rate, plus 10 hours for a second round, suggests a $6,000 deposit. Your consultant's rate schedule and your own history should drive the real numbers.

Set a replenishment trigger in the agreement. A common approach is to require a top-up when the balance falls below a stated share of the original deposit, and to pause review work, with notice, if the top-up has not arrived within a set number of days. Write the pause into the agreement so it reads as a term the applicant accepted, not a penalty the town invented midstream.

Keep the deposit in a separate ledger account per application. Mixing review deposits with general revenue makes the refund calculation a forensic exercise and invites exactly the challenge the program is designed to avoid.

The consultant's rate schedule

The rate schedule is the document applicants read most carefully, so it should be short, public and stable. List the labor categories that will touch a review, the hourly rate for each, and any reimbursable expenses such as travel or field testing at cost. Fix the rates for the term of the consultant's contract, with any annual adjustment stated in advance.

Decide whether the town adds an administrative charge for its own staff time, and if it does, state it as a separate, disclosed line backed by a cost basis. A hidden markup on consultant invoices is the fastest way to lose a fee dispute and the town's credibility with the development community at the same time.

Publish the schedule with the application materials. An applicant who can estimate the review cost before filing is far less likely to contest an invoice later, and the town's planning staff can point to it when the question comes up at the counter.

From deposit to refund

The lifecycle of a single application should run the same way every time, with each step leaving a record.

Step two is the one towns skip, and it is the one that protects them. A written task authorization defines what the reviewer is being paid to do on this application and estimates the cost. Without it, the invoice is the only record of scope, and the applicant has nothing to compare it against.

Invoicing and reconciliation

Require the reviewer to invoice each application separately, with hours by task and by person, a short description of the work, and the rate applied. "Review of submittal, 6.5 hours" is not enough. "Review of revised drainage calculations, second submittal, 6.5 hours, senior engineer" can be checked against the file.

Staff should compare each invoice against the task authorization before paying it. When hours run past the estimate, the reviewer should have flagged it in writing before the overrun, with the reason: a resubmittal that changed the design, an added meeting the applicant requested, a site visit nobody planned for. The flag goes to the applicant too.

Send the applicant a statement after each payment showing the starting balance, each invoice paid, and the remaining balance. Give the applicant a defined window to question a charge, and a defined path for resolving it, usually a review by a department head with the consultant's backup documents. Most disputes end the moment the applicant sees the detail.

Refunds and closing the account

State in the agreement when the account closes and how fast the balance comes back: for example, within a set number of days after the final decision, the withdrawal of the application, or the end of any appeal period. Applicants remember slow refunds longer than they remember large invoices.

Check whether your state requires interest on escrowed deposits or sets other conditions on holding them, and write the answer into the agreement. Close each account with a final statement that ties out to zero, and keep it with the application file for the retention period your records schedule requires.

Transparency for applicants

Pass-through fees work when applicants believe they are paying for real work at a fair price. That belief is built in advance, not argued after an invoice arrives.

• Publish the program. Post the fee ordinance or resolution, the agreement form and the rate schedule with the application materials.
• Estimate up front. Give each applicant the task authorization estimate before the review starts.
• Itemize everything. Every charge traces to a person, a task, a date and a rate.
• Share the work. Send the applicant the reviewer's comment letters at the same time staff receives them, so the applicant sees what the hours produced.
• Offer a pre-application meeting. A one-hour meeting that prevents a deficient submittal saves the applicant far more than it costs.
• Report the totals. A yearly summary of deposits, billings and refunds by application type answers the question before a council member asks it.

The reviewer must never profit from delay

Hourly pass-through billing carries a built-in conflict: every extra round of review earns the reviewer more money, and the applicant pays for it. Whether or not any reviewer ever acts on that incentive, applicants will notice it, and some will say so at a public meeting. The program has to make the concern structurally hard to sustain.

Several terms do the work. Cap the number of review rounds the applicant pays for at the estimated rate, after which a new authorization is required. Bill the applicant only for time caused by the application; time spent on the town's own internal questions or on staff training is the town's cost. Require the reviewer to issue complete comments in the first round rather than releasing them in pieces. Consider a fixed fee per submittal for routine application types, where the work is predictable enough to price.

Match the reviewer's schedule to the town's legal deadlines. Where a shot clock or statutory review period applies, write the reviewer's turnaround into the consultant contract so the review never becomes the reason a deadline is missed. The best protection against a padding accusation is a ledger that answers it before anyone asks.

Finally, keep the reviewer free of conflicts. The reviewer should not be working for the applicant, a competitor, or an opponent of the project on a related matter, and should disclose any relationship in writing before accepting the task.

What the cost-recovery agreement should cover

Draft one standard agreement with the town attorney and use it for every application that needs outside review. Variations by applicant are what turn a fee program into a negotiation.

• The legal authority for the fee, cited by ordinance or resolution
• The initial deposit amount and how it was estimated
• The replenishment trigger, the notice period and the pause in review if a top-up is late
• The rate schedule, attached, and the term during which it applies
• Any town administrative charge, stated separately with its basis
• What is billable to the applicant and what is not
• The statement frequency and contents the applicant will receive
• The window and process for disputing a charge
• When the account closes and how quickly the balance is refunded
• A statement that payment of review costs does not affect the decision on the application

The last item matters more than it looks. The applicant is paying for the review, not for the outcome, and the agreement should say that in a sentence any council member could read aloud.

Frequently asked questions