In this guide
A person can want a service action, an explanation of a status or access to an existing record. Those are related interests, but they are not the same request. Choosing the right route helps the responsible function understand what is being asked and limits unnecessary sharing.
Phoenix’s Citywide Public Records page identifies its public records route and directs Police and Municipal Court records to their respective departments. myPHX311 provides public service categories. These official distinctions establish routing context; they do not decide whether a particular record must be disclosed or how long a request will take.
State the purpose before naming the document
If you want a condition addressed, a service-reporting route may be relevant. If you want to understand an existing case, use the official status or contact instructions. If you seek records, begin with the responsible records resource. Do not assume a records request will cause the underlying service action to occur.
The same applies inside the workforce. An employee-administration question belongs in the authorized employee process. eCHRIS is not a general public-records search engine, and this publication cannot access personnel records on a reader’s behalf.
Make the scope intelligible
A records inquiry is easier to understand when its subject, period and type of record are clear. Follow the official instructions rather than copying an overly broad template. This article does not recommend a legal strategy, determine exemptions or promise that a particular document exists.
A fictional reader studying a public program might first ask where already-published reports can be found. That can answer the question without a new records request. If the reader needs something different, the official records page explains the available route. No actual request has been made by this example.
Do not attach unrelated private information
The desire to explain a problem can lead someone to include more material than the route needs. Avoid sending personnel, health, financial or credential information merely to demonstrate that a question is serious. Use the authorized instructions for any necessary personal information and the proper destination.
Employees discussing a process for training should use invented records or approved public material. Removing a name from a real case does not automatically make the remaining details appropriate for public discussion.
Keep an outcome question separate
Receiving a document is not the same as receiving the desired service outcome. A record can describe an action without proving that the action was correct, complete or satisfactory. Reading it requires attention to its purpose and context.
If a document changes your understanding, formulate the next question narrowly and send it through the appropriate official process. Do not assume the records staff are responsible for revisiting a technical decision simply because they supplied the document.
Use a three-way routing note
Write one sentence for each purpose: action requested, status explanation needed, record sought. Often only one sentence will apply. Keeping the purposes separate produces a clearer inquiry and helps workforce readers understand why different functions may be involved without turning the publication into an unofficial City help desk.
Read next
- A Complete Service Request Is More Than a Filled Form
- eCHRIS, Public Service Portals and the Work They Actually Hold
- Close the Service Loop with Evidence and a Clear Next Step
Sources and limits
Public sources checked October 5, 2026. Editorial examples are hypothetical; official instructions and case-specific decisions remain with the responsible City service.
- City of Phoenix: Citywide Public Records
Citywide records route and separate Police and Municipal Court destinations. No legal entitlement or response deadline determined.
- City of Phoenix: myPHX311
Public service categories and issue-reporting entry points. Not an emergency dispatch or employee HR interface.