How to Client-Proof Your Work Schedule
![]()
It’s a fact of freelance life that some clients just don’t really seem to understand the sort of schedule that is necessary to complete a project. Keeping to a schedule when you’re waiting for approval, content or something else from a client can take a lot of patience and a little skill. While not every client is the same — some are absolutely wonderful when it comes to scheduling — having a few tricks up your sleeve can be useful.
1. Put Time Estimates in Context
There cannot be a crisis today; my schedule is already full.
Maybe this scenario sounds familiar: You prepare a proposal for a client, complete with a schedule or timeline. You send it to the client and hear back nothing for days or even weeks. When you do finally get a response, the client wants you to take on the project — and he wants it completed on the schedule you suggested originally. That schedule, however, was based on you starting the project a week or two ago — and you may have picked up another project to work on when you didn’t hear back from the client in question.
I’ve seen plenty of estimates and proposals that highlight a date that the freelancer believes she can complete a project by. It’s rare that date is anything but tentative, however: instead, focusing your client’s attention on the amount of time it will take to complete the project after you’ve actually started it. Any prospective completion date needs to be in the context of the level of work that must occur before that date for a client to understand just how easily it can change.
2. Set Your Schedule When You Actually Start
Once you’ve gotten the go-ahead to start on a project, you can set deadlines and completion dates. Now that you have some certainty that the project is actually moving forward, you can correctly predict dates — as well as tell your clients when you’ll need to get their approval on drafts or mock-ups, as well as get materials or content from then. The schedule may still be tentative in spots, but you don’t have to worry about trying to talk a client into a revised schedule based on when he actually got back to you.
3. Give Your Client Deadlines
Any time you have to wait on your client, it’s important to explain just how long of a response window he has before the project will be delayed. It’s important to be polite of course, but issuing a firm date is in both your own and your client’s interest. More often than not, I’ve been able to get exactly what I need with a sentence along the lines of “As long as you can get the material to me by the date mentioned, we’ll be on track for the project to be completed by the due date.”
Issuing a firm date is in both your own and your client’s interest.
On those occasions when you have to keep following up with a client in order to actually get the material or go-ahead necessary, it’s useful to issue revised schedules, clearly showing new completion dates. Even pushing back the date by one day can get a client’s attention and response.
4. Don’t Let Your Clients Push Your Schedule
I submitted a project to a client on a Monday and didn’t hear back anything until the end of the day Friday — at which point, she wanted me to turn around corrections before Sunday morning. It’s an awkward situation to be in: no one wants to tell a paying client that she can’t have what she wants, but at the same time, the only way for me to take care of it would have been to dump my Saturday plans. If you give in once to a situation like this (even if you charge extra), it’s easy for a client to keep doing it.
Suggesting a more realistic schedule may not make your client happy, but it’s often the only practical option from a freelancer’s point of view. It’s not impossible that a client will walk away at that point, unfortunately, but it’s far more likely that they won’t want to go looking for another freelancer, especially if you’re already part way through the project.



