The translation management database helps me to manage my translation projects, create statistics on my productivity and drive invoicing.
Numbers produced (combinations)
I produce some or all of these combinations
Hourly rate (GBP)
Hourly word rate (WPH)
Avg order price (GBP)
PW by period
PT by period
HR by project
Avg order (AO)
PW by customer
AO by customer
HR by project
PW by category
WPH by task type
Production overview (GTD)
The GTD review is an overview of my performance and I measure it with some key data:
I do a GTD review every week but because I create a new week I can do the GTD review within the week I don’t have to wait until the end and I see progressively how things are going.
The main thing is that I look at are the hourly rate, the word rate, to reassure myself that the work I’m doing is worth it by seeing if the hourly rate is high enough and also the word rate is high enough to know that I’m doing things fast enough.
Statistics, particularly, hourly rate and word rate per hour
Overall statistics for a period, the year, Breakdown by category, domain,
customer breakdown enables me to see which are the best customers, the customers who are sending me the work I’m most efficient at
Weekly performance, how many hours I’ve done in a week how many words
Monthly production (hours)
Overall, I can see how many words I’m doing per month and whether I’m putting in the hours.
Monthly production (words)
The difference between batch words and project words. Project words is the number of words in the order. But if a project is 5,000 words, I might do 10,000 in all batches, 5,000 to draft and 5,000 to proofread. All this time and volume must be (and is) counted in the hourly rate.
A high hourly word rate means that I’m working as fast as possible (maintaining quality). A rising hourly word rate may be a sign of finding better ways of doing things (continuous improvement).
Hourly rate (GBP)
The hourly financial rate helps me tell whether the hours I’m putting in are profitable.
Measuring the key data
I therefore need to capture time spent on projects in the translation management database. I work on projects in batches of roughly half an hour, which I record using the timer screen. This video
Explains the key measures that the translation database helps to manage.
Demonstrates a test project and recording time spent.
Provides a short explanation of hourly rate.
I estimate a project for 1500 words at a word rate of 0.05, total price is 75 GBP. It will take me 1.5 hours, thus an hourly rate of 50 GBP. This is achieved in two half hour batches of 750 words one translating to draft and one half hour proofing 1500 words.
In this video, I use a new project,
Number of words: 1500
Price: 75 EUR
Time estimate: 1.5 hrs
Estimated hourly rate: 50 EUR
Start working on a project
Time the work done with the timer screen
Enter 2 batches: 1 x 0.5 hours to 750 words and 1 x 0.5 to 1500 words
Enter 1 batch: 1 x 0.5 hrs for 1500 words proofing (to OK)
1500 words in 1.5 hrs is a word rate of 1000 words per hour and hourly rate of 50 GBP
The timer screen is where I show the time spent on projects
Applies the Pomodoro method.
I can see my progress on the timer screen, how many days a job has taken me, my average hourly rate and word rate.
Each project in the translation management database has its own specific terms which I record against the project ID, so I can come back and look at the vocabulary for specific projects.
Search all terms
I can search through all the vocabulary to find the term I’m looking for. I can attach an existing term to the current project, enter new terms, and thus constitute the terms for a project. This is also an opportunity to improve terms I’ve come across already.
Import term bases
I import term bases into the translation management database, technical dictionaries (such as the engineering one) which are available when I’m doing a project.