Citizen-led planning initiatives: Somerset prep checklist

There may be a case number, a technical review, a Planning Commission date, and references to public hearings—yet very little explanation of what any of it means for your block, your road, or the community fabric around you.

You do not need to become a land-use attorney to participate effectively. For citizen-led planning initiatives in Somerset County, the most useful preparation is practical: identify where a proposal sits in the review process, learn which public body is handling it, gather specific information about its local effects, and show up at the right meeting with comments that decision-makers can use.

This guide is a working preparation plan for residents, neighborhood groups, and community organizations. It is not an official county checklist, and it does not replace the public notice or application materials for a particular case. Think of it as a way to make Maryland public participation planning easier to navigate—one step at a time.

Start with the right county office

In Somerset County, planning and zoning work is managed by the Department of Technical and Community Services, commonly referred to as DTCS. That department is the first place to orient yourself when a development proposal or zoning question affects your neighborhood.

The reason this matters is simple: local planning conversations often move between several public bodies. A resident may hear about a site plan at one point, a subdivision plat at another, and a zoning amendment later. Those are connected steps, but they are not the same decision. DTCS staff help administer the planning and zoning process, while advisory groups and public commissions review proposals at different stages.

A useful first conversation with the department should help you answer five basic questions:

• What is the name or case number of the proposal?
• Is the matter a site plan, subdivision plat, zoning amendment, comprehensive plan amendment, or another type of application?
• Has the proposal been reviewed by the Technical Advisory Committee?
• Which body is scheduled to consider it next?
• When and where will public comments be accepted?

The Department of Technical and Community Services is led by Director Jesse Drewer, MPA, with William Cornish serving as Assistant Director and Zoning Administrator. Knowing the department’s structure does not mean you need to memorize staff titles. It simply gives you a clear starting point when navigating the board and trying to understand who can answer which question.

When you contact the department, describe the issue in local terms first. “A proposed project may increase truck traffic on our road” is more useful as an opening than “I oppose this application.” The first statement identifies a planning concern that can be examined through drawings, traffic information, access plans, drainage plans, or conditions of approval.

That distinction also helps us keep public participation constructive. A strong citizen comment is not less forceful because it is specific. In fact, specificity gives the concern somewhere to go.

The fastest way to make a planning process less mysterious is to find out which decision is actually on the table—and which decision has not been made yet.

Build a one-page case file

Before attending a meeting, create a simple folder—digital or paper—with the information you can verify. Keep it to one page at first. You can add detail as the proposal moves forward.

Include:

• The property location and nearest crossroads.
• The applicant or project name, if listed in the notice.
• The type of application.
• The current review stage.
• The next scheduled meeting or hearing.
• The specific change being requested.
• The effects residents are asking the county to study.
• Questions that remain unanswered.

This small record prevents a common problem: discussing a project based on an early rumor after the application has changed. Plans can be revised. A proposed entrance may move, a site boundary may change, or conditions may be added before a public hearing. Keeping track of the current version lets you speak about what is actually pending.

It also makes community conversations more productive. Neighbors may have different views about a project, but they can still agree on factual questions such as where stormwater will go, how emergency vehicles will access the site, or whether a road is expected to handle additional traffic.

Track the Technical Advisory Committee before the Planning Commission

The Technical Advisory Committee, or TAC, reviews site plans and subdivision plats before they are presented to the Planning Commission for final consideration. For residents, this review stage is easy to overlook because it may feel less public than a formal hearing. It is nevertheless one of the most useful points in the process for understanding what a proposal is trying to do and which technical issues are still open.

TAC review is not a shortcut around public participation, and citizen-led planning initiatives cannot bypass it. The committee’s role is to examine the practical details that make a plan workable—or reveal where more information is needed.

Depending on the proposal, those details may include:

• The location and design of entrances and internal roads.
• The relationship between the project and existing rights-of-way.
• Drainage, stormwater, and erosion concerns.
• The placement of buildings, parking, utilities, and service areas.
• Emergency access and circulation.
• The relationship between the proposed use and nearby parcels.
• Compliance with applicable zoning and subdivision requirements.

You may not receive a complete answer to every community concern during TAC review. That is not a reason to wait until the final hearing. It is a reason to identify which questions belong in the technical record and follow them as the application progresses.

