Skip to content
AgendaWire

§01–§10 Practical answers for source-linked agenda alerts.

Start here when you are creating email alerts, reading an alert, or tracing a match back to the public record. Nothing on this page is collapsed, so find-in-page reaches every answer.

01 How AgendaWire works

Four steps run from creating an alert to checking the receipt. The rest of this manual is the detail behind them.

01.1 Create alert

Sign in, then choose one topic and one supported city or county.

01.2 Confirm subscription

AgendaWire saves an active alert and attempts a confirmation email to the signed-in user's email on file. For a workspace without a subscription, it first saves the selected alert as checkout pending; delivery and confirmation start only after Stripe confirms checkout.

01.3 Watch the standby state

A standby stage means monitoring has not started for this account yet, because no alert is configured.

01.4 Check the receipt

Open the source link before you brief a client or stakeholder.

02 Agenda records

Records is a fixed window of the most recent agenda records AgendaWire generated for your own active alerts, newest first, each one tied to its official source.

02.1 What the records feed covers

Records shows only the agenda records AgendaWire generated for your organization's own active email alerts. It is not a database-wide keyword search: there is no keyword box, and nothing outside the alerts you subscribed to appears. It never shows another organization's alert or watchlist data. This is source monitoring, not legal advice.

Open records

02.2 How far back the feed goes

Filters narrow this feed's 50-record recent alert window. Older records stay in the alert emails you already received. This is a fixed window, not a search across your whole history: records are listed newest first, 10 per page, across at most 5 pages for the 50 most recent records.

02.3 Filters

Filters narrow the recent window rather than searching further back: choosing a Jurisdiction or Topic reduces what the 50-record window shows, and never reaches older records outside it. The two filters offer only combinations a single one of your active alerts already covers, so choosing a jurisdiction limits the topics on offer to the ones an alert watches there. A combination no single alert covers cannot be selected, and the feed returns nothing for one assembled by hand in the URL. Filters live in the URL, so a filtered feed is shareable with anyone else in your organization.

02.4 Source context and official links

Records include only events with a summary, business impact, evidence quote, and usable official item, agenda, or packet link. Each shown record carries those fields; the government posting remains the record to rely on. Its record link opens that alert event's detail inside your account.

02.5 When the feed is empty

The feed names its own reason instead of showing a blank page:

  • You have no active alerts yet. Create an alert to start collecting agenda records.
  • No matching records appear in your recent alert window.
  • That page is past the most recent 50 records.

An empty result means nothing matched inside the recent window. It never means the jurisdiction, the topic, or your account has no records at all.

03 Email alert setup

Create an alert by choosing one topic and one supported city or county. AgendaWire handles the matching terms.

03.1 Create an email alert

Sign in, open Alerts, and choose one topic and one supported city or county. Each active alert uses one purchased watchlist slot. For a workspace without a subscription, an owner or admin continues from Create alert to secure checkout; the selection stays checkout pending until Stripe confirms it, then AgendaWire activates it automatically.

Open alerts

03.2 Which topics match today

Topics currently matching new agenda items: Short-Term Rentals, Zoning, Accessory Dwelling Units, Impact Fees, Development Approvals, Data Centers, Signs and Billboards, Alcohol and Cannabis, Procurement and Bids, Economic Development Incentives, Special District Finance, ALPR and Police Surveillance. Staged topics: Housing Tax Credit Support, Annexation and ETJ Changes, Municipal Land Transactions. A staged topic can be selected and saved, but it does not produce new matches until AgendaWire activates its classification.

03.3 STR city or county alerts

For a short-term rental owner, select Short-Term Rentals and choose the one city or county you want to watch. Create a second alert for the other place.

Create STR alert

03.4 Data center alerts

Data center proposals and rules can trigger on direct data center, hyperscale, or server-farm agenda language. Cooling, water use, grid or load demand, substations, backup generation, noise, setbacks, industrial zoning, special-use permits, and development agreements count only when the source ties them to a data center. Generic municipal IT purchases, server replacement, records or document storage, cloud or backup services, and unrelated development items are excluded. This is source monitoring, not environmental analysis, utility forecasting, complete DFW coverage, or legal advice.

