In this guide
Being experienced, trained and able to open a system are three useful facts. None, on its own, answers which decisions belong to you in a new assignment.
Start with the next decision on your desk
Instead of asking broadly whether you are “fully trained,” choose a real assigned task and identify its decision points. What may you prepare? What must be checked? Who may approve the outcome? What happens if the case does not fit the ordinary instructions? Ask these questions through your actual supervisor or designated training route.
Phoenix Planning and Development links publicly to technical policies, processes and interpretations. Those documents can help explain a service context. Reading them does not confer an employee’s delegated authority to decide a matter or replace the current internal instructions for an assigned role.
Use a short decision inventory
For a few recurring duties, record the action, required review and source of authority in an approved workplace location. Include a date because a temporary supervision arrangement may change. Avoid inventing a comprehensive permissions matrix that has never been reviewed by the employer.
Mark an unresolved permission as a question rather than guessing from what a colleague can do. A colleague may hold different duties, credentials or delegations. Even an identical job title does not establish that your first-week assignment has the same decision scope.
Worked hypothetical: from preparation to approval
Imagine a newly reassigned employee helping prepare a plan-review summary. They know the software and have handled similar documents elsewhere. Their first draft is complete, but they are unsure whether they may send the result directly to the customer.
The employee asks the assigned reviewer to confirm the release step. The reviewer explains the applicable approval route. The employee records that their current assignment covers preparation and that release requires the specified approval. The scenario is fictional; it does not describe a Phoenix position’s actual authorization or review standard.
The useful early output is a correctly routed draft. Speed gained by skipping review would not show readiness. Later, if the employer expands the assignment, the employee updates the decision inventory with the new scope and effective point rather than relying on memory.
Treat access as a separate check
The public ITS page describes identity management and technology support. If needed access is missing or old access remains, use the authorized workplace route. Do not borrow an account, share credentials or ask an unofficial website to inspect the problem.
Being able to click a control is not proof that using it is appropriate for your role. Conversely, lacking a permission can be a readiness blocker rather than a reason to work around the system. Describe the assigned task and blocker without exposing confidential case contents to an unrelated recipient.
Review one completed cycle
At a suitable employer-led check-in, walk through one piece of work from assignment to acceptance. Ask where your understanding was correct and where the decision route differed. This produces more useful evidence than a claim that you have “learned the system.”
End with three clear statements: what you may do independently, what still requires review and which unresolved boundary needs an official answer. Moving between field and office work adds the issue of skills that transfer while permissions do not. Temporary assignments require the same check when you are covering a different role for only a short period.
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 Planning and Development
Department mission and public links to technical documents and process improvements; those public resources do not authorize an individual employee to decide a case.
- City of Phoenix Information Technology Services
Public description of City technology, identity management, employee IT assistance and project functions; no private access workflow was tested.