<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Careers&gt;Freelance&gt;Proposals</title>	<link>http://tc.eserver.org/dir/Careers/Freelance/Proposals</link>
	<description>A listing of the most recently indexed works about Careers and Freelance and Proposals in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Careers&gt;Freelance&gt;Proposals</title>
		<link>http://tc.eserver.org/dir/Careers/Freelance/Proposals</link>
	</image>
	<item>
		<title>Estimating Project Times and Costs Without Losing Your Shirt--Or Your Sanity</title>
		<link>http://tc.eserver.org/29410.html</link>
		<guid>http://tc.eserver.org/29410.html</guid>
		<description>Determining how long it takes to complete a job is essential for planning and for budgeting your time, whether you&apos;re a wage slave or a freelancer. In this article, I&apos;ll focus on the needs of the freelancer, but the same approach will work equally well for managers of teams of technical communicators and even for lone writers.</description>
	</item>
	<item>
		<title>Note to Contractors: Expose Your Writing Tasks</title>
		<link>http://tc.eserver.org/24877.html</link>
		<guid>http://tc.eserver.org/24877.html</guid>
		<description>Some contractors short-change themselves by failing to reveal in cost proposals all of the tasks they perform. Argues that full disclosure can improve a contractor&apos;s bottom line.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Careers/Freelance/Proposals.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>