What I Keep Seeing in Land-Use Permitting and How You Can Get It Right

I have spent most of my adult life in Cambridge public service and in the permitting world. I have sat on the city council , as Mayor, as Chair Of the School Committee, a state senator and now I sit across it as a lawyer. I don’t see this as two sides, I see opportunity for both the City and community and my clients to “ win”. I love this work because it is where a city’s future gets built in real time. If you are a developer who wants to move a project from idea to approval without delay and costs that kill the project, there are a few mistakes I see over and over. The good news is that most of them are avoidable with some discipline and respect for the community process.

This is practical advice. It is not a theory. These lessons come from years of watching good projects get delayed and from helping others land smoothly.

Mistake 1: Treating Permitting Like a Paperwork Step and a sense of entitlement

Permitting is not just forms and deadlines. It is a public conversation about how a project fits into a neighborhood and into the city’s long-term goals. Good zoning is a pure form of Democracy with guardrails. When a team walks in thinking the permit is a stamp they are owed, it shows fast. Boards and city staff can feel that attitude, and neighbors react to it. No developer should believe they are entitled to approvals.

How to avoid it:
Start by hiring people who understand the City and community and then go on a listening tour.What does the community want. Is it housing? Small business? Historic character? Transit access? Tax revenues?If your project can help those goals, good, if not be nimble and modify. Respectfully explain why your plan responds to community wants and explain why and where it may not. Where it doesn’t ,mitigate. still makes sense. Walk in ready to talk about community fit, not just floor area and setbacks.

Mistake 2: Designing in a Bubble

Some teams do months of design without talking to anyone local. Then they arrive at the first meeting shocked by pushback. Any project that spends too long with architects without talking to someone like me , will waste time and money. Also ,if you go public and insult the community regaining : good faith is costly and time consuming.I am not saying you need to hand the pen to every neighbor. I am saying you need to know the landscape before you pour concrete into the design and look for every win-win possible.The community will know quickly if you are truly listening or pretending to listen.

How to avoid it:
Do early listening. Meet with the neighborhood group. Talk to abutters. Speak with planning staff informally. Learn what people worry about so you can address it in your plan instead of scrambling later. You will still hear criticism, but keep a list of all the issues you have heard and responded to.

Mistake 3: Ignoring the “Why” Behind Objections

Developers often hear a complaint and answer it too literally. A neighbor says “traffic” and the team responds with a 200-page traffic study. Sometimes that helps. Sometimes the real concern is safety for kids crossing the street, or fear that the block is changing too fast. Or delivering improvements for the immediate community, not the drivers coming to your new site. If you do not answer the real why, the process drags.

How to avoid it:
When you hear an objection, ask yourself what is underneath it. Acknowledge, don’t deny or diminish real concerns. Then respond in plain language. Show how you will make crossings safer, or how your project adds value without wiping out what people love. Data matters, but empathy and clarity matter more. Show the benefits outweigh the drawbacks or worse alternatives that could be less attractive.

Mistake 4: Don’t Be Cute

My mother always warned us not to be : cute” Nothing kills momentum more than “ gotcha moments “ where the community feels duped or tricked. Do the Counter intuitive and be honest about shortfalls or inconsistencies with community goals but highlight where you are and can be aligned. Also,like missing documents, inconsistent drawings, or last-minute changes that are not explained. Boards take their job seriously. If you look disorganized, they assume the project is disorganized too.

How to avoid it:
Always play devil’s advocate when preparing. Have folks on the team ask questions and challenge the team as the city or community will BEFORE the public meetings or even 1–1 conversations. Have one person responsible for document control. Make sure all sheets match. Label everything the way the board expects. Submit early. If you change something, highlight it and say why you changed it. Professionalism buys trust. Trust buys speed.

Mistake 5: It’s not your job to decide if a community likes a project

I have seen teams tell a community how great the plan is before listening. Nothing is more off putting than presuming what a community wants or should appreciate. It’s obnoxious and sometimes irrecoverable.

How to avoid it:
Introduce a plan after careful planning and explain you think the plan goes a long way but only the community can judge. We are here to listen and change if possible as the community sees fit. Obviously within economic feasibility., .

Mistake 6: Underestimating Conditions and Mitigation

Some developers treat conditions as a personal insult. They push back on every line. That turns a normal negotiation into a war of attrition. Conditions are not punishment. They are how cities balance private projects with public needs.

How to avoid it:
Tell the public we want our commitments and conditions to survive whoever owns the property. Go into the process expecting mitigation but recognizing the community leaders’ stewardship in protecting the public. If you think a condition is unreasonable, explain why with a better option in the spirit of having conditions that can be executed and protected. . Most boards want a workable solution, not a trophy win.

Mistake 7: Not Knowing the Political and Legal Path

Permitting has a legal structure, but it also has a human structure. Different boards have different roles. Timelines depend on appeal windows. One misstep can reset the clock. If you make a mess a long cooling off period may be required statutorily or politically.

How to avoid it:
Don’t make a mess and lose good faith . If you become contaminated, recovery will be a long process. Map the full pathway before you file anything. Know which board has final authority. Know what can be appealed and by whom. Build an approval calendar that includes buffers for public notice, hearings, revisions, and potential appeals. If you do not do this, you will end up in reactive mode.

Mistake 8: Treating City Staff Like Obstacles

Planning staff, traffic engineers, and inspectors are not the enemy. Moreover they have duties and responsibilities to the public . respect that always. They are the people who can help your project succeed if you work with them early and respectfully. If you speed them out or talk down to them, they will stick to the narrowest reading of the rules, and you will feel it.

How to avoid it:
Bring staff into the conversation early. Ask for feedback. Respond to comments quickly. If you disagree, keep it professional and solution-focused.Look and create opportunities for holistic exchanges not just the transfer of paperwork through formal responses. A cooperative tone can save months.

Mistake 9: Forgetting the Neighbors After Approval

This is the last mistake, and it is the one that comes back to haunt people. A developer gets approved, then disappears. By the way, just what they expect. Construction is loud and disruptive, and neighbors feel blindsided. That leads to complaints, inspections, stop-work orders, and bad will on your next project. Worse project team changes from “ developers” to construction and people feel abandoned.

How to avoid it:
Make sure the development team is still involved. Keep communicating regularly. Don’t shift to just a third party construction agent. . Provide a construction contact. Publish a schedule. Tell people when loud work is coming. Fix problems quickly. You do not need everyone to love the project, but you do need them to feel respected.Update the community on commitments and keep them involved. This will pay off in so many ways.

Keep It Simple- All success stems from trust and good faith

Trust and good faith can’t help a terrible project but it can keep a good project from falling prey to politics and delay caused by a myriad of factors. I coach kids, and coaching teaches the same thing permitting teaches. You win by doing the basics well, being consistent and showing respect, and playing the long game. Permitting is not a trick. It is a relationship between a project and a community. If you treat it that way, approvals come faster, cleaner, and with fewer scars.

If you are building in a city like Cambridge, you are not just putting up a structure. Remember while there are great benefits to some new developments, they don’t need you, you need them. You are adding a chapter to a place people call home. You may leave but they are still there so respect that. Take that seriously, and the process will take you seriously.