Have you been wronged by TAPS?

UC Davis Transportation Services makes decisions that can cost students time and money. We’re collecting documented experiences with citations, permits, temporary tags, payment apps, and appeals to identify patterns and push for specific reforms.

“TAPS” is the commonly used legacy name for UC Davis Transportation Services. This independent project is brought to you by the UC Davis Minecraft Server community and is not an official UC Davis website.

Minecraft-style campus portrait with a diamond helmet and UC Davis scenery
Brought to you by the UC Davis Minecraft Server ↗
01 Document first
02 Protect identities
03 Publish patterns
04 Demand reforms

THE QUESTION

Is this one bad experience, or a repeatable system failure?

Strong claims require records. We are separating firsthand reports, supporting documents, official data, and unresolved allegations.

A
FIELD 01

Citations and registration

Expired-tag allegations, temporary plates, recently purchased vehicles, permit-to-plate mismatches, and citation photographs.

B
FIELD 02

Payment and app failures

Duplicate charges, incorrect zones, unavailable payment systems, delayed confirmations, and citations issued despite payment.

C
FIELD 03

What this project is

An independent project collecting detailed firsthand reports and supporting records, then reviewing them for recurring patterns. Public findings will distinguish documented facts, corroborated trends, and unresolved allegations.

SHARE YOUR EXPERIENCE

Tell us exactly what happened.

Reports are sent through a protected server endpoint into a private, access-controlled database. Vercel BotID and server-side rate limits reduce automated abuse, and the public website cannot read submissions.

01Protected intakeBotID and strict validation
02Private reviewAccess-controlled database
03Public patternsAggregate or redacted findings
Protect yourself.

Do not send your student ID, driver’s-license number, home address, financial information, or unredacted plate/VIN. Citation numbers are optional.

Read the privacy and retention policy →

PRIVATE INTAKEACCESS-CONTROLLED
Connectivity context
How may this report be used?
Optional background and contact

Contact details and employment status stay private and are never published automatically.

Protected by Vercel BotID, strict validation, and private database access controls.

PUBLIC RECORDS

We’re asking for the system, not the talking points.

The targeted request covers citation volume and revenue, violation 4.31, dismissal rates, officer guidance, payment-system failures, vendor contracts, and appeal processing. It was sent to the UC public-records address on July 15, 2026. We will publish the response timeline and non-exempt records as they arrive.

Request sent · July 15
Scope
Two academic years
Privacy
Aggregate, non-personal records
Authority
California Public Records Act

PROPOSED REFORMS

Concrete changes, not vague outrage.

  1. 01
    Warning-first treatment

    For recent vehicle purchases, temporary registration, and first-time plate-to-permit mismatches.

  2. 02
    Evidence with every citation

    Provide photographs, officer notes, rule text, and the relevant payment or registration query.

  3. 03
    Publish accountability metrics

    Show citation, appeal, dismissal, collection, and app-failure data on a regular schedule.

  4. 04
    Student review

    Give students a formal role in reviewing parking-policy changes and recurring enforcement failures.