Price the ghost week before it happens

Fixed-price work pauses when client review pauses. Hourly work may pause billing but not opportunity cost: the slot you held cannot serve another client, and restart tax applies when feedback finally arrives weeks later. Feedback delays are structural risks like bad legacy code. Price and contract should reflect them or you donate calendar.

Write feedback windows, a pause clause, holding/reserved capacity language, revision-round limits, and a rush-recovery fee into the estimate and SOW before kickoff - not after resentment. Measure calendar cost of waiting, not only hours logged. Do not wait until a ghost month to invent terms.

Feedback window clauses you can paste

Use language like this (adjust numbers to your market; clarity matters more than the exact day count):

Estimate assumption: "Assumes consolidated feedback within three business days per milestone. Delays shift the delivery date one-for-one unless a rush fee applies to compress later work."

Pause clause: "Project clock pauses after five business days awaiting client input. Resume on feedback; timeline extends by pause length."

Holding / reserved capacity: "Reserved capacity billed at fifty percent of day rate after ten idle business days unless release of the hold is agreed in writing."

Revision rounds: "Two consolidated revision rounds included per milestone. Round three and beyond are change orders at the stated hourly rate." For the mid-project "can we also" script, see how to raise a freelance change order without awkwardness.

Rush recovery: "If the client compresses the remaining schedule after a feedback delay attributable to the client, a rush fee of twenty-five percent of remaining fees applies, or the delivery date extends without rush."

Single decision-maker: "Estimate assumes one named approver. Committee review without a named owner is scoped as additional discovery or hourly coordination."

Asset gate: "Work on a milestone starts after the asset checklist is complete (copy, logos, access, legal text). Incomplete assets count as waiting on client."

Write the assumptions in the estimate PDF and the SOW. Memory is not a contract when tension rises.

Worked delay cost example

Assumptions for this worked example (label them as assumptions, not industry averages):

  • Your effective day rate for capacity planning: $800 / day (whatever you use internally from calculate a freelance hourly rate math).
  • You reserved four days for milestone B after delivery of staging.
  • Client was expected to return feedback in three business days.
  • Feedback arrives after eleven calendar days (eight business days of wait beyond the three-day window = five extra business days waiting, then two days of rework from late notes).

Rough holding cost if you kept the slot empty:

  • Extra wait beyond window: 5 business days × $800 = $4,000 of blocked capacity (opportunity cost), whether or not you billed hours.
  • Restart / rework after ghost week: assume 1.5 days × $800 = $1,200 (reloading context, re-testing, addressing conflicting comments from three stakeholders).
  • Total structural cost in this example: about $5,200 before you "only" billed a few check-in hours.

Fixed price without pause terms absorbed most of that. Hourly without a retainer still lost the slot to other work you could not book. Neither matches blocked capacity unless priced upfront.

Shorter email you send on day six of silence: "Milestone B waiting on input since DATE; per pause terms the delivery forecast moves to DATE_Y. Reply with consolidated feedback or confirm release of the hold."

Hourly, fixed, and retainers under slow feedback

Fixed price versus hourly when each works: chronic slow feedback favors hourly with a minimum retainer for reserved capacity, or fixed with explicit pause clauses. Fixed without a pause clause means you finance their internal chaos.

How much buffer a freelancer needs already treats client feedback as a schedule line item. Put the specific windows and pause language here; keep buffer math on that page. Clients who consistently slow-walk feedback should pay a higher effective rate or a retainer covering held slots - not a silent discount.

Mutual SLA on retainers: you respond within X hours during posted hours; they return feedback within Y business days. Breach of their window pauses your deliverable clock.

Time zones, committees, and missing assets

Client approvers in other zones may read email only at their morning. Your Friday afternoon delivery becomes their Monday review by physics. Price calendar days in assumptions, not only your business days.

Committee review without a named owner is a risk multiplier. Charge discovery time to map the approval graph before a fixed quote. Example: copy delivered Monday; brand, legal, and founder respond on different weeks - you assumed one round in five days. Next phase: retainer with a defined review window and pause billing, or hourly with a weekly cap and waiting-on-client status lines.

Delay often hides missing logos, copy, or legal text. The asset checklist is a start gate, not a nicety.

Proactive nudges, release of the slot, and rush

Status updates that chase approval are work. End of day status update habits help clients see blockers; if chasing is frequent, include communication hours in the estimate or retainer.

If pause exceeds the agreed threshold, offer to release the hold and rebook at the next available start. Document in writing: waiting since X; forecast now Y; hold released or holding fee applies.

When the client compresses after slow feedback, rush fee covers displaced work - congestion pricing, not punishment. Empathy for their internal conflict is fine; absorbing infinite delay is not. Endless delay without pause pay is a client-fit problem - raise terms or exit on renewal rather than subsidizing chaos forever.

Second worked example: three-approver ghost month

Assumptions: fixed-price milestone fee $6,000; your internal day rate $800; you assumed one approver and five business days for feedback; actual path is brand + legal + founder across eighteen business days; you kept the next milestone slot half-open "just in case."

Calendar cost sketch:

  • Idle beyond the five-day window: 13 business days × $800 = $10,400 opportunity cost if the slot stayed reserved.
  • At fifty percent holding (pause clause): 13 × $400 = $5,200 if you had that term - still money, but honest.
  • Without pause terms you absorbed the wait and then accepted a rush to "make the launch." Rush without fee displaces another client or your buffer week (how much buffer a freelancer needs).

After this once, the next quote includes: named single approver or +15% coordination; five-day feedback window; pause after five; holding fee after ten; rush fee if they compress. You are not being difficult. You are refusing to finance their committee with your calendar.

Document every delay in a short email the day the window expires. Silence teaches clients that windows are decoration.

What to put in the estimate PDF (checklist)

Before you send a fixed quote, confirm these lines exist in writing:

  1. Feedback window in business days per milestone
  2. Pause trigger day count
  3. Holding / release rule for reserved capacity
  4. Included revision rounds and change-order rate
  5. Rush fee if they compress after their own delay
  6. Named approver or extra coordination fee
  7. Asset checklist as start gate
  8. Timezone note: calendar days vs your local business days

If any line is missing, you are negotiating from memory later. Memory loses. Buffer and schedule assumptions belong with how much buffer a freelancer needs; rate math belongs with calculate a freelance hourly rate.

Client feedback delays belong in pricing as assumptions, pause terms, buffer in rate, and release of idle slots. Measure calendar cost, not only hours logged.