Word count is the measurement of total words in source, target, or translation memory file content, used to define project scope, pricing, and productivity targets. In localization workflows, word counts are broken down by match type, file, language pair, or individual service so that clients and providers can compare effort, generate consistent quotes, and track production volume across different projects.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Word count is the central figure quoted in purchase orders, translation briefs, and CAT tool analysis reports before and after project delivery. Project managers use it for invoicing, measuring translator productivity, and comparing source and target volumes across locales, especially when languages expand or contract differently during final desktop-publishing layout.
Word counts can be misunderstood when clients quote source text volume but expect target-language invoicing, or when CAT tools count words differently from localized file formats. Inconsistent counting, especially around tags, numbers, CJK characters, and compound words, leads to repeated billing disputes and inaccurate productivity comparisons across multiple linguists and major projects.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.