A practical way to read the review trail

When you locate project materials, do not begin by trying to understand every drawing. Start with the changes that would be visible from your neighborhood.

Look for:

1. The site boundary. Confirm which parcels are included and how close the project comes to homes, farms, waterways, public roads, and community facilities.

2. Access points. A project with one entrance may create a different safety and traffic pattern from a project with several entrances. Note whether access uses an existing road, a new connection, or a narrow rural route.

3. The proposed use. “Development” is not a sufficient description. A residential subdivision, commercial use, utility-scale solar energy facility, and agricultural support use can have very different effects.

4. The surrounding context. A plan that looks orderly on a page may still create a sharp transition between an established neighborhood and a more intensive use. Pay attention to buffers, setbacks, lighting, fencing, and screening.

5. The unresolved items. Meeting notes, staff comments, or revised plans may show that drainage, access, landscaping, or other issues remain under review.

A resident group can divide this work among several people. One person can review access and traffic, another can look at drainage, and another can compare the proposed use with nearby zoning. Share findings in plain language rather than forwarding a stack of documents without explanation.

Avoid the “everything is wrong” comment

A long list of general objections can make it difficult for a board to identify the decision it needs to make. If a project raises several concerns, rank them.

For example:

• The proposed entrance may conflict with an existing curve and limited sight distance.
• The project may direct stormwater toward neighboring properties.
• The application may not explain how construction traffic will use the local road.
• The proposed buffer may not screen equipment or lighting from nearby homes.

Each point identifies a subject that can be addressed through a plan revision, a condition, a technical response, or further review. That is more useful than repeating that the project is “too large” without explaining what the size changes on the ground.

Understand when one hearing is not enough

Major zoning amendments in Somerset County can require a two-hearing process: one public hearing before the Planning Commission and a second before the County Commissioners. This is especially relevant for significant amendments, including changes involving utility-scale solar energy facilities.

The two hearings are not duplicate appointments on a calendar. They are separate opportunities connected to different stages of decision-making.

The Planning Commission reviews the proposal and makes a recommendation. The County Commissioners then consider the matter in their legislative role. A recommendation is influential, but it is not the final action. If you attend only the first hearing, you may miss the later point at which the legislative body considers the amendment.

That is why your preparation should include a hearing map:

The exact schedule will depend on the proposal and the public notices issued for it. Do not assume that a meeting mentioned in an early announcement is the last opportunity to participate.

Prepare testimony for both audiences

At a Planning Commission hearing, comments about site design, compatibility, access, density, and the relationship to the comprehensive plan may be especially relevant. At a County Commissioners hearing, the focus may include the broader policy and legislative effect of the amendment.

You do not need to give two completely different speeches. You can carry forward the same local knowledge while adjusting the question you are asking.

For example:

• “The proposed access road would add turning movements near a school bus route. What traffic review supports this design?”
• “If the amendment is adopted, what standards will control access, setbacks, screening, and decommissioning for future facilities?”
• “How does the proposed change fit the county’s long-term growth and land-use goals?”

These questions connect what you see every day with the standards the public body is responsible for applying.

For a hearing statement, a reliable structure is:

1. Identify yourself and, if relevant, the neighborhood or community you are speaking from.

2. Name the application or amendment.

3. State your position clearly.

4. Give two or three specific reasons.

5. Request a defined action: additional information, a plan revision, a condition, continued review, or approval or denial based on the record.

6. Close by identifying the local effect you want the board to understand.

A short statement can be more effective than a long one if it gives the board a clear point to consider.

Use Maryland’s participation rules as a practical tool

Maryland law creates a framework for public involvement in planning and land-use decisions. Under Maryland Land Use Code §§ 3-203 and 3-204, a local planning commission must hold at least one public hearing before recommending adoption of a comprehensive plan or plan amendment to the legislative body.

That requirement matters because a comprehensive plan is not merely a background document. It helps establish the county’s direction for growth, land use, infrastructure, housing, transportation, and community facilities. When a plan or plan amendment is under consideration, residents are being asked to comment on a broader direction—not just one parcel.

Maryland jurisdictions also review and update comprehensive plans on a 10-year cycle. Somerset County’s planning conversations therefore sit within a long horizon. A decision made during a workshop or hearing may shape where future development is encouraged, how infrastructure is prioritized, and what kinds of changes communities can expect over time.

