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: contract language From:Kat Nagel/MasterWork <katnagel -at- EZNET -dot- NET> Date:Fri, 18 Aug 1995 09:08:09 -0400
Loren Castro wrote:
>I have a hard time
>imagining the Government's insistence on accepting only X or Y and the
>contractor's insistence on delivering both, but I suppose it happens.
>I can only guess, but I suppose it could happen in civilian work also.
As it happens, I ran into exactly this situation with one of my first clients.
o The contract said "either A or B.'
o This eager little beaver cheerfully delivered BOTH items,
along with an invoice for the agreed-upon $$$.
o The client (even more cheerfully) said "Thank you very much,"
and gave me a check for _1/2_ of the $$$. Since they only
asked for one or t'other, they weren't going to pay for both.
o The lawyers (mine, as well as theirs) said they could get away
with that because of the way the contract was worded.
Now, I give such clients A, collect my full $$$, _then_ tell them that they
can have B as well for only $x more (20% or 25% of original contract).
Works pretty well.
/| Kat Nagel
\'o.O' MasterWork Consulting Services Rochester, NY
=(___)= LIFE1 (techwriting/docdesign) katnagel -at- eznet -dot- net
U LIFE2 (vocal chamber music) PlaynSong -at- aol -dot- com
