Skip to main content
Before They Build™
How it worksCommunity GuideEvidenceMy RecordResourcesAboutContactStart here
Public Beta · Edition 5 · Updated June 2026·Help improve Before They Build — report errors, suggest features, or share feedback.

Companion Handbook · Investigation

The Research a Project Handbook

How to find out what is actually being proposed before you take a position.

Plate ICivic Handbook · Vol. I · companion volume

Before They Build

The Research a Project Handbook

A Neighborhood Action Guide

Companion Handbook · Civic Handbook · Vol. I

Plate IX — The Evidence Drawer — six steps, one folder
Plate IXThe Evidence Drawer — six steps, one folder
Project
Companion Handbook · Investigation
Status
Companion handbook
Location
Bring to your kitchen table

Vol. I · Edition One · Generated June 19, 2026 · Private to this device · Not legal advice.

© 2026 Before They Build™. All rights reserved. Educational re-use permitted; see beforetheybuild.com/permissions.

Preface

How to use this handbook

This handbook can be read straight through in about half an hour, or jumped into by §-tab when a specific question comes up. It pairs with two other things on this site: the Investigation workflow (the interactive worksheet for one project) and the Community Response Directory (who to call when you have evidence in hand).

  • Read it straight through the first time, so the six steps make sense together.
  • Jump by §-tab after that — every step is self-contained.
  • Use it with the Community Record to log what you find as you go.
  • Use it with the Response Network only after you have facts; phone calls without facts go nowhere.

New to local government? Start with Understanding Local Government. It explains who decides what before this handbook explains how to find out.

Quick wins

If you only have…

  • 15 minutes. Pull the parcel up in county GIS. Note the zoning. Open the planning agenda for next month and search for the address.
  • 30 minutes. Add: walk the site with a phone camera. Note drainage, mature trees, wildlife sign.
  • 1 hour. Add: email the planner with the five questions in §4. Save the reply.

In one paragraph

Why a sign, a rumour, or a flyer is not the project

Most neighbours hear about a project the same way: a sign in a field, a flyer in the mailbox, or a sentence at a community meeting. None of those is the project. The project is the file — the application, the , the , the , the emails. This handbook walks you through finding that file before you decide what you think.

The six steps

The investigation framework

  1. 01Discover
  2. 02Document
  3. 03Verify
  4. 04Contact
  5. 05Respond
  6. 06Decide

Investigation path

  1. Identify. What parcel, what applicant, what application number.
  2. Document. Photograph the site today. Today is the only "before" you will ever have.
  3. Search. Permit portal, planning agendas, county GIS, FEMA flood maps, EPA ECHO.
  4. Contact. Planning staff first. Ask the five questions on §4.
  5. Verify. Read the actual ordinance and the staff report. Do not trust summaries.
  6. Decide. Support, oppose, propose a condition, or keep watching. Write down why.
  7. Escalate. If staff stops responding or records are denied, see §7.

The interactive version is the Investigation workflow— six checkpoints, one printable summary at the end.

Tools to bring

What you will need

  • The address or parcel ID — if you have only a sign, drop a pin on a map and work backwards.
  • A phone with a camera and a timestamp on.
  • A notebook or this handbook's worksheet pages.
  • A folder (paper or digital) named after the project.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Summary

Executive Summary

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

A sign in a field is not the project. The project is the file. Find the file, read the file, and decide based on the file. This handbook is the seven-step path from rumour to record.

Seven steps

  1. Identify — parcel, applicant, application number.
  2. Document — photograph today. Today is your only "before."
  3. Search — permit portal, GIS, agendas, FEMA, EPA ECHO.
  4. Contact — planning staff. Five questions.
  5. Verify — the actual ordinance and the staff report.
  6. Decide — and write down why.
  7. Escalate — when staff goes silent or records are denied.

RED FLAG

Do nothing before you have documented the site. Once construction begins, the "before" photograph is gone.

See Plate IX — the Evidence Drawer.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · §1

