Stop putting vague scope like "additional revisions" in your contracts

Got burned last month when a client kept asking for tiny tweaks over 3 weeks and called them all "revisions." Now I spell out exactly how many rounds you get and what counts as a new one, saved me 10 hours on my last project.

4 comments

4 Comments

aliceharris27d ago

Has anyone tried adding a time limit instead of just a revision cap? Like I put in my contracts that all revisions must be requested within 14 days of delivery. That way if a client sits on something for a month and then comes back with a list, it's a new project not a revision. It stops that whole "we forgot to mention this earlier" game they love to play lol

the_cameron27d ago

Heard this exact same trick works for getting contractors to actually show up on time too.

rose_clark8120d ago

Combining both the time limit and a revision cap is the way to go. That 14 day window keeps them from sitting on deliverables forever, and the fixed number of rounds stops the death by a thousand cuts. Having both in there closed that whole loop for my workflow.

rose_clark8127d ago

Does a 14 day limit actually hold up if they claim they never got the delivery email?