A working-hours agreement is more than a start and end time in a contract. It tells the assistant when to be available, how quickly to respond, and what counts as urgent on a given day. It also tells the manager when the assistant is off and who covers the work in the gap. Writing the agreement before the first week prevents availability from being negotiated one message at a time.
Record the time zone before anything else
Write the assistant's home time zone and the client's operating time zone in the agreement. Include the offset that applies during the period of the engagement because daylight saving can change the overlap. A schedule that works in one season may fail in another. The agreement should name the dates when the overlap changes.
Convert the core hours into both time zones and show the overlap in plain language. A table with two columns is easier to use than a paragraph of explanation. The assistant and the manager should both confirm the same overlap. A mismatch here causes lateness that looks like a performance problem.
Record how the assistant will know about a time change. A calendar invitation, a shared team calendar, or a written notice all work if the owner is named. The agreement should not rely on someone remembering to mention the change. A recurring reminder before each daylight shift is a simple control.
Check the overlap against the client's actual meetings and review times. A role that supports a morning review needs the assistant available before that review starts. If the overlap does not cover the review, the agreement should say how the work reaches the reviewer. The schedule should follow the work rather than the other way around.
Define response windows for ordinary requests
Set a response window for ordinary requests, such as a reply within the same working day. The window should describe the first response, not the completed task. A quick acknowledgement tells the requester that the work has been seen and when to expect more. It reduces the follow-up messages that interrupt other work.
Separate the response window from the completion target. A task may need a reply in two hours and completion by the next morning. Writing both prevents an acknowledgement from being mistaken for a promise to finish. The requester should know which date refers to which outcome.
Name the channel where an ordinary request should arrive. A request sent to three channels is easy to miss and hard to audit. The agreement should say which channel is authoritative and what to do with a request that arrives elsewhere. The assistant should not be expected to monitor every channel at all times.
Record what happens when the volume exceeds the window. A queue that is longer than usual should have a visible status so the requester knows the delay is known. The assistant should not have to choose between silence and working late. A short delay notice is part of the agreement, not a failure.
Define urgent work narrowly
Write a short definition of urgent work and keep it narrow. A same-day payroll correction or a client deadline may qualify, while a routine report usually does not. The definition should use examples from the role rather than a general word such as important. A broad definition makes every request urgent and drains the schedule.
Name who may declare an urgent request and how the assistant should confirm it. A message marked urgent by someone outside the route still needs a decision. The agreement should say whether the assistant may act or must wait for the named owner. A clear rule prevents the assistant from being blamed for either choice.
Record the response expected for an urgent request and the trade-off it creates. If urgent work jumps the queue, the ordinary work moves later and someone should know. The agreement can say which tasks are paused first. Naming the trade-off keeps the priority decision visible.
Review urgent requests at the end of each week and ask whether each one met the definition. A pattern of false urgency may mean the intake route is too slow or the definition is too vague. The review should lead to a change in the process rather than a warning to the assistant. The goal is to protect the schedule for the work that truly needs it.
Plan the handoff for time off
Name a backup for planned time off before the assistant takes leave. The backup should know the queue, the review route, and the location of the current work. A name in a directory is not a handoff. The agreement should include a short checklist that the assistant completes before leaving.
Record which tasks can wait and which must continue during the absence. A task with a deadline inside the leave window needs an owner before the leave starts. A task without a deadline may pause, but the requester should be told. The decision belongs in the handoff note, not in a conversation at the end of the last day.
Ask the backup to confirm the handoff by reviewing the open items. A confirmation catches a missing file or an unclear next step while the assistant is still available. The confirmation should be written in the handoff note. A verbal assurance is easy to misremember.
Handle schedule changes without renegotiating everything
Write a short process for changing the schedule, such as a request made at least one week ahead. The process should name who approves the change and how it is recorded. A change that only exists in a chat message is hard to apply to payroll or planning. A simple form or calendar update is enough.
Distinguish a one-time change from a permanent change. A single appointment may need a swap, while a new school schedule may need a lasting adjustment. The agreement should say which approval and notice apply to each. Treating every change the same creates unnecessary friction.
Record the effect of a schedule change on the review queue and the client-facing work. A change that leaves no reviewer during a critical window needs a different plan. The manager should confirm the coverage before approving the change. The approval should include the coverage decision, not only the new hours.
Make the agreement visible and testable
Keep the agreement in one document and link it from the role-scope card. A schedule split across a contract, a chat, and a calendar is difficult to apply when a question arises. One source makes the current version obvious. The document should show the date it was last reviewed.
Ask the assistant to describe the ordinary response window and the urgent route in their own words during onboarding. A correct explanation is stronger evidence than a signature. The manager can correct a misunderstanding before the first real request. Record the explanation in the onboarding notes.
Test the agreement on a normal week before adding unusual work. A schedule that cannot survive an ordinary week will not survive a busy one. Note where the plan and the actual day diverged. Those notes are the first input for the next revision.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Cybersecurity and Infrastructure Security Agency — Secure Our World practical guidance on access control and account security.
Related reading
Build a role-scope card before a virtual assistant starts
A one-page role-scope card that names the tasks, the decisions, the tools, and the stop rule before a virtual assistant's first morning.
Write a first-month check-in script for a virtual assistant
A repeatable check-in script that surfaces blockers, review load, and role drift without turning the meeting into a status recital.
Create a mistake-review ritual for a new virtual assistant
A blame-free mistake review that separates the task defect, the instruction gap, and the review miss so the same error does not return.