Create data center alert

03.5 Procurement alerts

Procurement and contract signals can trigger on planned solicitations, RFP or RFQ authorizations, budget-backed purchases, contract renewals, vendor selections, awards, and relevant consent-agenda actions when the source supports the match. To create a watch, open Alerts, choose Procurement and contract signals, and select an available city or county. The public DFW page monitors the active DFW public meeting sources shown on the coverage page. That source set changes as sources are added or retired. An early signal may never become an open opportunity.

Open DFW procurement watch

03.6 Confirmation email

After an alert becomes active, AgendaWire attempts a confirmation email to the signed-in user's email on file and starts matching future agenda items. The active alert stays active if that confirmation is skipped or cannot be delivered.

04 Sources and coverage

What AgendaWire reads, how fresh it is, and why some records take longer than others.

04.1 What counts as a source

AgendaWire reads public meeting systems, agenda centers, council packet pages, and document links posted by local governments. The official posting remains the record to rely on.

04.2 Public source status labels

Updates delayed means new data is delayed and the saved source check may no longer reflect current source health. Healthy means the latest successful check is still within its expected freshness window and no newer failure is recorded. Stale means no successful check is recorded, or the last success is older than the greater of 24 hours or 3 expected poll intervals. Failing means the latest recorded source check failed after the last successful check. Unsupported means no active supported source is configured for that public body. Unknown means source health could not be checked because the agenda database was unavailable.

Report stale source

04.3 What the last successful check means

The timestamp is the most recent time AgendaWire successfully checked that monitored public meeting source. It does not prove that a government body posted every expected document, that later pipeline stages finished, or that no relevant record exists elsewhere.

04.4 Supported and pending places

A DFW topic page reflects the active DFW source set and links to the coverage page for each source's latest check. A jurisdiction topic page shows checks only for the public bodies listed on that page. If a city or county is unavailable or marked Unsupported, send the jurisdiction and official meeting page so AgendaWire can evaluate coverage.

Email coverage request

04.5 Scanned agenda documents

Some agendas are posted as scanned images with no text layer. AgendaWire attempts OCR recovery on eligible documents, so a scanned posting is not automatically a coverage gap, but a document can still be unreadable and its items can be missed. On jurisdiction topic pages that show Source checks, the per-source row shows source status and may show a recent no-text-layer warning. The DFW topic pages link to the coverage page for each source's latest check. Neither surface proves every document was read or every relevant item matched. When a specific document still cannot be read, check the official posting directly.

04.6 Data center watch coverage

The DFW Data Center Watch follows the DFW public bodies AgendaWire monitors, each listed with its latest source check on the coverage page. It does not include every DFW city, planning or zoning board, code-enforcement system, court case, permit system, or government record.

Open DFW Data Center Watch

04.7 Open official source

Use the official item, agenda, or packet link when you need the public record. AgendaWire may keep an operational copy of what the crawler fetched, but that copy is not a public snapshot link, and the government posting remains the record to rely on.

04.8 Request another city or county

Send the jurisdiction name, the public meeting page, and the topic you care about. We prioritize coverage where there is active demand and a reliable source.

Email coverage request

05 Alerts and digests

What a match contains, how to read each field, and when email arrives.

05.1 What a match contains

Every alert has two sides. The official record is normalized text extracted from the government posting. The AgendaWire read is the classification laid over it. Reading them side by side is how you decide whether to act.

Illustrative example. Not a real agenda item.

Official record
Public body
Dallas, TX · City Council
Document
Posted agenda packet, item 24
Item text
“Authorize a development agreement for a data center campus, including substation and cooling infrastructure, on a 96-acre tract in Council District 8.”
Source link
The official item, agenda, or packet link when the posting provides one.

This side is normalized text extracted from the public posting. Whitespace, document structure, and length can be normalized, so it is not a byte-for-byte copy. The government posting remains the record to rely on.

AgendaWire read
Topic
Data center proposals and rules
Evidence quote
A quoted phrase from the item text, checked against that text before it is stored.
Decision stage
Scheduled how decision stage works
Affected location
Council district: “Council District 8” — how affected location works
Business impact
AgendaWire's source-based read of why the item matters to the topic you asked to watch.
Confidence
92%confidence — the classifier’s 0–100 match score for this topic