§1 — Identify

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

If you do not know what to call it, you cannot research it.

  • Parcel ID or address — from county GIS.
  • Applicant name — usually on the sign or on the agenda.
  • Application number — assigned by the planning department.
  • Type of approval — by-right, special use, variance, rezoning, subdivision.

Worksheet

Parcel / address
Applicant
Application #
Type of approval
Hearing date(s)
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · §2

§2 — Document

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

Today is the only "before" you will ever have. Spend twenty minutes now.

  • Wide shots of the parcel from each accessible side
  • Standing water, drainage paths, low points
  • Mature trees with DBH visible
  • Existing structures and conditions
  • Wildlife sign — burrows, scat, tracks, nests
  • Wetland indicators (cattails, sedges, hydric soils)
  • Existing access points and driveways
  • Adjacent roads, traffic, sight lines

RED FLAG

Keep originals. Phone photos carry GPS and timestamps — those are evidence.

AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · §3

§3 — Search

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

Public records cover ninety percent of what you need to know.

  • County GIS — parcel, zoning, easements, floodplain
  • Permit portal — building, grading, demolition, land disturbance
  • Planning agendas — staff reports posted with the meeting
  • Meeting video archive — what was actually said
  • FEMA flood maps — official flood-hazard layer
  • EPA ECHO — federal compliance history for any facility
  • State public-records portal — for documents not posted
  • Historic aerial imagery — NETR / historicaerials.com for what the site looked like decades back
  • County deeds & registry of titles — chain of ownership and recorded easements
  • State environmental databases — wetlands inventory, contaminated-sites lists, water-quality reports
See the Public Records Handbook for sample request language.
Official RecordGovernment DocumentProfessional ReportMedia ReportSocial MediaRumourFIG. B — Climb the pyramid. Cite the highest tier available.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · §4

§4 — Contact

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

Start with planning staff. Five questions get you eighty percent of the picture.

  1. What zoning district is the parcel in, and what does that allow by right?
  2. What kind of approval does this application need, and where in the process is it?
  3. Has staff issued a report or recommendation yet? May I have a copy?
  4. What conditions, if any, are staff considering attaching?
  5. What is the public comment deadline?

RED FLAG

Be polite. Planning staff is not your opponent. They are the most useful person in the room.

Sample email

Subject: Question about Application #[NUMBER] at [ADDRESS]

Dear [Planner Name],

I'm a neighbour at [YOUR ADDRESS]. I have five short questions about
the application referenced above:

1. What zoning district is the parcel in, and what does it allow by right?
2. What approval type is this application, and where is it in the process?
3. Is a staff report available? May I have a copy?
4. What conditions, if any, is staff considering?
5. What is the public-comment deadline?

Thank you for your time.

[Your name] · [phone] · [email]

Sample voicemail

"Hello, this is [your name] at [phone number]. I'm a neighbour of the property at [address] — Application number [if known]. I'd like to ask five short questions about the approval process and the comment deadline. Please call me back at [phone]. Thank you."

AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · §5

§5 — Verify

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

Do not trust summaries — yours, the applicant's, or anyone else's.

  • Read the exact text of the relevant ordinance section.
  • Read the staff report. Note where it agrees and disagrees with the application.
  • Check that submitted plans match the conditions being proposed.
  • If a study (traffic, stormwater, noise) is cited, get the study itself.

What a staff report actually contains

  • Project description in the planner's own words.
  • Findings against the criteria the body must use to decide.
  • Recommendation — approve, approve with conditions, or deny — with reasons.
  • Proposed conditions of approval, often the most negotiable part.
  • Letters and emails received from the public to date.
RungWhat counts
StrongOfficial permit · official map · recorded plat · signed staff report · adopted ordinance
MediumNews article from a named outlet · public statement on the record · professional study commissioned by an agency
WeakSocial-media post · rumour · second-hand account · anonymous flyer
FIG. A — Weigh every claim against the highest rung you can find.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · §6

