<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Keeping statistics about your freelance business</title>
	<atom:link href="http://thoughtsontranslation.com/2009/07/10/keeping-statistics-about-your-freelance-business/feed/" rel="self" type="application/rss+xml" />
	<link>http://thoughtsontranslation.com/2009/07/10/keeping-statistics-about-your-freelance-business/</link>
	<description>...the translation industry and becoming a translator</description>
	<lastBuildDate>Wed, 28 Jul 2010 18:30:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Joan</title>
		<link>http://thoughtsontranslation.com/2009/07/10/keeping-statistics-about-your-freelance-business/#comment-2180</link>
		<dc:creator>Joan</dc:creator>
		<pubDate>Fri, 14 Aug 2009 18:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=595#comment-2180</guid>
		<description>Sorry, I&#039;m a late replier.
I&#039;ve tried tracking a number of these things, and am not very good at sticking with them, but there is one very simple record-keeping system I&#039;ve used for a long time that I find useful. It&#039;s nothing but a color-coded table in Word.
I keep a table of each job (my invoice/client name/job/number/amount/date submitted and invoiced/and the date the invoice is paid). I started this table at the beginning of 2000, and from that point on, I can go back and check how much I made in any given month of a given year and compare how I&#039;m doing.
Also, if a client name rings a bell, but I can&#039;t quite remember, I can find them, see when I last work for them, how large the job was (and my invoice # which language, as well as the sequence number, my first invoice, in 1993, was 0001, the last was 4447, plus F, S, or T to indicate the language)
I can also see how long it took them to pay me. When I receive payment, in addition to noting the date, I color code the line for that job: blue (under 30 days), green (30-60 days), orange if I have to chase them down. One orange may not be a problem if something really did slip through the cracks and they quickly send it when I call. It can happen to anyone, but if it&#039;s a pattern, or I get the run around, have to remind repeatedly, the client may eventually get marked red (with a little skull and crossbones for effect), which means stay away.
In addition, I keep an extra little table below with mid-year and end-of-year totals also going back to 2000. If I&#039;m on track, I can relax a little. If I&#039;m behind, then it means I need to hustle a little.

