Why independence is part of the evidence
When a town hires a technical reviewer for a wireless application, a traffic study or a structural submittal, it is not just buying expertise. It is buying findings that the hearing body can rely on and that a court can later read as substantial evidence. Both depend on one thing the town controls before the review starts: whether the reviewer has any stake in the outcome.
An applicant whose project is denied will look first at the reviewer. If the reviewer has worked for a competitor, markets services to the applicant's industry, or stands to gain from the decision, the applicant's attorney will find it and use it. If the reviewer has none of those ties, and the record shows the town checked, the argument shifts back to the merits, where the town wants it.
Where conflicts come from in technical review
Specialized fields have small pools of qualified people. In wireless siting, many of the engineers who understand radio frequency design, structural loading and FCC rules well enough to review an application also work, or have worked, for carriers, tower companies, site acquisition firms or installers. That is how they learned the work. It is not disqualifying by itself, and a town that refused to hire anyone with industry experience would have no one to hire.
The problem is a conflict that is current, undisclosed or structural. A reviewer doing design work for a carrier this year, then reviewing a competitor's application in your town, has an obvious problem. A reviewer whose firm also does site acquisition for tower companies has a less obvious one. A reviewer paid more when the review takes longer, or who drafted your ordinance and also advises applicants on how to comply with ordinances like it, has a problem built into the arrangement.
Three ideas borrowed from federal contracting
Federal acquisition practice has dealt with this question for decades under the heading of organizational conflicts of interest. The federal rules do not govern a town's consultant contracts, but the three classic categories they recognize are a useful way to think about the problem.
Impaired objectivity. The reviewer's other work could be affected by the outcome of the review. A firm that designs facilities for one carrier and evaluates another carrier's application has a business interest in the result. So does a firm reviewing its own earlier work, such as a structural design it stamped for the same tower.
Biased ground rules. The reviewer helped set the rules it will apply, in a way that could favor some applicants. A consultant who wrote the town's design standards and also sells compliance services to the industry has influence on both sides of the line.
Unequal access to information. The reviewer obtains nonpublic information through the review that would give an advantage to another client. Coverage maps, network plans, lease terms and site lists submitted with an application are commercially sensitive. A reviewer with industry clients must not be in a position to carry them across.
Conflict types and the mitigation for each
Not every conflict calls for the same response. Some can be managed with disclosure and a firewall. Some can be managed only by assigning the review to someone else.
| Conflict | Example | Mitigation |
|---|---|---|
| Current work for the applicant | The reviewer's firm is doing design, permitting or construction work for the applicant or its affiliates anywhere | Reassign the review. Disclosure alone is not enough |
| Current work for a competitor | The firm works for another carrier or tower company active in the same market | Disclose, assign a reviewer who does no work for that client, and firewall the file |
| Past work for the applicant | The firm did work for the applicant within the look-back period | Disclose with dates and scope; the town decides whether the gap is long enough |
| Reviewing its own work | The firm designed, stamped or inspected the structure now being modified | Reassign the review |
| Drafted the standards it applies | The consultant wrote the ordinance and also advises applicants on compliance | Prohibit applicant-side compliance work in the jurisdiction during the term |
| Access to sensitive information | Network plans and lease terms flow to a firm with industry clients | Confidentiality terms, a named-reviewer restriction and a written information barrier |
| Compensation tied to outcome | Fees rise with denials, delays or follow-on work | Fixed rates and not-to-exceed amounts; no contingent fees; no follow-on work from the findings |
| Personal relationships | The reviewer has a family or financial tie to the applicant's staff or a landowner | Individual disclosure and reassignment of that person |
What to require in writing
Independence that is not in the contract is a hope. Put the requirements into the master agreement and repeat the key certification in every task order, so each review carries its own record.
- A disclosure at selection of every carrier, tower company, installer, site acquisition firm and other industry client the firm has served in the specialty over a stated look-back period, with dates and scope
- No current work for any applicant or its affiliates, anywhere, by the firm or the individual reviewer, for the duration of each review
- No work for applicants within the jurisdiction by the individual reviewer assigned to the town during the contract term
- A written information barrier describing who at the firm can see the town's files and how industry-facing staff are kept out
- A signed certification on each task order that the firm and the named reviewer have no conflict with that applicant, and naming any disclosed relationship
- A duty to disclose new conflicts within a stated number of business days of their arising
- Fixed rates and no contingent or outcome-based fees, and no follow-on work arising from the reviewer's own findings
- The town's right to reassign any task order on a conflict, at no cost for work not performed
Add one requirement on the other side. Ask every applicant to disclose, at filing, any business relationship with the town's reviewer or the reviewer's firm. The applicant knows its own vendor list better than anyone. A two-sided disclosure closes the gap that a one-sided one leaves open.
When firewalls work and when they do not
A firewall is a set of internal rules that separates the people doing the town's review from the people serving industry clients. Firewalls can work in firms large enough to keep the two groups apart in practice: different staff, different supervisors, separate file access, and no shared compensation pool tied to the industry work.
They do not work when the same principal supervises both sides, when the reviewer and the industry-facing engineer sit at the same table every day, or when the firm's revenue from industry work dwarfs the town's contract. In those cases the firewall exists on paper only, and an applicant's attorney will say so. Ask how the firewall is enforced, who audits it, and what happened the last time someone crossed it. A firm that cannot answer specifically does not have one.
How to verify independence
Disclosures are where verification starts, not where it ends. A town does not need an investigator to check the basics. It needs an hour and a list.
Read the firm's website, marketing materials and the professional profiles of the named reviewer. Firms list the clients and project types they want to win. Search the agendas and staff reports of nearby jurisdictions for the firm's name: a reviewer who appears as the town's consultant in one place and the applicant's consultant in another is a pattern you want to know about. Check the state engineering board for license status and any discipline. Then compare everything to the disclosure. Gaps are the finding.
The record should show the town checked
Write a one-page memo for each master agreement, and update it each year, recording the disclosures received, the checks performed, what they found, and the decision on any disclosed relationship. When the reviewer's independence is challenged at a hearing or in litigation, that memo shows the town did not take the firm's word for it.
Independent is not the same as adversarial
A reviewer free of ties to applicants can still fail the independence test by working as the town's advocate. A review that reaches for reasons to deny, uses inflammatory language, or ignores evidence in the applicant's favor is as easy to attack as one written by a conflicted reviewer. It invites the argument that the town decided first and commissioned the findings second. The reviewer's job is to tell the town what the application shows and what the rules require, in terms the applicant's own engineer would have to accept.
That means stating where the application complies as clearly as where it does not, citing the standard and the sheet for every finding, and acknowledging the limits of what the reviewer examined. A hearing body that sees findings in both directions trusts the ones that matter.
The same problem outside wireless
Wireless review is where towns most often meet this question, but it is not the only place. Any review where the qualified reviewers also serve the people being reviewed carries the same risk, and the same tools work.
Traffic impact studies. The engineers who review a developer's traffic study for the town often prepare traffic studies for developers in neighboring jurisdictions. Require the same disclosure of development clients, and bar the reviewer from working for any applicant with a pending project in town.
Structural and building plan review. Third-party plan reviewers may also design buildings. A reviewer must never check plans prepared by its own firm or by a firm it has a teaming or ownership relationship with. Ask for ownership and affiliate disclosures, not just a client list.
IT security assessments. An assessor that also resells security products or managed services has an interest in findings that call for its products. Separate the assessment from any procurement that follows, and require the assessor to disclose every vendor relationship that pays it a referral fee, resale margin or partner incentive.
Data and analytics work. A consultant evaluating a vendor's software, or recommending a platform, should disclose any reseller, partner or referral arrangement with the vendors under consideration. The question is the same in every field: does the reviewer earn more if the finding comes out one way?
What independence buys at the hearing
At a hearing, the applicant's engineer and the town's reviewer often disagree. The hearing body, usually without technical training, has to decide whom to believe. Credibility decides it, and credibility starts with the absence of a stake.
A reviewer with a clean disclosure, a documented verification and findings tied to the code can answer the inevitable question, "who else do you work for," in one sentence. A reviewer who hesitates, or whose answer surprises the town, can turn a strong technical case into a weak one in a single exchange. Prepare the reviewer for that question before every hearing, and have the verification memo in the packet.
What independence buys in court
For wireless facilities, Section 332(c)(7) requires any denial to be in writing and supported by substantial evidence contained in a written record. A reviewing court reads that record. Findings from a reviewer with an undisclosed conflict give the applicant a ready argument that the evidence is not substantial, and in jurisdictions where land-use decisions are treated as quasi-judicial, they can also support a claim that the process itself was unfair.
The same is true outside wireless. Traffic, structural, environmental and IT security findings all carry more weight when the record shows they came from someone with nothing to gain. Independence does not guarantee the town wins. It removes the easiest way to lose.
When a conflict surfaces mid-review
Sometimes a conflict appears after the review starts: a merger brings a carrier into the firm's client list, or the applicant's disclosure reveals a relationship the firm missed. Act on it the day it surfaces.
Stop the work and get the facts in writing from the firm. Decide, with your attorney, whether the conflict can be mitigated or requires reassignment. If it requires reassignment, move the task order to your second firm and give the new reviewer the application, not the first reviewer's draft findings, so the new review stands on its own. Note any effect on review deadlines and, where the law allows, discuss a written extension with the applicant. Record each step. A conflict handled promptly and openly rarely damages the town. One discovered later by the applicant almost always does.
Can we hire a reviewer who used to work for a carrier?
Usually yes. Industry experience is often what makes a reviewer competent. What matters is whether the relationship is current, how recent it was, whether it involves the applicant, and whether it was disclosed. Set a look-back period in the contract and decide disclosed relationships case by case.
Is a reviewer paid from the applicant's deposit still independent?
It can be, if the town selects the reviewer, signs the contract, directs the work and receives the findings first. The applicant funds the account; it does not choose or manage the reviewer.
Should the same firm review and then inspect the construction?
That is generally workable, because inspection checks the work against the approval rather than reopening it. The concern is a firm that profits from findings that create follow-on work, so keep inspection fees fixed and separate from the review.
Frequently asked questions
Generally not directly. Federal acquisition rules govern federal contracts. A town's consultant contracts are governed by state law, local ethics codes and the contract itself. The federal categories are useful as a framework for writing the town's own requirements.
Long enough to capture relationships that could plausibly affect judgment, and short enough that qualified reviewers remain available. Many towns choose a period of a few years. Whatever you choose, apply it the same way to every firm.
Choose the reviewer with no current tie to the applicant, require full disclosure of everything else, put an information barrier in writing, and document why the selection is the best available. Disclosure and documentation turn an unavoidable relationship into a managed one.
Making the summary disclosure part of the record helps, because it answers the credibility question before the applicant asks it. Commercially sensitive details about the firm's other clients can usually be summarized rather than published in full. Check your public records law.