This side is AgendaWire’s source-based classification of that text. The evidence quote is checked against the item text; the summary, business impact, decision stage, and affected location are classifier output you should verify against the official posting. Confidence is a 0–100 match score, not certainty and not a legal effect, and alerts currently require at least 70.

05.2 Decision stage and next action

Use these fields to tell a proposal or recommendation from a completed outcome.

Proposed
The source describes a proposal or draft but does not identify a scheduled meeting or completed outcome.
Scheduled
The source places the item on a future agenda or hearing calendar.
Recommended
The source reports an explicit recommendation to another body. A recommendation is not a final decision.
Continued
The source reports that the item was postponed, continued, or rescheduled.
Approved
The source reports approval as a completed outcome.
Denied
The source reports denial as a completed outcome.
Adopted
The source reports formal adoption of an ordinance, resolution, rule, or plan as a completed outcome.
Unknown
AgendaWire did not find enough source-supported procedural detail to assign a stage. Check the official source. Unknown is not a legal conclusion.

Body roles

Recommending body
The source says this body sends a recommendation to another body. It has not made the final decision.
Final decision-maker
The source identifies this body as making the reported approval, denial, or adoption.

Worked examples

Recommendation example

Recommended with a Recommending body means, for example, that a planning commission sent a recommendation to the city council. It is not a final decision.

Final decision example

Approved with a Final decision-maker means the source reports that the named body approved the item as a completed outcome.

Next body, Next meeting, and official action links are designed to appear only when the item text supplies them, and AgendaWire is not designed to fill in another body, date, or action. Check these against the official source before you rely on them.

The government posting remains the record to rely on. AgendaWire provides monitoring information, not legal advice.

05.3 Affected location

This field shows where an item applies, using locations the classifier extracted from the item text.

Exact address
A specific street address the official source names for the item.
Parcel or case
A parcel identifier or case number the source cites for the item.
ZIP code
A ZIP code the source states for the affected area.
Council district
A council or commissioner district the source names.
Corridor
A named street, highway, or corridor the source describes.
Named development
A named project, subdivision, or development the source identifies.
Neighborhood
A neighborhood or district name the source uses.
Citywide
The source describes a citywide or jurisdiction-wide effect.

Displayed locations are extracted by the classifier from the item text, and the list is bounded: AgendaWire shows up to 20 locations for one item, so a multi-property or citywide item can list several rather than only the first. Confirm the geographic scope in the official posting.

Worked examples

Exact address example

Exact address: “1500 Marilla St, Dallas” means the source names a specific address for the item.

District or corridor example

Council district: “Council District 9” or Corridor: “East Lancaster Avenue corridor” means the source names an area rather than one address.

Multi-property example

An item can list several locations, such as Exact address: “220 Main St” and Parcel or case: “Case Z-2026-014”. AgendaWire can list both.

Citywide example

Citywide: “Citywide short-term rental ordinance” means the source describes a jurisdiction-wide effect.

When the classifier produces no usable location, AgendaWire shows Location not stated. AgendaWire does not geocode a location or add coordinates.

An omitted location in the source does not mean the item has no geographic effect. The government posting remains the record to rely on. AgendaWire provides monitoring information, not legal advice.

05.4 Empty states on Alerts

No email alerts yet means no alert has been saved for the account. Inside a saved alert, the empty state names that alert's topic and reads No upcoming <topic> agenda items match this alert yet, which means no qualifying upcoming item has matched it; that state describes the matches, not the health of the monitored sources.

05.5 Email delivery

A matching item is queued for the scheduled immediate-alert run rather than delivered instantly. Daily summaries go out on the daily digest run, and weekly summaries are included in Monday's digest run. Weekly summaries unlock at 2 purchased watchlists and daily summaries at 5, and both stay optional per alert, so no summary arrives unless you turn it on.

05.6 Change or delete an alert

Open a saved alert from Alerts to turn its eligible weekly or daily summaries on or off; immediate email stays on. Owners and admins can delete an alert, which stops that alert and frees its slot to reuse, but it does not lower the quantity billed through Stripe.

