is weekend work out of scope?

No. An expectation the client never negotiated isn't a term you agreed to, and unspoken assumptions don't bind you the way written ones do. The default for independent professionals is business days, so the burden was on them to ask for weekend coverage and on you to price it — neither happened, which means it isn't in the deal. You can still choose to help out of goodwill, but choose it knowingly. The moment to correct the expectation is the first weekend request: a warm 'I'll pick this up Monday morning' resets the norm without any conflict, and it's far easier than unwinding a habit after months of quietly answering on Saturdays.

Enough that it's clearly a premium service and not just your normal rate with worse timing — a common range is fifty to a hundred percent over weekday rates, depending on how disruptive it is and how often it happens. The premium isn't greed; it's compensation for trading personal time and the opportunity cost of being unavailable to others or to rest. Pricing it visibly also does useful work: it signals that weekends are a real exception with a real cost, which naturally filters genuine emergencies from casual 'while you're at it' requests. If you find clients balking at the rate, that's usually a sign the request wasn't actually urgent enough to warrant a weekend at all.

Then keep that to yourself as a logistics choice, not a service offer. Plenty of freelancers do their focused work on a Sunday because it suits their life, but that's a private scheduling decision, not a commitment to weekend responsiveness for the client. The danger is letting it leak: if you reply to messages at 9pm Saturday, the client learns you're reachable then and starts expecting it. Protect the boundary by holding your replies until business hours even when you're working off-hours. Your working rhythm is yours to arrange; what the client buys is your stated turnaround on business days, and the two don't have to match.

It changes the practicalities but not the principle: you work your business days, and time zones are something to align on explicitly rather than assume across. If a client's Friday is your Saturday, that's worth naming in the contract so neither side is surprised — you might agree on overlapping hours or a shared definition of the working week. What you shouldn't do is silently absorb the mismatch by working your weekend to match their weekday. Raise it early, agree on a window that works for both, and write it down. Cross-time-zone work is completely normal; the failure mode is letting the gap quietly erode your days off because nobody discussed it.

Easily, if you frame it as availability rather than unwillingness. 'I'm offline on weekends but I'll have this to you first thing Monday' reads as professional structure, not a refusal — clients deal with vendor hours constantly and rarely take normal business hours personally. What damages relationships isn't holding a boundary, it's holding it resentfully or inconsistently, so that the client never knows whether a Saturday ask will be met with a yes, a no, or a sigh. Pick your policy and apply it steadily. A freelancer with clear, predictable availability is easier to work with than one who's technically always reachable but quietly burning out, and clients sense the difference over time.

Then it's stopped being a favor and started being scope creep, and you reset it the way you reset any creep — by naming the pattern. The trap is that each individual weekend ask feels too small to push back on, so you keep saying yes until 'sometimes' has quietly become 'always.' Catch it by treating the second or third request as the signal: 'Happy to have helped on that launch, but going forward I'll be handling weekend requests on Monday or at a weekend rate.' That sentence converts a drifting assumption back into an explicit choice. Generosity given once is a gift; generosity assumed forever is a discount you never agreed to, and you're allowed to take it back.