When worklife
changes.

Useful output: A three-part event file: facts, requested actions, and administrator confirmations.

Scope limit: Preparation only. No eligibility decision, filing deadline, benefit election, or submission is made here.

• Before contacting the office: Build a private evidence index with document type, issuer, relevant date, and availability. Ask the Health Benefits Office which event, form, and timing apply; do not calculate a deadline from this checklist.
• Preparing or submitting the request: Match each requested attachment to its stated purpose. Check signatures, required pages, and the approved destination, then keep a copy or reference for the version actually submitted.
• Checking the response: Distinguish delivery from acceptance and final confirmation. Compare the confirmed people, record, and effective date with your request, and ask about any unanswered item.

Useful output: A letter-reading sheet with distinct dates, affected people, and unanswered questions.

Scope limit: The tool does not decide qualifying-event status or recommend starting, cancelling, or continuing coverage.

• Before contacting the office: Read the letter for the people affected and the stated coverage-end date. Mark missing or ambiguous details and ask the issuer for clarification if needed; avoid substituting the last day worked.
• Preparing or submitting the request: Use the current instructions for the particular City request. Keep a continuation notice or another program application in a separate file with its own administrator and next step.
• Checking the response: Check whether the response confirms receipt, accepts the evidence, or states an outcome. Preserve unresolved effective-date questions rather than interpreting a card or deduction alone.

Useful output: A current-document index and a list of answered, pending, and submitted items.

Scope limit: No plan ranking, cost projection, provider guarantee, or eligibility recommendation is generated.

• Before contacting the office: Create a question list tied to document titles and sections. Resolve conflicting years or versions before comparing details, and ask the administrator what election process is available to you.
• Preparing or submitting the request: Review the chosen request for clerical accuracy: intended people, requested coverage description, required signatures, and current attachments. Keep plan questions separate from City submission questions.
• Checking the response: Compare the final confirmation with your submitted request. If a paycheck later raises a question, make a separate period-specific payroll inquiry without treating the entry as a benefits determination.

Useful output: A leave-conversation agenda with named contacts, known dates, and unresolved questions.

Scope limit: This is administrative preparation, not medical advice or a determination of leave, pay, protection, or state PFML coverage.

• Before contacting the office: Prepare separate questions about attendance, pay, and the named leave process. Ask the administrator which City, bargaining-unit, federal, or state process applies; do not assume that one program covers another.
• Preparing or submitting the request: Confirm the current forms, submission channel, required information, and method for reporting schedule changes. Give a supervisor the operational handoff and route confidential records only as instructed.
• Checking the response: Record what was requested, submitted, and determined as separate states. Check that a response addresses the actual schedule, and retain any payroll or benefits question as its own open item.

Useful output: An operational handoff grid and first-day verification list.

Scope limit: The checklist does not approve a transfer, work location, schedule, device, or security permission.

• Before contacting the office: Make an ownership grid with current state, requested or confirmed state, responsible contact, and evidence of completion. Keep proposed changes visibly separate from approved instructions.
• Preparing or submitting the request: Check arrival arrangements, authorized access, equipment handoffs, and timekeeping approval. Ask about a blocked task rather than requesting broad access or borrowing another person's credentials.
• Checking the response: Verify the first-day sequence against actual use. Close only items with an observable confirmation, and give remaining items a specific next action and responsible contact.

Useful output: A commuter administration note with program, requested action, relevant period, and confirmation.

Scope limit: No fare comparison, subsidy calculation, tax advice, or employee-program eligibility determination is supplied.

• Before contacting the office: Keep route research separate from employer-program administration. Identify whether you need enrollment instructions, a status check, a modification process, or cancellation instructions for a future order.
• Preparing or submitting the request: Confirm the accepted request channel, applicable period, and what acknowledgment to retain. Ask separately about delivery, pickup, activation, or payroll if those are the actual obstacles.
• Checking the response: Compare the confirmation with the intended program and period. If a payroll line is unclear, prepare a two-period comparison and ask the responsible office to explain it.

Useful output: A period-specific inquiry with one unexplained entry and its supporting reference.

Scope limit: No amount owed, tax treatment, payment instruction, or correction entitlement is calculated by this tool.

• Before contacting the office: For a paycheck, compare the same label and column across relevant periods. For a separate bill, record the statement date and coverage period separately, then verify its official contact route.
• Preparing or submitting the request: Ask a narrow explanation question with the current reference. Confirm which document portions the office needs before sending a full paycheck or unrelated leave records.
• Checking the response: Compare the office's explanation with the original question and the subsequent record. A transaction receipt, deduction, and benefits determination remain separate pieces of evidence.

Useful output: A minimal first-contact note and a separate list of formal-process requirements.

Scope limit: The tool does not provide medical or legal advice, determine eligibility, or approve a workplace adjustment.

• Before contacting the office: Prepare one question about the correct accommodation process. Use the current category-specific instructions, and record the task and barrier without guessing a professional assessment or duration.
• Preparing or submitting the request: Record the current form, designated recipient, and requested documentation. Keep possible adjustments labeled as discussion ideas and distinguish an initial routing inquiry from a formal submission.
• Checking the response: Distinguish contact arrangements, a submitted request, and an official response. If something is approved, compare implementation with the actual instructions and ask about any mismatch.

Useful output: A minimal contact plan with a private response method and one clearly stated question.

Scope limit: The desk is not counseling, clinical advice, or emergency assistance, and it does not promise a service outcome.

• Before contacting the office: Verify the current EAP contact on the official page. Prepare a minimal inquiry about the service or an initial conversation, without turning the first message into a personal history.
• Preparing or submitting the request: Ask about current appointment arrangements, the service scope, and how confidentiality works. If attendance or a formal workplace request is involved, identify its separate administrative route.
• Checking the response: Keep a small logistics note: contact made, callback or appointment arrangement, and next step. Do not treat the support conversation as a leave submission or accommodation determination.