§6 — Decide

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

A clear position, written down, is worth a hundred vague concerns.

My positionSupport · Oppose · Conditional · Watching
The key fact
The key concern
Condition I would accept
Deadline to act
The Investigation workflow on the site produces this as a printable summary.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · §7

§7 — Escalation

§1 Identify§2 Document§3 Search§4 Contact§5 Verify§6 Decide§7 Escalate

Most files move quietly through the system. When yours stops moving — or when answers stop coming — you have options.

When staff stops responding

  • Wait one full business week after a polite follow-up before escalating.
  • Copy the planner's supervisor on a brief, factual second email.
  • If still no response, write the planning director and your elected representative.

When records are denied

  • Ask for the denial in writing with the specific exemption cited.
  • Narrow the request — scope is the usual problem, not secrecy.
  • Appeal within the deadline (often 10–30 days).
  • Contact your state's records ombudsperson if one exists.

When permits conflict

Federal usually trumps state; state usually trumps local. Ask each agency in writing which permit it considers controlling and to identify the others it has coordinated with.

When to bring in a professional

  • Land-use attorney — when timelines are short or rights are at risk.
  • Wetland scientist — when wetland boundaries are disputed.
  • Environmental engineer — when stormwater or contamination is at issue.
  • Traffic engineer — when the traffic study is the key disagreement.

When to stop

Not every concern becomes a case. Stop when the information has been obtained, the issue has been resolved, the agency has responded substantively, or the permit complies. Closing a file well is part of doing the work well.

See the Community Response Directory for discipline-level professional listings — never individuals.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Worked Example

Worked Example — 123 Example Road

A fictional but realistic case: a proposed rezoning at 123 Example Road, Anytown — from R-1 (single-family) to MX-3 (mixed-use). Every handbook example on this site is fictional by policy.

§1 — Identify (filled in)

Parcel / address123 Example Road, Anytown — Parcel 14-22-008
ApplicantExample Holdings LLC
Application #RZ-2026-014
Type of approvalRezoning (R-1 → MX-3)
Hearing datePlanning Commission · 14 Aug 2026 · 7:00 PM

§2 — Document

Visited 22 Jun. 47 photos: drainage swale on the south edge, mature oaks along the road, two fox burrows behind the existing barn. Timestamps preserved.

§3 — Search (what turned up)

  • County GIS — parcel is partly within FEMA Zone AE along the south swale.
  • Permit portal — no current building permit; one expired grading permit from 2019.
  • Planning agenda — staff report posted 10 days before the hearing.
  • Comprehensive plan — designates this corridor "Neighborhood Mixed-Use" (consistent with MX-3).
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Worked Example

Worked Example (continued)

§4 — Contact

Emailed planner J. Reyes on 28 Jun. Response next morning:

  • Current zoning R-1; by-right uses are single-family + accessory.
  • MX-3 would allow up to 3 stories, retail on ground floor, residential above.
  • Staff report recommends approval with five conditions.
  • Public comment deadline: 7 Aug, 5:00 PM, in writing.

§5 — Verify

  • Read Ordinance §38-204 (MX-3) directly — confirmed 3-story limit.
  • Staff report's traffic finding cites a 2024 corridor study, not a project-specific study.
  • Stormwater section is conditional on a post-approval engineered plan — not yet drawn.

§6 — Decide

PositionConditional
Key factParcel intersects FEMA Zone AE; no project-specific stormwater plan submitted.
Key concernApproving rezoning before stormwater design fixes the order of operations.
Condition I would acceptApproval contingent on stormwater engineering review prior to building permit.
DeadlineWritten comment by 7 Aug · spoken comment 14 Aug

§7 — Escalation (not needed yet)

Staff responsive, records available, no permit conflict. File stays at Tab C until the hearing decision.

AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Pitfalls

Common Pitfalls