Public participation is strongest when we connect an immediate concern to that longer view. If a resident is worried about a proposed development, the question may be larger than whether one project is attractive or unattractive. It may also involve:

• Whether roads, water, sewer, or emergency services can support the pattern of growth.
• Whether new development is being directed toward places that can receive it.
• Whether rural areas, agricultural land, shorelines, or established neighborhoods are being protected in the way the plan describes.
• Whether the county’s infrastructure investments match the growth being considered.
• Whether the proposed change creates a precedent for similar applications.

Watch the notice period

For a proposed subdivision plat, Maryland Land Use Code § 6-103 requires public notice at least 10 days before the planning commission holds a public hearing. Treat that as a minimum period, not as a comfortable planning schedule.

When you see a notice, act promptly:

• Save a copy of the notice.
• Record the hearing date, time, location, and subject.
• Confirm whether written comments are accepted and where they should be sent.
• Ask whether revised materials are available.
• Share the information with affected neighbors.
• Submit questions early enough for staff or the applicant to respond.

A notice may satisfy a legal requirement while still leaving residents with little practical time to organize. Community outreach works better when one person watches county announcements, another monitors meeting agendas, and someone else keeps the neighborhood informed.

The Maryland Planning Commissioners Association, founded in 1983, also provides education and resources for citizen planners and zoning board members. It does not regulate Somerset County zoning decisions, but its educational role can help residents understand the vocabulary and responsibilities surrounding local planning.

Prepare for Somerset Planning Commission meetings

The Somerset County Planning Commission holds public hearings and meetings in Room 111 of the Somerset County Office Complex at 11916 Somerset Avenue in Princess Anne. Confirm the meeting details in the current public notice before you attend, since schedules and agendas can change.

Arriving prepared does not mean arriving ready for confrontation. It means knowing what you want to learn and what you want the commission to remember.

Bring:

• Your one-page case file.
• A printed or saved copy of the public notice.
• The latest plan or staff materials available to you.
• A short list of questions.
• Notes on how the proposal affects your road, property, neighborhood, or community facility.
• A written version of your comments in case the meeting moves quickly.

If you are speaking for a neighborhood group, agree beforehand on who will cover which topic. Five residents repeating the same sentence may use more time without adding more information. Five residents explaining separate, well-supported effects can give the commission a fuller picture of the community’s experience.

During the meeting

Listen for the distinction between discussion and action. A board may ask questions, request revisions, continue a matter, make a recommendation, or take another procedural step. Those outcomes carry different meanings.

Write down:

• What the applicant agreed to change.
• What information the commission requested.
• Whether the matter was continued or moved forward.
• Any conditions discussed.
• The date or event that comes next.

If you do not understand what happened, ask for clarification in a calm, direct way. “Could you explain whether the commission is voting tonight or continuing the matter?” is a perfectly reasonable question. Local government meetings are public because residents should be able to follow the decision, not because everyone is expected to arrive with an insider’s vocabulary.

After the meeting, compare your notes with the official minutes or posted materials when they become available. If a project returns with revised plans, compare the new version with the one you reviewed before. This is where the one-page case file becomes especially useful.

Participation is not only the moment when you speak at the microphone. It is also the steady work of following revisions, sharing accurate information, and returning when the decision moves to its next room.

Turn community concerns into usable planning information

Citizen-led planning initiatives are most effective when they combine lived experience with information a planning body can evaluate. Our community knows things that may not appear in an application: where flooding begins after a heavy storm, where children cross a road, which intersection becomes difficult during harvest traffic, or how a particular parcel connects to a larger pattern of development.

The task is to communicate that knowledge in a way that can enter the public record.

Describe the location

Avoid broad statements such as “traffic is already bad.” Identify the road, intersection, direction of travel, and time or condition when the problem occurs.

A stronger comment might say:

• “Vehicles turning into the property would approach from the east on a road with limited visibility near the existing curve.”
• “During school arrival and dismissal, this intersection already carries pedestrian and bus traffic.”
• “Heavy rain sends runoff toward the low point behind the neighboring homes.”