Very Helpful
Thanks
@webdesign_news
yes, it’s an endless fight … I hate when a client says: “Tomorrow it should be!” :-/
Good article and tips. I especially agree with the first one about all dates being relative to the start date. When I put together a proposal, I generally suggest a start date to the client that provides me enough time to complete the project considering my current workflow.
I’d also suggest that you clearly document the phases of your design or development project, so that the client can see from the get-go when his/her input will be required before proceeding.
Being clear about schedules and what can or cannot be achieved within a given timeframe means you have to reconcile yourself to the risk that a client might walk away if they feel the timing doesn’t suit their needs.
Don’t agree to a timeframe that you aren’t comfortable with, or you’ll feel negatively about the job right from the start, and you might also turn in work that’s less than your best.
One thing I do is list the work hours of the business on the contract. That way when they ask for a turn around that is over the weekend I just say the business is closed on weekends and I can start on it on Monday morning. My schedules also always include the dates I will need things from clients and that each late day means at least a one day extension in the project but I have a schedule so if it forces me to overlap another project it may mean more than a one day delay.
The reality is a build a buffer in projects but telling a client that you have other work scheduled in and delaying any more will mean XX days push back of the final day usually gets them moving quickly.
Great tips!
Another, in addition to previous post, is put in a daily deadline in the contract. For example: requests (for me these are usually simple types of requests like updating content, image, or adding a page) — received after 2:00pm will be completed next business day. If the request is urgent and must be completed today, please contact to discuss.
Depending on your contract, this gives you an opportunity to collect additional fees for last minute/urgent requests. This helped a LOT with some of my clients who would wait until the very last second and didn’t understand why I couldn’t necessarily drop what I was working on. The additional fees highly encouraged them to think long term and to get change requests submitted in a more timely manner.
Cortney
One thing that is always super interesting to me that #3 reminded me of is this – after working with clients for a while, they get a feel for the rhythm and the time it takes to get things done. Sometimes, you can fall into the trap of having them dictate the schedule around your work. I definitely have gotten sucked into that.
Now, every time a deadline or date is mentioned I write it down. After a call is had, I check the sanity of the dates and ensure that I am comfortable with what was agreed upon. If there’s anything amiss, I call the client back and provide some feedback on the dates discussed. I’ve found this really helps to avoid the transition of a casual conversations about when something can be expected transforming into an uncomfortable conversation about a missed deadline.
I like to handle this by basing the project timeline on the client’s actions, and addressing that in the actual contract. For example: Phase 1: Client provides X1 information. We provide Y1 within Z days of receipt of X1 information. Phase 2: Client approves work from Phase 1 (or requests changes) and provides X2 information. We provide Y2 within Z days of receipt of approval & X2 information, and so on. This puts the ball in their court at pretty much every stage of the game – the clock doesn’t start ticking until they’ve provided whatever is necessary to move forward.
If the project has a tight timeframe, I’ll shorten the timeframe of the Z variables rather than provide an actual timeframe, and specify in a cover letter or email that the project can be completed by [specific date] if they provide the requested data in a timely fashion.
The “best” is when clients say “I need it yesterday!”. Get real. Show some respect.
Numbers 1 and 2 became issues in the latest project I worked on, and it’s great to have this topic addressed.
For the longest time I’d had the deadline be a hard actual date, but now that my schedule’s gotten very crowded I realize I need to have the contracts work on a duration basis.
I had a project scheduled for 4 weeks of work so the deadline was set 4 weeks from when I drafted the contract; unfortunately the client didn’t approve the contract/send the deposit until a week later, effectively giving me only 3 weeks to finish according to the contract.
Luckily the client is understanding and I get to have that extra week, but from now on my contracts will stipulate something like “project to be completed _____ days from receipt of deposit.”
In a Proposal document, I always set a time frame (two weeks, etc.) rather than a target date. I also mention that the timer starts once the client has approved the proposal and signed an agreement.
I have a big problem with #4, but I’m slowly working toward fixing that.
I needed this article today. I’ve put myself in a situation that doesn’t give me any time to sleep. I really need to avoid that in the future! Thanks for the practical tips.
I experienced all of these when I was freelancing.
#1 I used to put estimated days in the contract and an expected completion date because I found that many clients can take ages to make a decision.
#2 This only occurred when the client wanted changes or extras, which of course meant more time, but it was never an issue.
#3 This was one of the biggest stumbling blocks for me, but kind of in reverse, and it is one of the reasons that I gave up freelancing. Basically, I had some clients that just could/would not provide the content for their site to go live within a reasonable time frame and, of course, wouldn’t pay until the site was live. In one case I had to wait over a year (yes, you read that right!) for the content and to get paid. With hindsight, may be I should have had a late penalty clause in the contract.
#4 I never had a problem with this as I found that, when freelancing, there wasn’t so much of a weekday/weekend divide – I could do things whenever I wanted, not just at weekends.
I run into this problem with clients for both freelance and agency work. One of my current clients doesn’t know what he likes until he sees what he doesn’t like; after each revision, he completely changes his “vision,” which inevitably entails days of work. And then, he proceeds to email every few hours, asking when it can be completed–and I’m forced to explain that my workflow is planned around the original project scope. All I really want to say is “you’re just going to bloody have to wait.”
Great post! Very cathartic.
These are four great tips! As a relatively new freelancer, I definitely struggle with this sometimes. I’d love to see a more in depth article on this.
Great tips! I’m definitely going to change my contract structure to “time from receipt of deposit” instead of a set date.
I also think it’s time to add a clause about project delays and required charges. Since I generally collect 50% up front (with balance on delivery), I might require payment of 25-30% when project is delayed…OR…balance due in full on projected date + x-time. Just not sure how to word it. I know there are “kill fees” in contracts, but what about “delay/just busy with other things/kind of forgot about our project fees”?
Any suggestions?
BTW…this very subject was on my mind yesterday. So I wrote a post while waiting, and waiting for client feedback…http://azzcatdesign.com/blog/
Cool Tips…Thanks
Nice helpful article, thanks
Great article, excellent advice… Time to enforce order out of all the chaos. I see rest filled nights ahead!
@carlolee
#freelanceswitchrox
Nice articles. A very important aspect of freelancing that is oft neglected.
In planning a project, it’s important to fix a proper schedule and stick to it and sometimes to build more buffer into it if required. This helps in the production and also management of expectation of the client.
End of the day, the client gets a realistic deadline that is close 90% correct and you don’t go mad trying to put out fires from rushing.
Freelancing would be so easy without clients, though we’d all have angry bank managers, phone providers, utilities providers, etc…
From my experience every client email is urgent to them, and some times you’ll make them a little angry by not responding almost instantly. I’ve found that it’s quite good to have a load of canned responses ready to go so that recurring issues can be dealt with reasonably quickly and simply.
Number 3, gives the client “skin” in the game. Unless they deliver on their tasks, you can’t can’t deliver on the project. Call them weekly to verify the completion times of their tasks and keep them personally obligated to the project schedule.
You must define how you do business or your clients and/or consultants will do it for you.
Great article for all businesses; I blogged it.
http://cadgrafx.com/blog/revit/2009/07/profitably-manage-your-revit-project.html
Great Post. Always give your self more time in a case something will go wrong.
One thing I discovered when it comes to scheduling and deadlines is that the semantics are hugely important.
It definitely sound much better if you say that you will have a project done by the mid next-week rather than next Tuesday. Or thatit will take 2 weeks rather than 10 days.
THANK YOU for this! Great article. I think you just solved a big problem in the past with various clients throughout the years.
I’m going to build much of this data into my proposals from now on!
Gregory