Published by Tomi
PUBLIC WORK / ORDINARY DAYS
NO. 01 — SAN FRANCISCOClearer questions. Smaller handoffs.
Room for the work that matters.
THE ORIENTATION
SF Employee Portal, SF My Hub, SF | My Portal: a familiar label does not tell you which record, decision or person you need. Begin with context, then choose the next useful action.
Read the opening guide →AN EDITORIAL DISTINCTION
Sent ≠ settled.A request, its receipt and a verified result are different events. Keep the next owner visible.
Follow a change through →THE DAYBOOK / NINE PRACTICAL READS
Pay, time, benefits, contact records and transitions. Read for the decision in front of you, not for another set of sign-in instructions.
9 articles
Orientation
Understand the municipal employee context, choose an official starting point and separate access from the workplace question behind it.
Read the article : SF Employee Portal: find the official route, then name the workPay & records
A careful way to turn an unfamiliar pay entry into a precise payroll question, without guessing what the record means.
Read the article : Read a pay statement before drawing a conclusionTime & coordination
Organize time-away questions around the request, the responsible decision-maker and the record that confirms what happened.
Read the article : Keep a time request separate from an approved recordBenefits literacy
Separate enrollment, coverage and payment questions, then prepare only the context the responsible benefits contact needs.
Read the article : Ask a benefits question that can be routed correctlyLife changes
Plan an address update around the responsible record owners, the right address type and evidence of completion.
Read the article : Treat an address change as a set of records to verifyTransitions
A practical handoff method for a new assignment, a department change or a departure: work ownership, permissions and unfinished questions.
Read the article : Leave a usable handoff, not a trail of loose accessCommunication
Describe the observation, the task and the next answer you need without sending a full employee record to the wrong place.
Read the article : Write a support brief that protects the private detailsRecords
A practical method for limiting copies, verifying recipients and keeping working notes separate from official employment records.
Read the article : Keep employee documents useful without spreading themFollow-through
Keep the request, its owner and the evidence of completion separate in a small, purpose-limited working note.
Read the article : Track a change without building a second personnel fileA NOTE TO KEEP
Name the task. Separate the observation from the assumption. Identify the authorized recipient. Ask for one next action.
Write a safer support brief →THE LOCAL QUESTION EXERCISE
Choose a work topic and the kind of answer you need. This local exercise suggests what to clarify before contacting your authorized department, HR or payroll team. It does not diagnose an account, calculate pay, determine eligibility or send a request. No private details are needed; nothing is saved or sent.
For a possible payroll correction, first distinguish the pay period from the payment date. For benefits, distinguish the election from coverage confirmation. For a role transition, distinguish responsibility from access. These are editorial prompts, not official product procedures or decisions.
Reset clears every choice. Read the support brief for a full example. This exercise has no connection to City systems, your employer or your records.
RECORDS BELONG IN THE RIGHT PLACE
No employee sign-in. No private-document uploads. No account services. Read our editorial method or learn how to keep documents useful without spreading them.