Joan</description>
		<content:encoded><![CDATA[<p>Sorry, I&#8217;m a late replier.<br />
I&#8217;ve tried tracking a number of these things, and am not very good at sticking with them, but there is one very simple record-keeping system I&#8217;ve used for a long time that I find useful. It&#8217;s nothing but a color-coded table in Word.<br />
I keep a table of each job (my invoice/client name/job/number/amount/date submitted and invoiced/and the date the invoice is paid). I started this table at the beginning of 2000, and from that point on, I can go back and check how much I made in any given month of a given year and compare how I&#8217;m doing.<br />
Also, if a client name rings a bell, but I can&#8217;t quite remember, I can find them, see when I last work for them, how large the job was (and my invoice # which language, as well as the sequence number, my first invoice, in 1993, was 0001, the last was 4447, plus F, S, or T to indicate the language)<br />
I can also see how long it took them to pay me. When I receive payment, in addition to noting the date, I color code the line for that job: blue (under 30 days), green (30-60 days), orange if I have to chase them down. One orange may not be a problem if something really did slip through the cracks and they quickly send it when I call. It can happen to anyone, but if it&#8217;s a pattern, or I get the run around, have to remind repeatedly, the client may eventually get marked red (with a little skull and crossbones for effect), which means stay away.<br />
In addition, I keep an extra little table below with mid-year and end-of-year totals also going back to 2000. If I&#8217;m on track, I can relax a little. If I&#8217;m behind, then it means I need to hustle a little.</p>
<p>Joan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cristina Silva</title>
		<link>http://thoughtsontranslation.com/2009/07/10/keeping-statistics-about-your-freelance-business/#comment-2007</link>
		<dc:creator>Cristina Silva</dc:creator>
		<pubDate>Mon, 13 Jul 2009 17:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=595#comment-2007</guid>
		<description>Corinne, 

This is interesting and I&#039;m actually working on tracking my numbers for different types of linguistic services this year (translation x edit/proof x interpretation x voice-over, etc) and am curious to hear what our colleagues are actually using to do that. I&#039;ve figured out that my accounting program (Quicken) actually has some categories that I can use to do that, but would like to see what others are doing.</description>
		<content:encoded><![CDATA[<p>Corinne, </p>
<p>This is interesting and I&#8217;m actually working on tracking my numbers for different types of linguistic services this year (translation x edit/proof x interpretation x voice-over, etc) and am curious to hear what our colleagues are actually using to do that. I&#8217;ve figured out that my accounting program (Quicken) actually has some categories that I can use to do that, but would like to see what others are doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Lossner</title>
		<link>http://thoughtsontranslation.com/2009/07/10/keeping-statistics-about-your-freelance-business/#comment-2002</link>
		<dc:creator>Kevin Lossner</dc:creator>
		<pubDate>Sat, 11 Jul 2009 11:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=595#comment-2002</guid>
		<description>This is a very useful reminder, Corinne. Every time I do a statistical workup on my business data I learn very important things, some of which show that I harbored fundamental misconceptions about the distribution of projects or the economic importance of some prominent customers. Fact-based reality checks are always good.

As far as some of the tools for doing this are concerned, I&#039;m at a bit of a crossroads. I own several good commercial solutions (one discontinued and no longer supported) which allow me to manage a lot of the administrative side of our translation business, but I have grown increasingly disgusted with little details in which the &quot;solution&quot; fails to accommodate the international, multi-lingual nature of the business where minor details such as the way numbers are written also differ between countries that appear to share a common language. Or in some cases I am just damned tired of clumsy workflows that force my to twist my administrative practices to fit.

So I&#039;m thinking about &quot;downshifting&quot; and restructuring all my data to use simple spreadsheets, a custom database and mail merge templates in the OO word processor or perhaps MS Word again. A horrible thought, really, but after nearly a decade of waiting for other programmers to get things sorted out I&#039;m just tired of half-solutions and little being done to advance them in a direction that would really save me time.</description>
		<content:encoded><![CDATA[<p>This is a very useful reminder, Corinne. Every time I do a statistical workup on my business data I learn very important things, some of which show that I harbored fundamental misconceptions about the distribution of projects or the economic importance of some prominent customers. Fact-based reality checks are always good.</p>
<p>As far as some of the tools for doing this are concerned, I&#8217;m at a bit of a crossroads. I own several good commercial solutions (one discontinued and no longer supported) which allow me to manage a lot of the administrative side of our translation business, but I have grown increasingly disgusted with little details in which the &#8220;solution&#8221; fails to accommodate the international, multi-lingual nature of the business where minor details such as the way numbers are written also differ between countries that appear to share a common language. Or in some cases I am just damned tired of clumsy workflows that force my to twist my administrative practices to fit.</p>
<p>So I&#8217;m thinking about &#8220;downshifting&#8221; and restructuring all my data to use simple spreadsheets, a custom database and mail merge templates in the OO word processor or perhaps MS Word again. A horrible thought, really, but after nearly a decade of waiting for other programmers to get things sorted out I&#8217;m just tired of half-solutions and little being done to advance them in a direction that would really save me time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riccardo</title>
		<link>http://thoughtsontranslation.com/2009/07/10/keeping-statistics-about-your-freelance-business/#comment-1997</link>
		<dc:creator>Riccardo</dc:creator>
		<pubDate>Fri, 10 Jul 2009 22:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://thoughtsontranslation.com/?p=595#comment-1997</guid>
		<description>1) Subject matter (Legal, IT, Medical, etc.)
2) Type of task (Translation, Editing, Proofreading, Interpreting, etc.)
3) Invoice aging (How many days before or after the agreed due date are you receiving payment from the customer?) 
4) Unpaid total by customer

1) and 2) are very useful if you want to get E&amp;O insurance
 
A combination of 3) and 4) is especially important, as we don&#039;t want to be overexposed towards certain customers, and bad numbers in 3) may indicate a customer that needs pruning</description>
		<content:encoded><![CDATA[<p>1) Subject matter (Legal, IT, Medical, etc.)<br />
2) Type of task (Translation, Editing, Proofreading, Interpreting, etc.)<br />
3) Invoice aging (How many days before or after the agreed due date are you receiving payment from the customer?)<br />
4) Unpaid total by customer</p>
<p>1) and 2) are very useful if you want to get E&amp;O insurance</p>
<p>A combination of 3) and 4) is especially important, as we don&#8217;t want to be overexposed towards certain customers, and bad numbers in 3) may indicate a customer that needs pruning</p>
]]></content:encoded>
	</item>
</channel>
</rss>
