One public front door
Start with the need, not the department chart. If another authority owns the answer, the city should identify it, explain why, and help with a lawful handoff.
A proposed public front door
Your City Hall, online.
Apply for a permit. Report a problem. Pay a bill. Contest a citation. Reserve a park. Read a contract. Follow a council vote. Prepare for an emergency.
A City of Westside should put every city service in one clear place, available at any hour, with real people responsible for the result.
City of Westside is an exploratory civic initiative, not an existing city, government agency, ballot measure, service provider, emergency service, or official source. No transaction, case, payment, report, permit, alert, or public record is live on this site.
One city. One website. Every service.
The resident should not have to understand the org chart.
Online information can be available at any hour, but the city must also work for people without a smartphone. Real people stay responsible for every answer.
One secure account—when appropriate
Reuse verified information only with permission. Keep public information and anonymous access open where appropriate. Do not require an account just to read, search, or ask a basic question.
One case from beginning to end
Keep the request, documents, payment where lawful, reviews, owner, status, date, decision, reason, correction, appeal, and final record connected.
Share only what is necessary
Departments should share only the information needed for a lawful public purpose. Identity, payments, health, safety, enforcement, employee, and public records need different access and deletion rules.
A public record of responsibility
Publish the rule, responsible department, service standard, source date, contract, cost, results, changes, incidents, and the person who made an important decision.
AI assistance with human control
Use automation to explain and help—not to hide policy, authority, uncertainty, or responsibility. A named human and lawful appeal path remain available.
Everyone must be able to get the same service: phone, counter, mail, language, disability, and trusted-representative options must reach the same responsible department without punishing residents who do not use a smartphone.
Try a sample city-service search
What do you need help with?
Use everyday words. This sample searches only the service examples on this page. It does not use AI, contact an agency, or send anything.
Possible city services
Every service should have a clear front door.
This list shows services residents might expect, not services that exist today. Some responsibilities would remain with county, regional, state, federal, education, nonprofit, private, or contracted organizations.
Showing All service categories. These are examples for a possible city.
Permits, planning & construction
Applications, plan review, inspections, decisions, and appeals.
Parking, streets & mobility
Street conditions, parking, curbs, sidewalks, traffic, and mobility.
Businesses, licenses & taxes
Starting, changing, and operating a business under clear rules.
Bills, fees & payments
Amounts due, lawful payment options, waivers, receipts, and disputes.
Non-emergency public safety
Non-emergency reports, prevention information, records, and follow-up.
Homelessness & human services
Outreach, shelter and service navigation, public-space follow-up, and coordination.
Property, neighborhood & risk
Verified property, planning, service, hazard, and neighborhood information.
Parks, recreation & libraries
Programs, reservations, access, facilities, and community spaces.
Council & participation
Agendas, proposals, meetings, comments, votes, reasons, and follow-up.
Records & transparency
Budgets, spending, contracts, audits, public records, and data.
Jobs & procurement
Public jobs, bids, vendor registration, contracts, and performance.
Elections, ethics & accountability
Elections, disclosures, ethics rules, complaints, audits, and oversight.
Emergency preparedness
Official preparedness guidance, accessible plans, alerts, and continuity information.
Selected service example
One case. One owner. Reasons and an appeal.
Report a neighborhood problem / 311
01Describe
02Route
03Inspect
04Act
05Explain and close
- What you could do
- Describe a non-emergency problem, add a location and accessible evidence, choose anonymous or account-based follow-up where lawful, and see which team owns the next step.
- One case from start to finish
- Example case WST-311-001 keeps one identity from intake through routing, inspection, work, verification, and closure. Sample information only.
- Responsible human or team
- A proposed resident-service team owns intake; the verified street, parking, sanitation, property, or safety team owns the action and answer.
- Status and expected deadline
- The service standard would show an expected first review and target response date, plus a reason whenever it changes.
- Documents, fees, and rules
- Location, problem type, timing, and optional photo. Rules would say when contact information or access permission is needed and when no fee applies.
- Notifications
- Receipt, owner, status changes, requests for information, delay reasons, work result, and closure would use the resident's chosen lawful channel.
- Decision reasons
- The record would explain routing, priority, inspection findings, action, deferral, duplicate closure, or why another authority is responsible.
- Appeal or escalation
- A resident could reopen a wrong closure, ask for a supervisor, correct location or facts, or receive the official route to another responsible body.
- Privacy and public records
- Collect only what is needed. The design must explain which parts of a request may become a public record and protect sensitive contact or safety information as law requires.
- How AI may help
- AI may translate, suggest a service type, remove accidental sensitive detail from a draft, detect missing location information, and summarize the record for staff review.
- What AI cannot decide
- AI cannot treat the report as an emergency, invent an inspection, close the case, rank people by protected traits, or replace an authorized human decision.
All service examples
Read all ten possible services.
Each example shows who would be responsible, what residents would need, how they would receive updates, and how they could challenge a decision.
Report a neighborhood problem / 311
Read the complete model
01Describe
02Route
03Inspect
04Act
05Explain and close
- What you could do
- Describe a non-emergency problem, add a location and accessible evidence, choose anonymous or account-based follow-up where lawful, and see which team owns the next step.
- One case from start to finish
- Example case WST-311-001 keeps one identity from intake through routing, inspection, work, verification, and closure. Sample information only.
- Responsible human or team
- A proposed resident-service team owns intake; the verified street, parking, sanitation, property, or safety team owns the action and answer.
- Status and expected deadline
- The service standard would show an expected first review and target response date, plus a reason whenever it changes.
- Documents, fees, and rules
- Location, problem type, timing, and optional photo. Rules would say when contact information or access permission is needed and when no fee applies.
- Notifications
- Receipt, owner, status changes, requests for information, delay reasons, work result, and closure would use the resident's chosen lawful channel.
- Decision reasons
- The record would explain routing, priority, inspection findings, action, deferral, duplicate closure, or why another authority is responsible.
- Appeal or escalation
- A resident could reopen a wrong closure, ask for a supervisor, correct location or facts, or receive the official route to another responsible body.
- Privacy and public records
- Collect only what is needed. The design must explain which parts of a request may become a public record and protect sensitive contact or safety information as law requires.
- How AI may help
- AI may translate, suggest a service type, remove accidental sensitive detail from a draft, detect missing location information, and summarize the record for staff review.
- What AI cannot decide
- AI cannot treat the report as an emergency, invent an inspection, close the case, rank people by protected traits, or replace an authorized human decision.
Apply for a residential building or remodel permit
Read the complete model
01Find the path
02Prepare
03Review
04Decide
05Inspect and close
- What you could do
- Check which proposed permit path may apply, read current rules and source dates, prepare documents, submit through an authorized future system, pay lawful fees, answer corrections, and receive a reasoned decision.
- One case from start to finish
- Example case WST-BLD-002 follows the same application through completeness check, plan review, corrections, payment, decision, inspections, and final record. Sample information only.
- Responsible human or team
- A named permit coordinator would remain responsible while authorized planners, engineers, building officials, fire reviewers, or outside authorities complete defined reviews.
- Status and expected deadline
- Each review stage would publish an expected response window, queue date, dependencies, and a new date with a reason when the case changes.
- Documents, fees, and rules
- A tailored checklist would identify plans, property facts, owner authorization, professional documents where required, current rules, and itemized fees before submission.
- Notifications
- The applicant would receive completeness, reviewer assignment, correction, fee, decision, inspection, expiration, and appeal notices in accessible form.
- Decision reasons
- Every correction and decision would cite the current rule, source, relevant plan sheet or fact, responsible reviewer, and what would satisfy the requirement.
- Appeal or escalation
- The service would identify correction meetings, supervisor review, code interpretation, hearing, and formal appeal paths with owners and deadlines.
- Privacy and public records
- Public plans and records would be separated from protected contact, security, payment, and account data under records, privacy, and safety rules.
- How AI may help
- AI may explain cited rules in plain language, translate, compare a checklist with uploaded materials, and flag missing fields for human review.
- What AI cannot decide
- AI cannot invent code, issue a final discretionary permit, approve structural or fire safety, waive lawful notice, or decide a final appeal.
Start or manage a business
Read the complete model
01Describe the business
02Build the checklist
03Complete reviews
04Receive decisions
05Maintain and renew
- What you could do
- See a coordinated checklist for the location and activity, identify city and outside-agency responsibilities, complete authorized city steps, track reviews, and maintain renewals.
- One case from start to finish
- Example case WST-BIZ-003 links the proposed city steps for a restaurant while keeping county health, state, federal, and other separate authorities visible. Sample information only.
- Responsible human or team
- A business navigator would own the answer, while each authorized licensing, tax, planning, building, fire, health, or outside agency owns its decision.
- Status and expected deadline
- The case would show city-stage dates and clearly label outside-agency timing as separate and not controlled by the city.
- Documents, fees, and rules
- Business activity, location, ownership authorization, entity information, plans, responsible-party details, current licenses, and itemized fees would be requested only as law requires.
- Notifications
- The service would send checklist changes, assignments, corrections, decisions, payment receipts, inspection notices, renewal dates, and links to outside authorities.
- Decision reasons
- Each city decision would cite the applicable rule and facts; outside-agency decisions would never be paraphrased as city approvals.
- Appeal or escalation
- The record would show the right owner, deadline, hearing, and correction path for each city decision and the official path for separate authorities.
- Privacy and public records
- The service would distinguish public business records from protected identity, tax, payment, security, employee, and account data.
- How AI may help
- AI may build a draft checklist, translate, explain agency boundaries, and flag inconsistent information for a person to resolve.
- What AI cannot decide
- AI cannot promise a complete list without current legal review, approve a business, issue health or alcohol authority, or combine agencies into one hidden decision.
Pay or contest a parking citation
Read the complete model
01Find the record
02Choose pay or contest
03Provide payment or evidence
04Human review
05Reason and appeal
- What you could do
- Look up an authorized citation record, understand the charge and deadline, pay through a secure official channel, request a lawful review, submit evidence, and follow the decision.
- One case from start to finish
- Example case WST-PKG-004 keeps the citation, payment or contest, evidence, notices, review, decision, and any appeal connected without implying a live ticket. Sample information only.
- Responsible human or team
- A parking-citation team owns account accuracy and process; an authorized reviewer who was not the finder tool owns the contest decision.
- Status and expected deadline
- The design would display payment and contest deadlines, expected review dates, hold rules, and any deadline change authorized by law.
- Documents, fees, and rules
- Citation identifier, vehicle or responsible-party verification, selected action, evidence, and any lawful fee or waiver request would be explained before proceeding.
- Notifications
- Receipt, payment result, contest filing, evidence request, hold status, decision, reasons, refund, and appeal deadline would be available in accessible form.
- Decision reasons
- A contest decision would identify the evidence, governing rule, findings, amount due or dismissal, and reviewer authority.
- Appeal or escalation
- The service would state each administrative or court review route, filing deadline, fee or waiver process, and non-digital option.
- Privacy and public records
- Vehicle, identity, payment, location, and evidence data would be access-controlled; public-record treatment and retention would be explained.
- How AI may help
- AI may explain the cited rule, translate, organize submitted evidence, and check that a draft includes required fields.
- What AI cannot decide
- AI cannot determine guilt, issue or dismiss a citation, decide a contest or final appeal, set a fine, or hide the evidence and reason.
Request and follow an inspection
Read the complete model
01Confirm readiness
02Schedule
03Inspect
04Explain findings
05Correct or close
- What you could do
- Request an available inspection tied to an authorized permit or case, choose an access window, identify readiness, receive the inspector's result, and schedule lawful follow-up.
- One case from start to finish
- Example case WST-INS-005 links request, assigned team, access notes, visit, cited findings, corrections, reinspection, and final result. Sample information only.
- Responsible human or team
- The inspection unit owns scheduling and the assigned authorized inspector owns findings, with supervisor and appeal routes visible.
- Status and expected deadline
- Available windows, expected arrival communication, result publication, correction deadlines, and reinspection timing would be shown without guaranteeing unavailable capacity.
- Documents, fees, and rules
- Related permit or case, work stage, responsible contact, safe access, required documents, and any lawful fee would be listed.
- Notifications
- Confirmation, assigned window, lawful access instructions, delay or reschedule reason, result, cited corrections, and next step would be sent.
- Decision reasons
- The result would tie each finding to observed facts, the current rule, evidence where lawful, the responsible inspector, and the way to correct it.
- Appeal or escalation
- A person could request clarification, correct record errors, seek supervisor or code review, and use any formal appeal allowed by law.
- Privacy and public records
- Access instructions, contact details, interior images, safety information, and protected property records would be limited to authorized use and retention.
- How AI may help
- AI may prepare the checklist, translate instructions, group cited corrections, and flag missing result fields before the inspector signs.
- What AI cannot decide
- AI cannot conduct the physical inspection, certify safety, invent conditions, sign a result, or decide a contested finding.
Look up property, neighborhood, and risk information
Read the complete model
01Search
02Compare sources
03Understand limits
04Correct a record
05Follow official guidance
- What you could do
- Search a location and see dated, source-linked records for jurisdiction, planning, permits, services, and official hazard or preparedness information, with conflicts and gaps visible.
- One case from start to finish
- Example case WST-LOC-006 keeps one location reference while showing that parcel, service, hazard, and school records may come from different responsible sources. Sample information only.
- Responsible human or team
- A city information steward owns source display and correction routing; each record owner retains authority over its data and official findings.
- Status and expected deadline
- The service would display each source date, refresh schedule, correction response target, and warning when information is stale or unavailable.
- Documents, fees, and rules
- An address or parcel identifier may be enough for public records; an account would not be required unless law or protected access makes it necessary.
- Notifications
- Optional alerts could cover a saved record's official change, correction result, or source update with clear consent and easy removal.
- Decision reasons
- Every displayed classification would identify its source, effective date, geography, responsible authority, definitions, and known limits.
- Appeal or escalation
- Users could report a mismatch, reach the record owner, request correction under applicable law, and distinguish information service from a formal appeal.
- Privacy and public records
- Public lookup should not expose unnecessary personal information, search histories, protected residents, security details, or inferred vulnerability.
- How AI may help
- AI may explain source terms, compare dated records, translate, and point out conflicts or missing information with citations.
- What AI cannot decide
- AI cannot invent a zone, replace an official hazard map, make a parcel determination, give a guarantee, or issue an evacuation order.
Seek homelessness help or request outreach
Read the complete model
01Describe the need
02Separate urgent and non-urgent paths
03Assign a human owner
04Coordinate lawful help
05Report an appropriate outcome
- What you could do
- Find verified help, request non-emergency outreach, describe urgent welfare or public-space concerns, understand which authority owns the next step, and receive appropriate follow-up where privacy allows.
- One case from start to finish
- Example case WST-HLP-007 separates a request for help from a public-space service issue while preserving one accountable coordination record. Sample information only.
- Responsible human or team
- A trained human-services coordinator owns routing and follow-up; authorized outreach, health, county, nonprofit, property, sanitation, or safety teams own their lawful work.
- Status and expected deadline
- The design would show an expected initial review, urgency criteria, owner, next contact, and honest limits where privacy or service availability prevents case-level disclosure.
- Documents, fees, and rules
- Location, observed need, safety concern, requested help, and optional contact information. It must not demand unnecessary identity, immigration, disability, or medical data.
- Notifications
- The requester would receive receipt, responsible team, appropriate status, delay or limitation reasons, and closure language that does not expose a person's private services.
- Decision reasons
- The record would explain routing, public-space action, lawful limits, and what success means without claiming that a person accepted service or left the street.
- Appeal or escalation
- People seeking help and requesters could correct facts, ask for a supervisor, use complaint or civil-rights routes, and receive official emergency direction when needed.
- Privacy and public records
- Housing, health, disability, benefits, immigration, location, and outreach details require strict minimization, role limits, retention, and separation from unnecessary enforcement.
- How AI may help
- AI may translate, explain verified options, route a draft by stated need, flag missing safety context, and summarize notes for authorized human review.
- What AI cannot decide
- AI cannot diagnose, determine eligibility, promise housing, direct enforcement, rank a person's worthiness, disclose protected data, or close a welfare concern without human review.
Search city spending, contracts, and public records
Read the complete model
01Search openly
02Open the source
03Ask or request
04Receive reasons and records
05Appeal if needed
- What you could do
- Search adopted budgets, transactions, contracts, changes, invoices, vendor performance, audits, and public records; download source records or start a lawful records request when information is not already public.
- One case from start to finish
- Example case WST-REC-008 links a public search, source document, clarification, records request if needed, response, production, exemption reason, and appeal. Sample information only.
- Responsible human or team
- A finance data steward owns published spending; procurement and department owners explain contracts; the records officer owns formal request and appeal handling.
- Status and expected deadline
- Published data would show update dates. A records request would show applicable acknowledgment, estimate, production, extension, and appeal dates without promising a result before review.
- Documents, fees, and rules
- Public search should require no account. A records request needs a clear description and delivery choice; identity is collected only when law or fulfillment requires it.
- Notifications
- Saved-search updates would be opt-in. Formal requests would receive acknowledgment, scope questions, estimates, releases, withholding reasons, and appeal instructions.
- Decision reasons
- Spending records would trace to adopted authority and source documents. Withholding, redaction, delay, no-record, or cost decisions would cite the responsible rule and person.
- Appeal or escalation
- A requester could narrow or clarify, challenge a redaction or denial, seek records-officer review, and use any independent or court remedy allowed by law.
- Privacy and public records
- Open records must be balanced with lawful privacy, security, privilege, protected personal information, and records retention—never hidden behind a dashboard.
- How AI may help
- AI may explain terms, find source documents, compare versions, extract cited fields, translate, and summarize with links to the underlying record.
- What AI cannot decide
- AI cannot invent spending, alter source records, decide a final exemption or denial, conceal a contract, or present an unsupported inference as fact.
Follow a council decision and participate
Read the complete model
01Find the matter
02Read source material
03Participate
04Follow the vote
05Track what happens next
- What you could do
- Follow a proposal from introduction through staff analysis, public notice, accessible meeting materials, comments, amendments, votes, signed text, the department responsible for carrying it out, and later review.
- One case from start to finish
- Example case WST-CNL-009 keeps one public matter number across agenda versions, source documents, comments, amendments, votes, reasons, effective date, and updates on the result. Sample information only.
- Responsible human or team
- The city clerk owns the public matter record; named staff own analysis; elected officials own their votes; the implementing department owns the result.
- Status and expected deadline
- The record would show notice, meeting, comment, vote, effective, action, and review dates, plus any lawful delay or reason for a change.
- Documents, fees, and rules
- Reading and searching need no account. Participation instructions would state format, deadline, accessibility, language, disclosure, decorum, and alternative channels.
- Notifications
- Residents could choose to receive agenda, amendment, meeting, vote, effective-date, and follow-up notices without being tracked for political targeting.
- Decision reasons
- The final record would preserve staff reports, public materials, amendments, roll-call votes, adopted text, executive action if any, and the authority to carry out the decision.
- Appeal or escalation
- People could correct accessibility or records problems, use ethics or open-meeting complaint routes, petition or seek review where law allows, and contact a human clerk.
- Privacy and public records
- Public comments and lobbying or ethics disclosures may be public; the service must explain this before collection and protect unnecessary account, language, disability, and contact data.
- How AI may help
- AI may translate, summarize with citations, compare versions, find a topic, prepare an accessible plain-language guide, and help staff route questions.
- What AI cannot decide
- AI cannot secretly make policy, write an authoritative final law without adoption, manufacture public support, suppress a view, vote, or target people by protected traits.
Prepare for an emergency
Read the complete model
01Know the official sources
02Make an accessible plan
03Choose official alerts
04Practice fallbacks
05Follow agencies during an incident
- What you could do
- Find source-linked official preparedness information, build an accessible household or business checklist, identify official alert channels, review current agency roles, and plan non-digital fallbacks.
- One case from start to finish
- Example case WST-READY-010 stores no live emergency status; it organizes a private checklist and links each official source without becoming an alert or dispatch record. Sample information only.
- Responsible human or team
- Authorized emergency agencies own warnings, orders, response, and official plans. A proposed city preparedness team would own only its lawful information and coordination duties.
- Status and expected deadline
- Preparedness pages would show source and review dates. During an incident, only official agencies may publish authoritative timing, warnings, routes, shelters, or orders.
- Documents, fees, and rules
- Public guidance should require no account. Optional saved checklists need clear consent, minimal data, deletion controls, accessible alternatives, and no hidden location tracking.
- Notifications
- The design would link to official alert registration and explain which agency sends each notice; it would not simulate enrollment, warnings, or delivery.
- Decision reasons
- Every instruction would identify the responsible official source, date, geography, and whether it is general preparedness or current incident guidance.
- Appeal or escalation
- People could report inaccessible or conflicting information, reach a human preparedness contact, correct an account setting, and use official complaint channels.
- Privacy and public records
- Preparedness must avoid creating a detailed vulnerability registry by default. Any access-and-functional-needs data requires purpose, consent, security, retention, and human safeguards.
- How AI may help
- AI may explain and translate official preparedness material, help draft a checklist, surface accessibility needs, and compare dated source versions with citations.
- What AI cannot decide
- AI cannot issue authoritative emergency orders, predict a safe route, invent current conditions, dispatch help, replace 911, or contradict responsible agencies.
Public AI under public rules
A resident bill of rights for public AI
Residents have the right to know when AI is used, what it does, which sources it relies on, and which human remains responsible.
These rights should apply whether the city builds a tool, buys one, receives it through a contractor, or uses it behind the counter. A vendor label never moves accountability away from government.
Know when AI is used and what role it plays.
See the official sources behind an answer or recommendation.
Reach a trained human without being trapped in automation.
Receive an understandable reason for a consequential decision.
Correct inaccurate data and challenge unsupported inferences.
Appeal through the same lawful path available without AI.
Obtain public records and audit information, subject to lawful limits.
Avoid collection that is not necessary for a stated public purpose.
Receive equivalent service without a smartphone or AI interface.
Know which department, system, and vendor is involved.
AI may assist
Useful, narrow, and visible
- Explain current, cited rules in plain language
- Translate and improve accessibility
- Help complete a form without signing or deciding it
- Route and summarize for authorized staff review
- Flag missing or conflicting information
- Compare records while preserving source links
- Identify patterns for human investigation and public audit
Assistance must display source, uncertainty, limits, the responsible department, and a clear route to a person.
AI must not
Authority cannot disappear into a model
AI must not secretly make policy, invent law, or turn a prediction into an unappealable public decision.
- Secretly make policy or invent law
- Issue a final discretionary permit
- Determine guilt or decide a final appeal
- Deny benefits, rights, or essential service without accountable authorized human review
- Conduct generalized facial recognition or mass surveillance
- Rank residents by political or social standing
- Use protected characteristics improperly
- Hide sources, uncertainty, or reasons
- Issue authoritative emergency orders
Proposed public AI register
If the city uses it, the public can inspect it.
Before the city uses AI, it should publish who is responsible, what the tool does, what information it uses, how it was tested, what it costs, what went wrong, and who can stop it.
- Purpose
- The specific public problem, legal authority, intended benefit, and uses that are out of scope.
- Department
- The named public owner and contact responsible for the result, records, complaints, and correction.
- Vendor or system
- The product, model, version, provider, subcontractors, hosting, and important changes.
- Data used
- Sources, collection authority, sensitive fields, sharing, quality limits, access controls, and resident correction path.
- Decision role
- Whether the system explains, drafts, routes, recommends, flags, or affects a consequential decision—and who decides.
- Tests and results
- Accessibility, security, privacy, accuracy, bias, reliability, language, failure, and real-world monitoring with methods and dates.
- Human review
- Named review point, training, authority, time, records, override, escalation, and resident contact options.
- Retention
- What input, output, prompt, log, audit, and record is kept; for how long; why; and how deletion or preservation works.
- Cost
- Contract, use, staffing, oversight, incident, exit, and replacement costs tied to public records.
- Incidents
- Known failures, harms, complaints, corrections, notices, response owners, and changes made.
- Suspension authority
- Who must pause or end use, which triggers apply, how affected people are told, and what fallback service continues.
Emergency boundary
This website does not dispatch help or issue alerts.
For an emergency, call 911 and use alerts and instructions from official public agencies.
A future city website could explain preparedness and link to official agencies. It must never imitate a 911 call, current incident status, evacuation order, alert enrollment, responder location, or guaranteed delivery.