TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Frozen contractors From:Peter Kent <71601 -dot- 1266 -at- COMPUSERVE -dot- COM> Date:Mon, 20 Nov 1995 09:59:44 EST
A quick question for the contractors among you...
How do you handle frozen contracts. For instance, you take on a 3 month
project, but after two months it becomes clear that it's going to take much
longer; 6 or 8 months, perhaps more.
I'm just interested to hear how writers:
a: deal with this possibility in their contracts.
b: deal with a freeze if it actually happens.
A writer asked me these questions the other day, wondering if I was going to
deal with the subject in my book update. I am, but I don't know if the way I
deal with the problem is the best or only way (I'm sure it's not, in fact).
I've structured my business such that I always have several clients, so if one
delays it's no big deal; cash flow is down for a while, but picks up later
when the contract continues. In one case I've got the client to pay more
money, but that was because they wanted me to continue testing their software
and submitting my test reports, then pick up the documentation bit a little
Peter Kent: 71601 -dot- 1266 -at- compuserve -dot- com, 303-989-1869
Coming soon, an updated and revised Technical Writer's Freelancing
Guide. E-mail for more information. Comments/suggestions welcome.