How a campaign works
This page describes what happens between a broken definition and a fixed one. It is a description of a process, not a request: nothing here asks the reader to do anything, and PEVRA’s own campaign pages — the ones that do carry a request — are enumerated in the repository file data/lobbying-pages.json and are deliberately not linked from here.
git c35aac7
1. Someone reads their own code
Almost every campaign PEVRA has watched started the same way: a rider looked up their own jurisdiction’s definition and found that their device is not in it. That is what the legal database is for. Each page names the instrument, quotes the operative clause, links the official source, prints the date the source itself carries, and names the steward who checked it. Where PEVRA has not checked, the page says so rather than guessing — most rows in the database say exactly that today.
2. The question becomes specific
A flat statement that the device is banned here is not a thing a legislature can act on. “The definition of a low-speed electric scooter at section X requires two or three wheels, handlebars and a floorboard, so a one-wheeled device falls instead to the motor-vehicle residual at section Y, which it cannot be registered as” is. The jurisdiction pages and their briefs are written to produce the second sentence rather than the first.
3. A vehicle is found
Law changes through a docket — a bill in a session, a rulemaking with a comment window, a hearing on a calendar, a city ordinance on an agenda, an effective date already scheduled. The action calendar tracks the ones PEVRA knows about, each with the days remaining and the official document behind it. A window that has already shut stays on the page, marked closed, because knowing one was missed is worth more than a tidy list.
4. Text is picked, not written from scratch
The model templates exist so that nobody drafts from a blank page. Today there are six, of five kinds: a whole class written by function rather than by shape; two one-clause patches into a definition already in force; a rebuilt category with an umbrella term and one set of operating rules; a city ordinance a council can adopt; and one page that is watching for a body’s own model text and holds none yet, which says so instead of inventing it. Which one fits depends on how much of a code is broken, and each template’s page says what it is for.
5. Objections arrive in a fixed order
They are nearly always the same eight, and they are answered on the objections page. The two that decide most outcomes are “why not use the e-scooter definition we already have” and “shouldn’t riders be licensed”. The first is a drafting question with a factual answer; the second is a policy question, where PEVRA has a stated position and says that it is a position.
6. Something is filed, and it becomes a public record
A comment, a letter, written testimony, a request that an agency start a rulemaking. PEVRA files these under its own name; where it has, the calendar entry for that docket carries the filing and says exactly what was asked for and by when. Those entries are accounted for as PEVRA’s own advocacy, separately from the education pages — which is why this page names them and does not link them.
7. The database is updated, whichever way it goes
A definition that changes produces a new citation record: a new quoted clause, a new steward, a new date. Every one of those changes is a commit in a public repository, so the previous claim does not quietly vanish, and PEVRA’s correction policy is that a retracted claim stays visible, struck through, for 90 days — long enough that a screenshot of the old page resolves to the correction. A campaign that fails produces the same record with the same honesty. The point of a cited database is that it is as useful in defeat as in victory.
What PEVRA does not do
PEVRA does not publish legislator contact details on its education pages, does not run petitions from them, and does not link them into its own advocacy pages. This is a deliberate separation: the pages that report what the law says are accounted for separately from the pages that ask for something, so that the two can never be mistaken for one another. A build gate reads every emitted education page and fails the build on a call to action, a legislator address or a link into the action tree, so the separation is checked on every deploy rather than remembered.
This page is education. It describes a process and asks nothing of the reader. Common objections, answered · The templates · Look up a place
This page is legal information, not legal advice, and is not a substitute for the advice of an attorney. Nothing here should be construed as an attempt to offer or render a legal opinion or otherwise engage in the practice of law. PEVRA does not warrant that this information is complete or accurate and disclaims all liability for any loss caused by errors or omissions. Laws change; check the 'as of' date and the official source linked on every claim.