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:Re: How to handle when the scope changes? From:"Jeff Hanvey" <jewahe -at- lycos -dot- co -dot- uk> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 16 May 2003 13:55:36 -0400
First, you should have provisions for change orders in your contract with
the company. Enforce these change orders, and don't start any work until the
change has been signed and approved. You can - and should - renegotiate your
rates accordingly.
If you do not have this provision, then you 1) should stick to the original
scope or 2) accept the loss and do the project as changed.
----- Original Message -----
From: "Kirsten Zerbinis" <salmonzerbinis -at- rogers -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Friday, May 16, 2003 11:40 AM
Subject: How to handle when the scope changes?
>
> I am a freelance tech writer, working as the sole writer on an 8-week
> project. I accepted the contract I was offered at the low end of my
> pay range, with the caveat that I would do only the one contract for
> this customer at that rate. The next job, if they offered it to me,
> would be at a higher rate. I gave reasons (typical salary range for
> this position in this area) why this was so, and while they didn't
> agree to it, they didn't disagree. (I didn't really make it sound like
> a question.)
>
> Anyway, the twist is this. Now, two weeks into my eight-week project,
> they are talking about increasing the scope, adding a third piece of
> software to the pile of things to be documented within 8 weeks. They
> would make one of their employees available to me to help me accomplish
> the work within the timeframe
>
> I would feel taken advantage of if I do the new job at the same rate as
> the old job. However, the old job isn't up yet. Also, I don't think I
> could separate work on one from work on the other, so billing
> separately isn't an option. Have you come across this situation? How
> do you generally handle a change of scope like this?
>
> Thanks for any insight
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.