How towns buy technical expertise they do not keep on staff

The review you need four times a year

A town of fifteen thousand people does not need a radio frequency engineer on payroll. It needs one for about forty hours a year, usually on short notice, usually when an application is already on the counter and a legal clock is already running. The same is true of traffic impact review, structural plan check on an unusual building, a security assessment of the utility billing system, or a data project nobody on staff has done before.

The question is never whether to buy that expertise. It is how to buy it so the reviewer is under contract before the need arrives, the price is known before the work starts, and the turnaround fits the deadline the law already set. Towns that solve this once spend the rest of the year calling a number. Towns that solve it application by application spend the first third of every review clock on procurement.

Why a full-time hire is the wrong answer

A specialist on staff for a once-a-quarter need sits idle most of the year, drifts toward general work, and loses the current practice that made them worth hiring. Specialties like wireless review or traffic engineering move with the industry: new equipment, new modeling methods, new federal rules. A reviewer who sees dozens of applications a year across many jurisdictions stays sharper than one who sees four in yours.

There is also a coverage problem. One staff specialist is one point of failure. When they are on leave during a busy month, the clock does not pause. A contracted firm with several qualified people behind one agreement covers vacations, conflicts and surges without a new hire.

The honest case for staff is volume. If the town is reviewing a specialty every week, the arithmetic changes and a position may pay for itself. Run the hours from the last two years before deciding. Most towns find the specialty work is lumpy, clustered around a few large projects, and well under a half-time load.

Five routes to the same reviewer

Most municipalities have more than one legal path to a specialist, and the right one depends on how often the need recurs, whether the work counts as a professional service under your state's rules, and who ultimately pays. State procurement law and local charters differ widely, so confirm each route against your own code and your attorney before relying on it. The shapes below are common across many states.

Route	How it works	Best fit	Watch for
On-call professional services agreement	One competitive selection, then a master agreement with rates; each job is a task order	Recurring specialty review where timing is unpredictable	Term limits, total contract caps, and task orders that quietly exceed the original scope
Qualifications-based RFQ	Rank firms on qualifications, then negotiate a fair price with the top-ranked firm	Engineering and architectural work, where many states require this method	Skipping the negotiation step, or letting price creep back in as a ranking factor where the law forbids it
Cooperative contract	Buy from a contract another public entity already competed, if your rules allow it	Commodity IT services and standard assessments	Whether the original solicitation named entities like yours, and whether the scope really covers your work
Interlocal agreement	Share a reviewer or buy services from a county, regional council or neighboring city	Building and plan review, GIS, and regional transportation work	Capacity: the partner's own workload always comes first
Applicant-reimbursed consultant	Town hires and directs the reviewer; the applicant funds it through a deposit or fee	Large or technical land-use applications	Who the consultant answers to, and fee limits that apply to certain application types

These routes stack. A town can hold an on-call agreement with a wireless reviewer, selected through a qualifications process, and fund each task order from the applicant's deposit. The procurement method decides how you choose the firm. The funding method decides who pays. Keep the two decisions separate and both get easier.

On-call agreements, in practice

The on-call agreement is the workhorse for occasional specialty review. You run one selection, award a master agreement to one or more firms, and then issue a short task order each time an application arrives. The task order names the application, the deliverable, the due date and a not-to-exceed amount drawn from the rate schedule in the master agreement.

Award to two firms where the specialty allows it. A second firm covers the conflict case, when the first firm has done work for the applicant, and the surge case, when three applications land in the same month. It also keeps both firms honest on turnaround, because neither one owns the work.

Set the term to match how your rules treat multiyear agreements, commonly an initial term with renewal options. Put a total ceiling on the master agreement that reflects realistic use, and track spend against it in the same spreadsheet you use for the task orders. The most common on-call failure is not bad work. It is a contract that ran out of authorized money in month nine while an application was mid-review.

Qualifications first, price second

For engineering and architectural services, the federal Brooks Act sets the model: rank firms on qualifications, then negotiate a fair and reasonable price with the most qualified one. Many states have their own version for public agencies, and federal grant rules at 2 CFR 200.320 allow qualifications-based selection for architectural and engineering services with price excluded as a selection factor. Whether your specific work falls inside that definition is a question for your code and your attorney. Wireless review, traffic studies and structural plan check usually involve licensed engineers. IT security assessments and data work often do not.

Where qualifications-based selection applies, it serves a town well. The cheapest reviewer is rarely the one whose written findings hold up when the applicant's attorney cross-examines them at a hearing. Ranking on qualifications lets you pick the reviewer you would want testifying, then hold them to a fair price in negotiation. If negotiation fails, you move to the next firm on the list.

Where it does not apply, you can still weight qualifications heavily in a best-value evaluation. Publish the weights. A selection committee that scored qualifications at seventy percent and price at thirty can defend its choice. One that picked the firm it liked and backfilled the reasons cannot.

Applicant-reimbursed review, and who the consultant works for

Many towns recover the cost of specialist review from the applicant, usually through a deposit account drawn down as the consultant bills. This is reasonable and common. It is also the route most likely to compromise the review if the structure is wrong.

The rule that protects you: the town selects the consultant, the town signs the contract, the town directs the work, and the consultant's deliverable goes to the town. The applicant funds the account and receives the invoices for transparency. The applicant never chooses the reviewer, never negotiates the scope, and never sees a draft before staff does. A consultant the applicant picked and paid directly is the applicant's consultant, whatever the letterhead says.

