In this article
A time-away request, an approval and a recorded absence are different events. Keep each visible rather than assuming one proves the others. For an actual City and County of San Francisco leave question, begin with your department’s established personnel route and the Department of Human Resources employee-leaves page, which directs readers to SF | My Portal. This guide helps you organize the conversation; it does not determine your leave eligibility, a required form, a deadline or a right to payment.
Start with the question, not a category guess
Employees often know the practical situation before they know the administrative label. You may need time away, a changed schedule or clarification about an existing record. Describe the work-related question clearly through the authorized channel. If the correct category is uncertain, ask the responsible personnel contact to identify it rather than selecting a label because it sounds closest.
There is a difference between providing enough information for routing and broadcasting sensitive details. A supervisor may need to coordinate coverage while an authorized personnel team handles a separate review. Ask who needs which information. Do not assume that every person copied on a scheduling message needs the supporting documents associated with a leave matter.
Build a simple status trail
For your own coordination notes, use distinct words for distinct stages. “Prepared” means you have gathered what you intend to submit. “Sent” means you used the instructed route. “Received” means the relevant recipient acknowledged it. “Decision communicated” means you have an answer from the responsible decision-maker. “Record checked” means you reviewed the relevant official record afterward. These are editorial labels, not a description of buttons or statuses in a City system.
The point is to prevent an ambiguous phrase such as “all set” from carrying several meanings. If someone says the paperwork is complete, ask which part is complete and whether another action remains. A clarification can be brief: “Does this confirm the decision, or does it mean the request is ready for review?”
- What exact dates or work periods does the request concern?
- Who owns the next review or decision?
- What instruction governs the next step?
- What response or record will tell you that stage is complete?
Make coverage planning a separate conversation
A work-coverage plan explains how responsibilities will be handled. It is not, by itself, a leave decision. Similarly, an approved absence does not automatically tell colleagues who will receive a recurring report or monitor a shared queue. Keeping the conversations separate reduces both confusion and unnecessary disclosure.
For coverage, list the work that cannot wait, the approved alternate owner and the location of the current instructions. Distinguish a routine task from a decision that requires particular authority. A colleague who can prepare a document may not be authorized to approve it. Do not solve a coverage gap by sharing credentials or asking someone to act under your identity.
Use neutral scheduling language in broad team communications. Personal explanations belong only where they are required and appropriate. An operational handoff can state when a task moves to another owner without describing the private reason for the absence. The role-transition guide explores that distinction in more depth.
A hypothetical status misunderstanding
Hypothetical example: an employee sends a proposed absence to a supervisor and arranges a colleague to cover a weekly task. The colleague says, “I have it covered,” and the employee treats that message as confirmation of the whole request. A later conversation reveals that the administrative review is still separate.
The useful correction is not to decide who should have guessed what. It is to write down the two open questions: whether the proposed absence has the required decision, and whether the task handoff is operationally ready. The employee asks the established personnel contact about the first and the supervisor about the second. One answer can be complete while the other remains pending.
Check a record without turning it into a diagnosis
When reviewing an official time or leave record, identify the relevant dates and the displayed entry. If the entry differs from your understanding, preserve the distinction between what you see and what you expected. The discrepancy might need an explanation, a different record or a correction. You do not have to decide which before asking the responsible team.
A concise message can state, “The record for these dates shows this label. The instruction I received referred to a different description. Which record should I use to understand the status?” Avoid making your own retrospective edits simply to make two documents look consistent. Ask what the authorized correction process is.
Where a pay question overlaps with time away, treat that as an additional question with its own responsible contact. A time record and a pay statement do not become interchangeable because they concern the same dates. Our pay-statement review explains how to frame the observed difference without claiming a cause.
Plan the return as carefully as the departure
A return can involve more than being present again. Ask the appropriate workplace contact what operational handoffs remain: recurring meetings, task ownership, equipment or permissions, and any instructions that changed while you were away. Do not assume that a colleague’s temporary access should continue, or that your earlier access should be restored without review.
For your coordination notes, close each item with the actual result. “Coverage ended and the task owner confirmed receipt” is clearer than “back to normal.” If an administrative record remains unresolved, keep that item open independently of your return to work. This prevents a practical transition from hiding an unanswered record question.
The aim is a small, reliable trail rather than a second personnel system. Keep only the notes you are permitted to retain, use approved locations, and follow the current instructions from the responsible team. A clear change record can help you remember what is pending without treating an informal checklist as official authorization.
Sources & scope
Public sources checked October 27, 2026. Sources establish only the limited public facts described above. The working methods and labeled hypothetical examples are original editorial analysis, not official City procedures or individual advice.