When a translation relationship lasts for years, what remains is not only the delivered files: the record of resolved sentences, the approved terms and the spelling decisions accumulate. This accumulation is called language assets, and if who it belongs to is not written down at the outset, it becomes a matter of dispute later.
Definition
Language assets are the accumulated asset made up of the memory, the termbase and the guides. The scope includes more than one document. It is valued as a whole.
What they cover
The translation memory, the termbase, the style guide and the reference archive fall within this scope. The list is enumerated in the contract. The scope is kept clear.
How they come about
The assets accumulate by themselves as work is done. No separate production process is needed. The accumulation is continuous.
The source of their value
The value is that decisions made in the past can be reused. The same question is not solved twice. The gain is cumulative.
Growth over time
As the volume grows, the match rate rises. Cost falls and consistency increases. The effect is measurable.
The question of ownership
Who the assets belong to is defined in the contract. An undefined situation produces uncertainty. The question is asked at the outset.
A definition in the client's favour
The common practice is for the assets to belong to the client. The client is the source of the content. The definition has a reason.
Handover conditions
The format in which they will be delivered on request is written down. A standard format is used. The condition is made concrete.
The standard format requirement
The assets are delivered in common and open formats. A proprietary format produces dependence. The rule protects.
The risk of dependence
If the assets are not with the client, changing supplier becomes expensive. This risk grows silently. The safeguard is in the contract.
Transition cost
If the assets are not handed over, the new supplier starts from scratch. A loss of consistency is experienced. The cost appears twofold.
Keeping them up to date
At the moment of handover the assets need to be up to date. An asset without maintenance is of no use even if it is handed over. The maintenance condition is written down.
Responsibility for maintenance
With whom the maintenance lies is defined. Ownership and maintenance may not be on the same side. The distinction is stated.
The confidentiality dimension
Because the assets carry client content, they fall within the scope of confidentiality. They are not used for other clients. The limit is strict.
The shared memory problem
The content of more than one client is not kept in the same memory. The separation is set up at the outset. The structure is designed accordingly.
Backing them up
The assets are backed up regularly. Losing them wipes out years of accumulation. The backup is kept in a separate environment.
At the end of the relationship
When the work comes to an end, the assets are delivered and the copies held by the supplier are handled according to the contract. The process is defined in advance. The ending is orderly.
Assessment criterion
When a supplier is selected, the asset management policy is asked about separately. The policy determines the long-term relationship. The question is added to the list.
Strategic importance
Language assets are the only permanent capital an organisation accumulates in its multilingual communication, and with the right ownership arrangement the relationship is continued by choice, not by necessity. This balance protects the organisation. The arrangement is set up at the outset.
What it is confused with
Language assets are often taken to be merely the delivered translation files. Yet the real value is not in the files but in the memory and decision records behind them; an organisation that holds the files but not the assets starts again from the beginning with every new supplier.