Because your time off has real, quantifiable value: rest, family, errands, exercise, and the recovery that makes your weekday work possible at full quality. Working weekends also carries hidden costs — fatigue that slows the following week's output, the opportunity cost of everything else you could have done, and the slow erosion of boundaries that leads to burnout. The 1.5× norm (borrowed from overtime conventions like "time and a half") prices that scarcity; it is not a penalty on the client, it is the market price of your least flexible hours. Freelancers who don't charge it aren't being generous — they're subsidizing clients with their health.

They are long-standing industry norms: 1.5× ("time and a half") for weekends/overtime and 2× ("double time") for holidays appear across freelancing rate guides, contractor norms, and employment overtime conventions in many countries. Both are adjustable in the calculator — they are starting points reflecting common practice, not legal requirements. Some freelancers go further: 2× weekends is common among in-demand specialists, and 2.5–3× holidays appears in agency rate cards. The "right" multiplier is the one that makes you genuinely indifferent between working and resting — if you'd still resent the weekend work at 1.5×, your multiplier is too low.

Put it on your rate sheet before it ever comes up: "Weekend work is billed at 1.5×, public holidays at 2×." When quoting, state it as fact, not apology: "This timeline needs 8 weekend hours, which we bill at the weekend rate of $112.50/hr." Clients accept published policies; they resist surcharges that appear invented for their project. If a client pushes back, don't defend the multiplier — offer the alternative: "Happy to do it on weekdays at the standard rate; the timeline moves to Friday." Framed as a choice between two legitimate options, the premium stops feeling like a penalty and starts feeling like what it is: the price of speed.

Whatever your contract says — and that's the point. Define it explicitly: public holidays in your country, plus any religious or personal observances you keep. If you observe holidays your clients don't (Eid, Diwali, Lunar New Year, or simply your family's fixed vacation week), naming them in the contract avoids the "but it's a normal Tuesday for us" argument entirely. Attach the list as a schedule to the contract so it can be updated yearly without renegotiating the whole agreement. Ambiguity here is where disputes start; a dated list is where they end.

Then the work happens on weekdays, on a weekday timeline — the premium is the price of your off-hours, so declining it just moves the deadline. Frame it as a choice: "I can deliver Friday at the standard rate, or Sunday at the weekend rate." Most "refusals" evaporate when the alternative is waiting, because the client's urgency was real — they just hoped the urgency would be free. The rare client who truly can't pay and can't wait is telling you their planning failed; that's not an emergency you should subsidize. Hold the line kindly and firmly: every exception you grant teaches the market your policy is decorative.

Yes — convert first, then fold it in. Estimate the off-hours the project needs, price those hours at the premium rate, and either fold the uplift into the project price or itemize it as a line: "Weekend delivery premium: $600." Itemizing is usually better: it shows the client exactly what the urgency costs and gives them the lever to remove it ("actually, Monday is fine"). Our rush fee calculator handles the related case of compressed timelines — weekend premiums and rush fees stack, so price them as separate lines rather than one murky "urgency fee."

That's your call — many freelancers set a threshold (e.g. work after 8pm or before 8am counts at 1.25–1.5×) and publish it alongside the weekend/holiday schedule. Whatever you choose, write it down the same way: published, consistent, non-negotiable in the moment. Inconsistency ("sometimes I charge it") reads as arbitrary and invites haggling; consistency reads as policy and ends discussion. One practical tip: define "evening" by clock time in your timezone, stated in the contract — "after 8pm PKT" leaves no room for creative interpretation.

A short clause does it: "Standard hours are Monday–Friday, 9am–6pm [your timezone]. Work performed on Saturdays, Sundays, or the holidays listed in Schedule A is billed at 1.5× / 2× the standard hourly rate respectively. Rush timelines are quoted separately." Attach the holiday list as the schedule so it can be updated yearly. Add one more sentence covering the gray zone: "Work outside standard hours on weekdays is billed at 1.25×." Have the client initial the rate schedule — the physical act of initialing makes the policy feel agreed rather than imposed, which is exactly what you want if it ever matters.

They filter, not scare — and filtering is the point. Clients with genuine urgency pay the premium gladly, because it's cheaper than their delay (a launch slipping a week costs them far more than your $600 uplift). Clients without urgency accept the weekday timeline, which is also fine. The only clients "scared away" are the ones who wanted your weekends at weekday prices, and losing those is the policy working as intended. In practice, freelancers who publish off-hours rates report fewer weekend requests, not fewer clients — the policy trains the market to plan better, which improves your life without reducing your income.

Absolutely — the calculator allows up to 3× weekends and 4× holidays, and you should use that headroom if your life demands it. If you deeply value your time off (parents of young kids, caregivers, anyone with a packed life or health constraints), higher multipliers are honest pricing, not greed. The "norm" is a floor for the market, not a ceiling on your worth. A useful calibration: set the multiplier at the level where you'd feel genuinely fine about losing the weekend — if 1.5× still stings, try 2×. The premium isn't just compensation; it's a rationing mechanism that protects the hours you can't get back.