Check the limits on what you can charge before you build the fee. For wireless facilities, federal rules require fees for small wireless facilities to be a reasonable approximation of the town's actual costs, and some states cap application fees by statute. A deposit that funds real review hours at published rates is easy to defend. A flat consultant fee with no relation to the work is not.

What goes in the scope

A scope written once in the master agreement and referenced in every task order saves weeks over the life of the contract. It tells the firm exactly what a complete deliverable looks like, so you are not negotiating the shape of each report.

• The application types covered, named in your code's own terms, so nobody argues whether a modification counts as a new application
• A completeness screen as a separate, fast deliverable, with a written list of missing items tied to the specific code section that requires each one
• The standards the review applies: your code sections, adopted design standards, and the federal or state rules that limit what the town may require
• The written findings format: each finding states the requirement, what the application shows, whether it complies, and what evidence supports the conclusion
• Turnaround in business days for each deliverable, measured from receipt of a complete package from staff
• Hearing support: attendance, testimony, and response to the applicant's rebuttal, priced separately
• Independence terms: disclosure of any work for the applicant or its affiliates, and the right to reassign the review
• Records: the town owns the deliverables, and the consultant retains working files for a stated period in case of litigation

The findings format matters more than it looks. Many land-use decisions must rest on evidence in the written record. A reviewer who writes "the proposal appears acceptable" has given you nothing to rely on. A reviewer who writes "the code requires X, sheet C-3 shows Y, Y meets X because Z" has given you a finding.

Rate schedules that do not surprise the council

Ask for hourly rates by labor category, not by named person. Name the categories (principal, senior engineer, engineer, technician, administrative) and require the firm to say which category each named reviewer falls into. That way a staffing change inside the firm does not reopen pricing.

Fix the rates for the first year and set an escalation rule for each renewal, either a fixed percentage or a published index. State which expenses are reimbursable and at what markup, if any. Travel to a hearing, printing of large-format sheets, and field visits are the usual items. Everything else is in the hourly rate.

Each task order should carry a not-to-exceed amount built from an estimate of hours by category. Require the firm to notify staff in writing before it reaches eighty percent of that amount, with the reason and a revised estimate. A council that approved the master agreement will forgive a change order it heard about early. It will not forgive one it read about in an invoice.

Turnaround tied to the legal clock

This is where most consultant agreements fail the town. The agreement says "timely" or "within thirty days," and the law gives the town sixty days from submittal to decide, including a completeness determination that may be due much earlier. Some deadlines come from federal rules, such as the FCC's shot clocks for wireless facilities. Others come from state permit streamlining laws, subdivision statutes or the town's own code, and some carry consequences as serious as a permit being deemed approved. Know which of your application types carry hard deadlines and what happens when one is missed.

Work backward from the decision date. Subtract the time staff needs to write the report, the agenda deadline for the hearing body, and the legal notice period. What remains is the reviewer's window, and it is usually shorter than anyone expects. Then put the completeness screen at the front, because many deadlines can only be paused by a written incompleteness notice sent within a fixed number of days.

Write those numbers into the master agreement as the default turnaround for each application type, with a shorter turnaround available on request at a stated premium. Then add the clause that matters most: if the consultant cannot meet the turnaround on a given task order, they say so in writing within one business day of receiving it, so staff can route the work to the second firm. The penalty for a late review should be losing the task order, not a fight after the deadline has passed. A consultant agreement that does not know the legal deadline will eventually miss it, and the town, not the consultant, carries the consequence.

Treat any written agreement with the applicant to extend a deadline as an exception, not a plan. Where the law allows mutual extensions, they are useful for a genuinely complex application. They are a poor substitute for a reviewer who was under contract on day one.

Independence written into the contract

A specialist reviewer is useful to the town only if the applicant cannot credibly claim the review was biased, and the town cannot credibly be accused of using a reviewer who was. In fields like wireless siting, many of the qualified engineers also work for carriers, tower companies or installers. That is not disqualifying in itself. Undisclosed, it is.

How to evaluate qualifications

Score what predicts a defensible review, not what fills a proposal. Ask each firm for two redacted review letters from the last two years and read them as the applicant's attorney would. Then call two municipal references and ask one question: did their findings survive a hearing?

• Named reviewer. The actual person who will write your findings, with licenses and years in this specialty. A firm that will not name them is selling a brand.
• Sample work product. Redacted review letters showing findings tied to code, evidence and conclusions.
• Hearing record. How often the reviewer has testified, and whether they have handled cross-examination.
• Turnaround evidence. Typical turnaround on recent municipal reviews, and how the firm handles a surge.
• Conflict disclosure. A complete list of industry clients in the specialty, with the firm's firewall practice described.
• Regulatory currency. How the reviewer tracks changes in federal and state rules that limit what a town may require.

Managing the consultant once hired

Assign one staff member as the contract manager for each master agreement. That person issues task orders, tracks deadlines and spend in one log, and is the only channel between the consultant and the applicant. When an applicant's engineer wants to argue with the reviewer, the conversation happens with staff present or in writing through staff, never in a side call.

Review the first two deliverables closely, then sample. Read for the findings format, the citations and the tone. A review that reads as advocacy against the applicant is as much a liability as one that reads as a rubber stamp. Both give the applicant's attorney something to work with.

Close each task order with a two-line note in the log: delivered on time or not, and whether the findings held. After a year, those notes tell you which firm to call first, whether to renew, and whether the volume now justifies a staff position after all.

Frequently asked questions