Six ways good investigations go wrong, and how to avoid each.

  1. Calling the wrong office. Planning ≠ permitting ≠ zoning enforcement. Ask the receptionist which desk handles the application number.
  2. Missing the comment deadline. Written deadlines are usually days before the hearing. Calendar it the day you learn about the project.
  3. Treating rumour as fact. If you cannot cite it, do not write it.
  4. Skipping the staff report. The staff report tells you the criteria the body must use. Argue against the criteria, not in spite of them.
  5. Arguing property value when the hearing criteria are about land use, traffic, drainage, or compatibility. Aim at the right target.
  6. Starting research at the hearing instead of weeks before it. By the night of the hearing, the file is usually closed in everything but name.
  7. Mistaking opposition for research. Starting with a conclusion before gathering facts. Decide last.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · What success looks like

What Success Looks Like

You know enough to move forward when every box below is ticked.

  • You know the application number.
  • You have read the public notice end to end.
  • You have identified the decision-making body and its chair.
  • You have the hearing date on your calendar.
  • You know where the staff report and site plan live.
  • You have written down your position and the one fact you would put first.
Six ticks is enough. Keep going only if a new fact changes your position.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Glossary

Glossary

Plain-language definitions for the words this handbook uses.

By-right.
A use the zoning already allows; no hearing needed.
Conditional use.
A use allowed only if certain conditions are met.
Special-use permit.
Permission for a use that isn't allowed by right in this zone.
Variance.
Permission to bend a zoning rule for one specific property.
Rezoning.
Changing what can legally be built on a property.
Easement.
A permanent right for someone else to use part of your land.
Staff report.
The planning department's written analysis and recommendation on an application.
Conditions of approval.
Specific limits attached to an approval (hours, fencing, monitoring, traffic, noise).
Site plan.
The drawing showing what will be built, where, and how it connects to streets, utilities, and drainage.
Comprehensive plan.
The long-range guide a city or county is supposed to follow when making land-use decisions.
Public notice.
A legally required announcement that a decision is coming, usually with a hearing date.
Agenda item.
A single matter scheduled for a body's meeting.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Templates

Templates Appendix

Sample email to a planner

See §4 — Contact for the full version.

Sample meeting request

Subject: 15-minute meeting request — Application #[NUMBER]

Dear [Planner Name],

Could we schedule a 15-minute meeting (in person or by phone) about
Application #[NUMBER] before the [DATE] hearing? I have read the
staff report and have three short questions about [TOPIC].

I'm available [TWO TIME WINDOWS]. Thank you.

[Your name] · [phone]

Public records request

See the Public Records Handbook (Tab B) for the full template.

AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Project File Index

Project File Index

Project File Index

Project name
Parcel / address
Application #
Applicant
Type of approval
Decision body
Hearing date(s)
Comment deadline

Documents collected

DateDocumentSource
   
   
   
   
   
   
   
   

Contacts logged

DateName / roleWhat was said
   
   
   
   
   
   

Decisions and dates

  
  
  
  
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Checklist

Investigation Checklist

Investigation Checklist

Tear this page out. Keep it inside the front cover of your project file.

  • Parcel identified (address or parcel ID)
  • Owner identified
  • Zoning verified against the comprehensive plan
  • Site plan obtained
  • Hearing date found and added to calendar
  • Staff report requested or downloaded
  • Public-records request submitted (if needed)
  • Contacts logged with name, date, and notes
  • Five questions prepared for the hearing or meeting
  • Timeline updated and stored with the project file

Ten boxes. When all ten are ticked, you have done the work. The hearing is no longer the start of your research — it is the end of it.

Related on this site

  • Investigation workflow — the six-step interactive version
  • Read the worked example on its own page
  • Understanding Local Government Handbook
  • The Public Records Handbook
  • Public Records Center — start, track, and appeal records requests
  • Understanding Permits — what the permits in your research actually mean
  • Community Response Directory
  • The Public Hearing Handbook

Research a Project · What success looks like (screen mirror)

What success looks like