Open alerts

06 Account and billing

Profile security, trial status, plan access, and Stripe billing.

06.1 Watchlists, trials, and pricing

Each purchased watchlist slot is $40 per month, and checkout always collects a payment method. A single slot starts with a 14-day free trial that bills automatically at $40 per month afterward unless you cancel; quantities above 1 start paid service immediately. Weekly summaries unlock at 2 purchased watchlists and daily summaries at 5, at no extra cost, and both are optional.

Review pricing

06.2 Stripe billing

Choose 1 to 100 slots from your account page. Workspace owners and admins can change the slot count and open Manage billing, which opens Stripe for invoices and payment methods. Adding slots is prorated right away; reducing slots is not prorated, and the count cannot go below your active email alerts. Contact support if billing access is unavailable.

Open account

06.3 Clerk profile and security

Use your Clerk profile for email, sign-in, and security settings. AgendaWire uses workspaces: active workspace members share alerts and agenda records, and each receives workspace alert and digest email. Members can create or adjust alerts; owners and admins manage billing and can delete alerts.

07 Data and evidence

What AgendaWire stores, and the claims it does not make.

07.1 Public records only

The ingestion pipeline reads public government postings. It does not use private city systems, paid databases, or unofficial social posts.

07.2 Stored source documents

AgendaWire stores fetched source documents so a match can be traced back to what the crawler saw, which helps distinguish a changed source from a missed match. Those copies are operational records rather than public snapshot links, and active source-document storage is retired under the data-retention policy. Public topic pages show qualifying upcoming matches, not an archive of every normalized record.

07.3 Procurement alert limits

AgendaWire is not a bid database. Procurement alerts do not replace SAM.gov, a municipal bid portal, solicitation documents, vendor registration, or procurement due diligence. A source-backed agenda signal may never become an open opportunity.

Review DFW procurement signals

08 Troubleshooting

Common fixes when something looks off.

08.1 No email arrived

Check spam first. If Alerts still says No email alerts yet, no alert has been saved. If a saved alert shows no upcoming matching items, the next qualifying public agenda may not have posted yet.

08.2 A hit looks wrong

Open the source and compare the agenda item with the alert text. If the match is wrong, send the source link and alert subject so we can label it as a false positive.

Report a bad match

08.3 A source is stale

Send the jurisdiction and the official page if you see a newer agenda outside AgendaWire. That gives us the exact connector to inspect.

Report stale source

09 Common questions

The short version. These answers are intentionally blunt.

09.1 Can I use AgendaWire as the official record?

No. AgendaWire points you to official postings. The city, county, or public body remains the source of record.

09.2 Why did one city produce more alerts than another?

Posting habits vary. Some bodies publish detailed packets every week. Others post shorter agendas or meet less often.

09.3 What should I include with a support request?

For support, include the alert name, city or county, topic, source link, and alert subject if you have one.

09.4 Can I create an alert myself?

Yes. Sign in, open Alerts, and choose one topic and one supported city or county. For a workspace without a subscription, an owner or admin continues directly to secure checkout from Create alert; the selected alert activates after Stripe confirms checkout.

09.5 Can AgendaWire add a topic?

Usually, if the topic appears in public agenda language often enough to classify. Send examples from two or three jurisdictions.

10 Contact and escalation

When the manual does not answer it, send the source link and we will trace the pipeline.

10.1 What to send

For an existing alert, send the source link, alert name, city or county, topic, and alert subject. For a source problem, send the jurisdiction and the official page. That is enough to start tracing the pipeline.

10.2 Escalation paths

Every path below reaches the same inbox, support@help.agendawire.com. Picking the right one pre-fills the subject and the details we need.

General support
Anything that does not fit the paths below, or when you are not sure where the problem belongs.Email support
Coverage request
A city or county you want AgendaWire to add or re-check. Send the jurisdiction name, the official meeting page, and the topic.Email coverage request
Bad match
An alert that does not match the agenda item it cites. Send the alert subject and the source link so we can label it a false positive.Report a bad match
Stale source
A body posted a newer agenda that AgendaWire has not picked up. Send the jurisdiction and the official page with the newer agenda.Report stale source