Specific descriptions help staff determine whether a concern belongs in traffic analysis, stormwater review, emergency access planning, or another part of the application.

Separate observation from assumption

You can say what you have personally observed without claiming information you have not verified. For example:

• Observation: “The road narrows near the proposed entrance.”
• Question: “What is the planned width and sight-distance treatment at that entrance?”
• Request: “Please provide the traffic and access information before the commission acts.”

This approach protects the credibility of your comments. We do not need to overstate a concern to make it matter.

Ask for a response, not only recognition

A public body may not be able to solve every concern in the way a resident prefers. But asking for a response creates a clearer record.

Useful requests include:

• “Please identify how stormwater will be managed during construction and after completion.”
• “Please explain whether emergency access has been reviewed for the proposed layout.”
• “Please clarify which standards will apply if similar facilities are proposed elsewhere.”
• “Please continue the matter until the revised plan is available for public review.”
• “Please explain how this proposal relates to the county’s comprehensive plan goals.”

These requests are neither weak nor adversarial. They give the board a specific way to address the issue.

Build a neighborhood process that can last

One hearing can bring attention to a proposal, but durable civic engagement requires a small system that residents can maintain. This is especially true when a project has multiple review stages or when the county is working through a comprehensive plan update.

A neighborhood group does not need a formal organization to begin. It needs clear roles and reliable communication.

Consider assigning:

• A meeting watcher who checks Planning Commission, County Commissioners, and relevant committee agendas.
• A document keeper who saves notices, plans, revisions, and minutes in one shared location.
• A local knowledge lead who gathers observations from residents along affected roads or near the project area.
• A speaker coordinator who helps residents prepare concise testimony without trying to script everyone’s views.
• A follow-up person who records what the public body requested and whether the next materials address it.

This kind of organization strengthens Eastern Shore community outreach because it makes participation accessible to people who cannot attend every meeting. Someone can submit written comments, review documents, or share a question even when work, caregiving, transportation, or health makes in-person attendance difficult.

Community fabric is built through these small acts of continuity. A resident who misses one hearing should still be able to understand what happened. A new neighbor should be able to find the current plan rather than an outdated social media post. A public comment should be connected to the next stage instead of disappearing after the meeting ends.

Create a simple public record for your group

Keep the record factual and easy to update:

Do not treat this record as a substitute for the county’s official file. Its purpose is to help residents stay oriented and communicate accurately.

If your concern involves a broader issue—such as transportation, housing, agricultural land, shoreline resilience, or access to public services—connect the individual proposal to the county’s comprehensive planning conversation. That is where citizen-led planning initiatives can move from reacting to one application toward shaping the policies that guide future decisions.

A final preparation sequence

When a new notice arrives, use this order:

1. Identify the decision. Determine whether the matter concerns a site plan, subdivision plat, zoning amendment, comprehensive plan amendment, or another action.

2. Find the current stage. Ask whether DTCS staff or the Technical Advisory Committee has reviewed the materials and which public body acts next.

3. Save the notice and documents. Record the date, location, case information, and any written-comment instructions.

4. Map the local effects. Look at access, traffic, drainage, emergency response, compatibility, buffers, lighting, and infrastructure—not only the project’s name or general purpose.

5. Share verified information. Give neighbors the current version of the plan and distinguish confirmed facts from open questions.

6. Prepare focused comments. State your position, explain the local effect, and request a specific response or action.

7. Track every hearing. If the amendment requires a Planning Commission hearing and a County Commissioners hearing, prepare for both.

8. Follow the revision trail. Compare new plans with earlier versions and check whether promised information or changes appear.

9. Record the outcome. Note what was decided, what remains unresolved, and when the next step will occur.

10. Keep the conversation going. Use the experience to participate in workshops, surveys, town halls, and broader county planning discussions.

The goal is not to make every resident fluent in planning law. The goal is to make sure that the people who live with a land-use decision can understand the choice being made and contribute meaningful local knowledge before it is finalized.

Somerset County’s planning process has formal steps, but public participation does not have to feel formal or distant. When we know where to start, follow the review from TAC to the Planning Commission and, when required, to the County Commissioners, and speak in concrete terms about what a proposal means for our roads, homes, services, and shared places, we become more than spectators at a hearing.

We become part of the planning record—and part of the community’s direction.