You are done enough to move forward when you can check every box below.

  • I have the application number and the parcel ID.
  • I have walked the site and photographed it today.
  • I have read the staff report and the site plan.
  • I have contacted planning staff and saved the reply.
  • I have decided my position and written down why.
  • I know the date of the next decision in this case.

Six ticks is enough. Keep going only if a new fact changes your position.

Research a Project · What success looks like (screen mirror)

What Success Looks Like

You are done enough to move forward when you can check every box.

  • I have the application number and the parcel ID.
  • I have walked the site and photographed it today.
  • I have read the staff report and the site plan.
  • I have contacted planning staff and saved the reply.
  • I have decided my position and written down why.
  • I know the date of the next decision in this case.

Six ticks is enough. Keep going only if a new fact changes your position.

Research a Project · Read next

Read next

Where readers usually go from here. Pick one — they are short.

  • The Public Records Handbook →Templates for getting documents the application packet leaves out.
  • The Public Hearing Handbook →Turn what you found into a three-minute statement.
  • Understanding Local Government →Identify which room makes the binding decision.
  • Community Response Directory →Match each issue you discovered to the right responder.
AHearingBRecordsCResearchDResponseELocal GovFConstruction & Ops
Research a Project · Read next

Read Next

Where readers usually go from here. All four are companion handbooks or tools on Before They Build.

  • The Public Records Handbook — Templates for getting documents the application packet leaves out.
    beforetheybuild.com/handbooks/public-records
  • The Public Hearing Handbook — Turn what you found into a three-minute statement.
    beforetheybuild.com/handbooks/public-hearing
  • Understanding Local Government — Identify which room makes the binding decision.
    beforetheybuild.com/handbooks/understanding-local-government
  • Community Response Directory — Match each issue you discovered to the right responder.
    beforetheybuild.com/resources/respond

Before They Build

Civic Handbook · Vol. I · Edition One

Research a Project Handbook · generated June 19, 2026

beforetheybuild.com/reports/community-guide

Printed June 19, 2026 · Reference ID ------

Private to this device. General information only — not legal advice. Confirm details with your local authority.

© 2026 Before They Build™. Educational use permitted. Not legal advice. Reprint or commercial use: beforetheybuild.com/permissions

Free during Public Beta · Suggested Support $2–3 · beforetheybuild.com/support

Reader-supported

If this resource helped you, consider supporting the mission. Core educational resources stay free for every neighbour.

Support the mission →

Before They Build™A neighbour education project

A neighbour-friendly guide for understanding, documenting, participating in, and remembering the decisions that shape your street.

Best of the site · Sitemap · Binder Map

A · Hearing

  • Public Hearing Handbook
  • Hearing Survival Card
  • Rezoning Handbook
  • Meeting Helper

B · Records / C · Research

  • Public Records Handbook
  • Public Records Center
  • Records Request Packet
  • Research a Project
  • Easement Handbook
  • My Community Record
  • Evidence Packet
  • Notice Decoder

D · Response / E · Local Gov

  • Community Response Directory
  • Agency Library
  • File a Complaint
  • Understanding Local Government
  • Community Guide
  • Agency Contacts

F · Construction & Ops

  • Noise & Construction
  • Water & Wetlands
  • Wildlife
  • Understanding Permits
  • Permit Checklist
  • Permit Response Card

About & Trust

  • Our mission
  • Authority provenance
  • Trust ledger
  • Editorial standards
  • Edition log
  • Glossary
  • Contact
  • Privacy
  • Accessibility
  • Permissions
  • Terms
  • Support
  • Mission · Bundles · AI

Before They Build™ is supported by readers and mission supporters. Core educational resources remain free. Support the mission.

Plain-language note. Before They Build provides general information to help neighbours organize and ask better questions. It is not a law firm, a government agency, or a substitute for legal advice. Always confirm details with your local authority.

© 1970 Before They Build™. All rights reserved. · Permissions · Last updated January 1970.

Public Beta · Edition 5 · June 2026 · what's new · feedback welcome