Skip to main content

Target Logfiles

This article aims to clarify the use of target logfiles for project's costs calculation and the payment of the vendor's budget.

Updated over 2 months ago

What are Logfiles?

Logfiles show the project's segment count and specification, words and characters to be translated, and serve as a base for cost estimation and calculation, also for setting the vendor's budget.

Previously, Bureau Works only allowed the creation of pre and post-analysis logfiles based on the source file for cost estimation. Now, you have the option to calculate the Target logfile to serve as a base for calculus and estimation of costs.


How To Generatate a Target Logfile?

In order to generate a Target Logfile, first you must pre-translate the work unit using Machine Translation, Context Senstive Translation or Translation Memory. Learn more about pre-translation here.

After finishing the pre-translation, you must manually create the logfile, selecting the Whole Project option and then finally selecting the Target option.


This allows the user to utilize the logfile to estimate the word count in the Target or to calculate the project budget prior to completing the translation, by pre-translating the file using Translation Memory, Context Sensitive Translation or Machine Translation.

How Cost Calculation Works with TARGET Logfiles

Feature Overview

This feature allows you to define how project costs are calculated—either based on the original source content (SOURCE) or the pre-translated content (TARGET).

If your team uses pre-translation methods—such as machine translation, translation memory, or context-based suggestions—selecting the TARGET option will generate more accurate cost reports. This setting ensures that cost analysis reflects content that was already translated automatically, rather than the raw source text.

The configuration can be managed through the Net Rate tab within your Organizational Unit settings.

How It Works

SOURCE vs. TARGET

  • SOURCE (default): Cost is calculated based on the original source text, before any translation is applied.

  • TARGET: Cost is calculated based on the content after pre-translation, which may include:

    • Machine translation

    • Translation memory matches

    • Context-sensitive translation

Using TARGET offers a more precise view of the content that still requires manual translation, helping you better estimate actual effort and cost.

Behavior When Using TARGET

When TARGET is selected, the system ensures that pre-translation is completed before cost analysis occurs. As a result, the logfile reflects content that was automatically translated through configured tools.

No additional steps are needed—the system automatically handles the correct processing order.

Impact on Project Automation

Selecting TARGET as the basis for logfile and budget calculations modifies the project workflow accordingly:

  • Pre-translation is executed first: The system applies all relevant automated translations before generating the logfile.

  • Logfile is generated from TARGET content: This ensures the logfile includes the pre-translated segments.

  • More accurate cost analysis: Since the logfile is based on the final pre-translated version, the analysis more accurately reflects remaining manual effort.

  • Word and segment counts adjust accordingly: The counts reflect only what remains in the TARGET content.

If SOURCE is selected, the project behaves as usual: logfile generation happens before any translation is applied, and word/segment counts reflect the full, untranslated source content.

How to Configure This Setting

  1. Go to your Organizational Unit settings.

  2. Open the Net Rate tab.

  3. Choose the logfile from Target:

    • Reports and analysis

    • Project and Task budget calculations

Each setting can be configured independently based on your operational requirements.

If you’re uncertain about which option best fits your workflow, feel free to contact us—we’re happy to assist.


Did this answer your question?