ZAMBO.

Direct answer

An earlier deadline is a new job at a new price. Sell it like one.

Nobody argues when an airline charges more for the last seat on an earlier flight. Time is part of the product. When a client moves your deadline earlier, they are buying more of it, and the whole fix is to answer with a priced choice instead of a sigh and a late night.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 22, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on publication day.

Step 1. Name the move for what it is: a change

The agreed job has three legs: the work, the price, and the date. Moving any one of them is a change to the job, and changes are priced and accepted before they happen. Deadline moves feel smaller than scope changes because the work itself looks identical, but the cost is real: other clients rescheduled, evenings handed over, checking done under pressure. The moment you treat the move as a change, the conversation has a shape both sides already know from every other trade: here is what changed, here is what it costs, accept it and it starts.

Step 2. Answer with the two-door choice

One short message, every time: the original date at the original price, or the new date at the original price plus the rush fee, stated as a number. Two doors, both open, client picks. The choice works because it never says no: the client can always have the earlier date, at the price the earlier date costs. It also ends the negotiation about whether a rush fee is fair in the abstract. The client is not buying your reasoning. They are buying a date, and the date has a price tag on it. Send the choice in writing and wait for the pick before a single rushed hour happens.

Step 3. Get the new date and the new price accepted together, before the rush

A rush agreed in a hurry, in words, is a fee dispute scheduled for delivery day. Get one written acceptance that carries both halves: the new date and the new total. An email reply works. A change note on the delivery record is better, because it sits with the work. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-24), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The job is then delivered as a handover the client checks and accepts, and the two public records below show what that acceptance state looks like:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the two cards together. The accepted record shows a client decision made and dated against the work itself: 4 of 4 steps checked, release_hint ok_to_release. The pending record shows work fully checked, 5 of 5 steps, with the decision still owed. A deadline change accepted the same way, on the record, cannot later become an argument about which date or which price was agreed, because the record holds the work, the date it was saved, and the client's decision in one place.

Step 4. Offer the partial early delivery when the full rush is refused

Sometimes the client needs one piece early and the rest on schedule, and only discovers that when the full rush price lands. Offer it deliberately: the critical piece by the early date for a smaller rush fee, everything else on the original date at the original price. The partial door protects the relationship without giving the rush away, and it teaches the accurate lesson: earlier costs more in exact proportion to how much earlier and how much of the job moves. What it must never become is the whole job early at the partial price. The scope of the early piece is written down like any other change.

Step 5. Invoice the rush as its own line, the moment it is delivered

Put the rush fee on the invoice as a separate line that names the change: rush fee, deadline moved from the original date to the new date, accepted on the day it was accepted. A named line is hard to dispute and easy to approve, because it points at a decision the client remembers making. A quietly inflated total invites the client to re-open the whole price. If the fee is disputed anyway, the file is already assembled: the agreement with the original date, the written choice you sent, the acceptance of the new date and price, and the delivery record showing delivery on the new date.

Step 6. Print the rush rate in the next agreement

The permanent fix is one paragraph in the agreement: the delivery date, a line stating that an earlier date is a change, and the rush rate, as a percentage or a fixed fee, with the trigger written down. Clients who have seen the rate in advance rarely argue it in the moment, because the argument was settled when everyone was calm. Repeat movers are also telling you something useful about their planning, and the printed rate is how their planning problem stops becoming your unpaid overtime.

What a record does not settle

A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the work was good, does not set your rush rate, and cannot make a client accept a change they never agreed to. The agreement, the written change, and the acceptance state settle what was promised and when. This page is general information, not legal advice.

Frequently asked questions

My client keeps moving the deadline earlier. How do I charge for rush work?

Treat every earlier deadline as a change to the job, because that is what it is: the same work in less time costs more to produce, in evenings, in rescheduled clients, and in risk. Answer each move with a choice, not an argument: the original date at the original price, or the new date at the original price plus the rush fee. State the fee as a number, in writing, before the rush starts, and get the client to accept the new date and the new price together, in a reply or on the delivery record. A rush fee agreed after the work is delivered is a negotiation you will lose, because the urgency that justified it is gone. If the client will not pay it, the original date stands, and you can still offer a partial early delivery of the piece they need most at a smaller fee. Put your rush rates in the agreement for the next job, printed in advance, so the next moved deadline prices itself.

How much should a rush fee be?

There is no standard rate, and anyone quoting one is guessing. Pick the shape that matches how you work and use it consistently: a percentage added to the job price, a fixed fee per job, or a higher hourly rate for the rushed hours. The honest test is what the rush actually costs you: hours moved from other clients, evenings and weekends, and the risk premium for work checked under time pressure. A fee that covers none of that is a favor with an invoice attached. Whatever shape you pick, print it in the agreement before any deadline moves, with the trigger written down: work needed sooner than the agreed date is rush work at the stated rate. A rate the client saw at the start is a term of the job. A rate invented mid-panic is an argument.

What if the client refuses the rush fee but still wants the earlier date?

Then the earlier date is the thing being refused, not your fee. Hold the original date calmly and in writing: the agreed delivery date stands at the agreed price, and the earlier date is available the moment the rush terms are accepted. Offer the middle door if one honestly exists: the single most urgent piece delivered early for a smaller rush fee, with the rest on the original date. What you do not do is absorb the rush silently, because a silently absorbed rush teaches the client that deadlines move for free, and the next deadline will move earlier still. If the client says the earlier date was always the understanding, the agreement and the change record settle it: the original date in writing beats a memory of a call, which is why every accepted move gets written down when it happens.

How do I record a deadline change so it cannot be disputed later?

Write the change down as its own small record at the moment it is agreed: the original date, the new date, the price change, and the client accepting both. An email reply that says yes to a message stating all four is enough; a change note attached to the delivery record is better, because it sits with the work itself. When the work runs through Zambo, the job is delivered as a handover the client checks and accepts, step by step, so the delivery date on the record and the acceptance state are facts neither side has to reconstruct from chat threads. Disputes about deadlines are almost always disputes about which date was agreed, and they end the moment a dated record shows the original date, the move, and the acceptance of the move in one place.

How do I stop deadline creep on the next job?

Price time in the agreement itself. State the delivery date, state that an earlier date is a change, and print the rush rate next to both, so the client can see the cost of moving the date before they ask. Deliver in stages with an acceptance at each stage, so a deadline move lands on one stage at a time instead of repricing the whole job at once. And when a client moves a date, answer with the choice every time, original date at the original price or new date at the rush price, until the pattern teaches itself. When the work runs through Zambo, every step is saved as it happens and the client gets one handover link to accept or flag, so the schedule and its changes sit on the same record as the work. For $0.99, run the next rush job on a record where the date, the change, and the new price are saved before the work starts: get the Day Pass. A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related