In this guide
A person may say “I need the records” when they really want to understand a decision. Another may ask “Why did this happen?” while looking for a specific report. Employees who help navigate public information need to recognize the difference. A records request and a general service question can be related without being the same task.
Identify the material being sought
Ask what existing document, correspondence, report or other record the person is trying to locate. A useful description can include subject, approximate period and the relevant program. It should not require the person to know an internal filename. The aim is a clear scope, not a test of their familiarity with City organization.
Phoenix's Citywide Public Records page directs readers to the citywide process and separately identifies Police and Municipal Court routes. That distinction is important when helping someone find the official starting point. This publication does not receive requests, decide disclosure questions or promise a response time.
Separate a record from a new analysis
An existing report may answer a question, but a request for a custom explanation can involve a different service. A frontline employee should avoid promising that a records process will create a new calculation or a new narrative. Instead, help the person identify the material they believe exists and the separate office that may explain a program.
For an invented example, a reader wants to know how a fictional facility project was funded. They might seek a named budget table, a Council report or a contract record. Asking for those identifiable materials is more precise than requesting “everything that proves the project was a good idea.”
Reduce ambiguity without narrowing the person's rights
Offer neutral clarification about subject and period. Do not pressure someone to abandon relevant material or tell them that a request is invalid based on this article. Legal requirements, exemptions, fees and retention questions belong with authorized records staff and the applicable law.
A useful assistance note describes the clarification made and the official route provided. Avoid collecting unnecessary personal details or copying sensitive information into an informal notebook. The official process should handle the data needed for the actual request.
Keep public navigation separate from employee systems
eCHRIS is an employee-system context, not a public-records submission route. A resident's request should not be redirected to an employee login, and a public records discussion should not prompt a worker to share private HR screenshots. Use the published City route and current departmental instructions.
The best outcome of this short conversation is a clearer description of the sought material and a verified official destination. It is not a disclosure decision made at the counter. That boundary protects both useful service and the integrity of the records process.
Sources and limits
Official public sources checked October 5, 2026. Examples and exercises are original editorial illustrations, not City records or instructions.
- Citywide Public Records
Public records routes, including separate Police and Municipal Court routes. No disclosure or retention determination.