Translate | ISO/IEC 19770-1:2017 IT Asset Inventories, License Entitlements, Ownership and Disposal Evidence
How do you translate an IT asset inventory, software licensing record or IT asset management audit report accurately? Teams working across countries need to keep asset identifiers, license entitlements, installation evidence, contract scope and disposal decisions aligned while translating technical descriptions. A cleanly written target-language inventory is of little value if it turns an assigned device into an owned device, a requested license into a granted right, or an unverified deletion into a certified erasure.
ISO/IEC 19770-1:2017 concerns requirements for an IT asset management system across the organization, rather than a universal software-license contract or a technical specification for each product. The ISO catalogue says this edition was confirmed in 2024 and has a 2024 climate-action amendment. Its management-system scope includes IT assets in organizational context. Translators using its name should distinguish the standard’s management framework from local accounting policy, product licensing terms, cybersecurity controls and statutory disposal requirements.
This guide answers the narrow question of how to translate IT asset management documents without changing rights, status or audit evidence. It explains a concept map, concrete inventory and software entitlement examples, handover records, procurement terms, approval language, multilingual quality assurance and twenty-four worked cases. The examples are invented teaching scenarios, not official ISO passages. Where contractual rights or security evidence matter, the controlling source and authorized reviewers always take precedence over stylistic fluency.
Quick answer
- Preserve asset IDs, serial numbers, SKUs, product versions and license metrics exactly.
- Separate possession, assignment, ownership, license entitlement, installation and actual use.
- Treat discovered installations as observations, not proof of a right to use software.
- Keep dates, contract parties, usage scope, exceptions and approval status explicit.
- Translate disposal and data-erasure claims only to the strength supported by records.
- Send unresolved licensing questions to the authorized commercial or legal reviewer.
Contents
- Start with the asset and the reader’s decision
- Separate entitlement, installation and use
- Identify license metrics before translating quantities
- Do not change assignment into ownership
- Make lifecycle states explicit
- Read contracts as scoped rights
- Audit exceptions and evidence quality
- Represent procurement and supplier handoffs
- Protect discovery and configuration data
- Explain virtual and cloud assets carefully
- Treat disposal and wiping as evidence-backed events
- Account for mergers, transfers and relocation
- Build a balanced ITAM dashboard translation
- Review the actual delivery environment
- Terminology crosswalk
- Worked translation cases
- Translation and release workflow
- Frequently asked questions
- Four-week practice plan
1. Start with the asset and the reader’s decision
An IT asset is not just a computer. Depending on the organization’s scope, it may be a device, software entitlement, virtual resource or controlled component. Translation starts by asking whether the recipient wants to reconcile stock, audit usage, check a renewal, identify a security risk or approve disposal. Each decision relies on different fields. An elegant label that hides the asset’s controlled identity defeats all five tasks.
Build a field map: human-readable description, immutable asset ID, physical serial, owner, custodian, lifecycle state, location, evidence date and source. Match repeated IDs between the register and linked documents. A recipient must be able to trace a translated row back to the same source item without guessing which laptop or license is intended.
Try this before translating the next file: If a record says ‘assigned to team’, does the organization own it, has it merely allocated it, or has it only booked it for future assignment? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
2. Separate entitlement, installation and use
A software entitlement records a right derived from terms, not a measurement of what is on a device. An installation discovery tool records observations, which might be incomplete or stale. Actual use needs another kind of evidence. In multilingual reporting, ‘licensed’, ‘installed’ and ‘actively used’ should never substitute for one another even if a general dictionary offers nearby words.
A simple diagram in words is useful: contract or purchase evidence can support entitlement; deployment or discovery evidence may support installation; activity logs may support use. Each chain has an owner and relevant date. Translation should preserve the chain and the uncertainty instead of creating an unsupported conclusion that an observed application is compliant.
Try this before translating the next file: Can the reader tell which field is a right, which is a detected installation and which is a usage estimate? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
3. Identify license metrics before translating quantities
Per-user, per-device, core-based, concurrent-use and subscription metrics are not interchangeable. A phrase like ’25 seats’ may be informal shorthand whose contractual meaning needs confirmation. A translator must keep the supplied metric, period and exclusions visible rather than simplifying every license to one copy of software.
Record the product edition, version, eligible population, counting rule, pool or tenant, geographic or organizational scope and date of the source calculation. Where the metric is undefined, retain the original term and request clarification. The translator’s job is not to interpret a publisher’s licensing agreement in place of counsel or the asset manager.
Try this before translating the next file: Does ‘twelve licensed users’ refer to twelve named accounts, twelve simultaneous users or twelve purchased units? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
4. Do not change assignment into ownership
Assignment answers who uses or cares for an asset; ownership answers who holds legal or organizational title. A leased server may be in a team’s custody but not its property. A managed device may belong to a vendor while the customer administers its software settings. Those distinctions matter when records move between accounting, service desks and procurement.
Translate role columns with an explicit vocabulary for owner, custodian, user, operator, approver and supplier. If the source form combines two roles, preserve that ambiguity and flag it for the form owner. Do not invent a responsible party merely because an empty cell seems unhelpful.
Try this before translating the next file: Which role is authorized to authorize disposal, and is that the same person listed as daily user? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
5. Make lifecycle states explicit
An asset can move through request, purchase, receipt, configuration, active service, repair, storage, transfer, retirement and disposal. ‘Retired’ from productive service is not identical to physically destroyed or securely erased. Lifecycle status should not be translated as a narrative that falsely implies later steps happened.
For every lifecycle label, maintain the controlling system’s event code, effective time, recording time, actor and evidence pointer. An interim state may last weeks. If the source says ‘awaiting return’, retain that open dependency. In recipient screens, keep the translated label short without collapsing the difference between planned and completed actions.
Try this before translating the next file: Can a reviewer reconstruct the exact stage and its supporting event without inferring a subsequent stage? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
6. Read contracts as scoped rights
An enterprise agreement may cover a named legal entity, an affiliate group, eligible geographies, specified products, versions, use cases and dates. The target text must not quietly extend those rights to all subsidiaries or all cloud environments. Local team names are especially unreliable substitutes for legal contracting parties.
Map entity names to the signed agreement, keep product identifiers unchanged and show effective and expiry dates with timezone or locale clarification where needed. If the contract uses a defined term, retain its capitalized role in the translation glossary. Escalate any ambiguous territorial or affiliate definition rather than interpreting it through ordinary-language intuition.
Try this before translating the next file: If a sentence names an affiliated company, does the agreement actually grant it entitlement or merely mention it in a reporting annex? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
7. Audit exceptions and evidence quality
An exception record documents a variance and the approval or remediation plan attached to it. The words ‘accepted risk’, ‘temporary exception’ and ‘compliant’ represent different states. Translating an exception as full approval can erase the need for remedial work and make an audit trail misleading.
Preserve exception ID, rationale, scope, expiry date, compensating action, approver and whether verification occurred. Distinguish evidence attached by a submitter from evidence checked by an auditor. A blank supporting attachment is not the same as a verified absence of an issue.
Try this before translating the next file: Does a translated status indicate a documented exception or imply that the underlying requirement was already met? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
8. Represent procurement and supplier handoffs
Quotes, purchase orders, invoices, delivery notes and acceptance records represent different commitments and facts. A purchase order is not proof of receipt; a delivery note is not proof of acceptance; payment is not always proof of license authorization. Multilingual procurement desks often mistake these milestones when using one broad verb for ‘obtained’.
Build a chain from request through approval, order, delivery, reconciliation and acceptance. Use separate fields for quantity ordered, quantity delivered, quantity accepted and quantity entitled. Cross-check company names, product editions and contract periods. Where a reseller provides information that the publisher must confirm, keep that division of authority explicit.
Try this before translating the next file: Has the buyer only ordered five subscriptions, or has the license right actually commenced under the agreement? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
9. Protect discovery and configuration data
Discovery systems can return hostnames, IP addresses, installed-product strings, fingerprints and device metadata. Translators should not localize machine keys, executable names, paths or version identifiers as if they were readable headings. Changing one key can disconnect a translated report from an automated reconciliation pipeline.
Create a do-not-translate list for unique IDs, hashes, schema keys, file paths and software strings when the system depends on exact matching. Translate explanatory captions into a parallel display field. Protect sensitive inventories from unnecessary distribution, and follow the organization’s approved security-handling rules.
Try this before translating the next file: Could a machine still join the translated table to the original discovery report using the exact same identifiers? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
10. Explain virtual and cloud assets carefully
In cloud infrastructure, a tenant, account, subscription, service, instance and license are separate objects. One subscription may fund many instances, while a virtual machine may be recreated under a different identifier. A translated phrase like ‘server purchased’ can be a costly error when the source describes rented capacity.
Check whether the record’s quantity describes deployed instances, reserved capacity, concurrent usage, billing units or rights of access. Record the observation window and cloud service version. Keep automated resource identifiers unmodified even when their human names are translated for a local team.
Try this before translating the next file: Is the number shown a point-in-time count, monthly consumption total or contractual cap? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
11. Treat disposal and wiping as evidence-backed events
A disposal instruction is not a completed disposal event, and a completed physical collection is not evidence of data erasure. Third-party recycling and secure deletion often generate different documents. Translation must keep intended action, performed action, verified result and certificate source separate.
Review the collection receipt, chain-of-custody record, wiping report, verification method and final disposition certificate separately. Use the exact device list and date ranges. Never substitute ‘securely destroyed’ for ‘sent to recycler’. If the record contains personal information, apply authorized handling and redaction before distributing translations.
Try this before translating the next file: Can the receiving auditor identify the exact proof of erasure for each identified storage device? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
12. Account for mergers, transfers and relocation
An internal transfer between departments is different from a sale or a change in legal ownership. Company acquisitions may alter contractual rights only under specified terms; relocation can affect tax, data governance and license geography without changing device identity. These differences are important in translations of register-change forms.
Retain the source and destination organizations, transfer effective date, approved person, asset identity and any unresolved contract review. Where the record uses the word ‘transfer’, ask what exactly moves: possession, cost center, service responsibility, title or access right.
Try this before translating the next file: Does the transfer document state a fact already effective or merely request permission for a future change? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
13. Build a balanced ITAM dashboard translation
Dashboards combine counters, statuses, ratios and caveats. ‘Compliance percentage’ may be an internal calculation dependent on discovery completeness and chosen metric; it is not necessarily a certified conclusion. A score without method can mislead readers in another language.
Document numerator, denominator, observation period, exclusions, freshness and source system. Translate annotations around each metric as carefully as the metric label. State whether data are estimated, sampled, reconciled or independently checked. Do not silently change a period from quarter-to-date to calendar quarter.
Try this before translating the next file: Can a reader reproduce the dashboard result from the disclosed method and interpret its limitations? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
14. Review the actual delivery environment
An inventory may be displayed in ERP, asset management software, exported spreadsheets or PDF audit packages. Strings that fit an English column may clip in another language; Unicode punctuation can also break matching rules. Translation quality includes the receiving system, not just a bilingual Word document.
Run imports against a test environment, protect formulas and keys, check sortable labels and inspect evidence links. Sample older records and rare statuses, not only active assets. Confirm whether a report is accessible for teams using screen readers and ensure translated help text explains unfamiliar abbreviations.
Try this before translating the next file: After importing the translated file, does every identifier still reconcile and every status remain interpretable? Write the answer in a source-language annotation first, identify the record that can substantiate it, and then carry that bounded meaning into the target language. An unresolved question belongs in an issue register, not inside an invented confident sentence.
Terminology crosswalk for bilingual reviewers
These English concept descriptions are anchors for choosing equivalents in any target language, not a universal word-for-word dictionary. Record preferred target terms separately for each locale, audience and version. A term that is natural in consumer copy may be wrong in a controlled technical record.
1. IT asset
An item managed within the organization’s defined ITAM scope; the exact boundaries are locally established and should not be inferred from the word ‘computer’.
2. Entitlement
A right to use a product or service under specified terms; not interchangeable with installation or user activity.
3. Installation
Evidence that software or a component appears on a device or environment, without by itself establishing a license right.
4. Usage
An observation of activity under a defined measurement method and reporting period.
5. License metric
The agreed counting rule governing entitlement, such as eligible users, devices or other contractually defined units.
6. Custodian
The person or team entrusted with possession or care; may differ from the legal owner.
7. Discovery
A technical observation process that detects assets or software, subject to data quality and coverage limitations.
8. Reconciliation
Comparison of multiple records to find agreement or gaps; not a synonym for proof that every entry is correct.
9. Exception
A documented deviation requiring a scope, decision, time limit or further action.
10. Decommissioning
Removal from active service; does not necessarily establish physical destruction or verified erasure.
11. Erasure evidence
Record of a data-removal operation and its verification method, tied to specific media.
12. Configuration item
An element managed under configuration controls; its identity and relations may be distinct from an inventory asset.
13. Software edition
The precise product offering, which may affect entitlement and compatibility.
14. True-up
A contract-defined reconciliation or adjustment mechanism, not automatically a penalty or refund.
15. Managed service
A service delivered under an agreement whose supplier-held assets and customer responsibilities require careful separation.
16. Effective date
The date on which a term, status or decision operates, which may differ from the date the record was written.
17. Source of truth
The record the organization has designated as controlling; a translated description must not silently supersede it.
18. Revision
The controlled version of a document or data object; an updated translation and a revised engineering or business record are not automatically the same event.
19. Status
A recorded condition at a stated moment, such as proposed, reviewed, active or closed; status must not be mistaken for a promise.
20. Scope
The precise population, asset, location, date range or activity covered by a claim; translation must carry exclusions and boundaries.
21. Evidence
The observation, record or test that supports a statement; words such as confirmed and verified should be reserved for the corresponding evidence.
22. Owner
The person or function accountable for a record or decision, not necessarily the person who physically possesses the item.
23. Traceability
A usable link from a claim through its supporting records to the origin, date, version and responsible reviewer.
24. Qualification
A condition or limitation that modifies a statement; removing a qualification can convert a correct sentence into a misleading one.
Twenty-four original worked translation cases
Every miniature source is invented for teaching, not quoted from an ISO standard or a real customer’s records. The ‘faithful English sense’ line states the proposition to preserve when translating into another language. The ‘tempting mistake’ line illustrates a plausible but misleading change in meaning. Translate neither status nor measurement by intuition.
Case 1: New laptop allocation
Example source: “Device A-015 assigned to Sales; ownership retained by Central IT.”
Tempting but inaccurate rendering: “Sales owns the new laptop.”
Faithful English sense to preserve: “A-015 is assigned for Sales use while Central IT retains ownership.”
Assignment is operational custody, not transfer of title. A translation that deletes ‘retained’ changes responsibility for repair, insurance and eventual disposal.
Reviewer action: Compare the owner and assignee fields with the register. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 2: Unconfirmed purchase
Example source: “Purchase request PR-90 submitted; purchase order not issued.”
Tempting but inaccurate rendering: “The order has been placed.”
Faithful English sense to preserve: “A purchase request was submitted; no purchase order has yet been issued.”
A request can be declined or changed. Procurement verbs often merge ‘request’, ‘order’, ‘purchase’ and ‘receive’; here they are separate workflow states.
Reviewer action: Match the purchasing system’s event timeline. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 3: License allocation
Example source: “40 user subscriptions purchased; 34 accounts provisioned.”
Tempting but inaccurate rendering: “Forty users are active.”
Faithful English sense to preserve: “Forty subscriptions have been purchased and 34 accounts have been provisioned.”
Provisioning is not evidence of current activity. The licensed count and provisioned count answer different questions.
Reviewer action: Confirm the SKU, counting method and provisioned-account export. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 4: Discovery scan
Example source: “Scanner detected 12 installations; entitlement review pending.”
Tempting but inaccurate rendering: “Twelve licensed copies verified.”
Faithful English sense to preserve: “Twelve installations were detected, while entitlement review remains pending.”
Discovery does not establish permission. Preserve ‘detected’ and ‘pending’ even when readers prefer a simple yes-or-no outcome.
Reviewer action: Review collection window and license agreement separately. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 5: Cloud billing
Example source: “Eight compute instances observed at 09:00 UTC.”
Tempting but inaccurate rendering: “Eight instances run all month.”
Faithful English sense to preserve: “Eight instances were observed at 09:00 UTC, without a monthly usage conclusion.”
A point-in-time metric must not become a period average. Time zone and window are part of the evidence.
Reviewer action: Check cloud report granularity and timestamp. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 6: Repair status
Example source: “Device awaiting vendor assessment; fault cause unknown.”
Tempting but inaccurate rendering: “Vendor confirmed hardware failure.”
Faithful English sense to preserve: “The device is awaiting vendor assessment and the fault cause is not yet established.”
Receiving a support ticket is not a diagnosis. Translators should keep unknown causes explicit.
Reviewer action: Compare vendor ticket and local service desk status. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 7: Temporary loan
Example source: “Spare laptop loaned until 30 June; return not recorded.”
Tempting but inaccurate rendering: “Loan ended on 30 June.”
Faithful English sense to preserve: “The loan period was set to end on 30 June; no return has been recorded.”
The planned end date does not prove actual recovery. Keep the open return action in the recipient language.
Reviewer action: Look for a dated return acknowledgement. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 8: Software renewal
Example source: “Renewal quotation expires 15 August; approval pending.”
Tempting but inaccurate rendering: “Subscription renewed until August.”
Faithful English sense to preserve: “The renewal quote is valid until 15 August and has not yet been approved.”
A quote validity date is not a license expiration or a renewal confirmation.
Reviewer action: Check exact contract and procurement approval records. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 9: Reseller assurance
Example source: “Reseller states five licenses available; publisher validation not obtained.”
Tempting but inaccurate rendering: “Publisher confirmed five licenses.”
Faithful English sense to preserve: “A reseller reports five available licenses; the publisher has not validated the claim.”
Attribution determines evidentiary strength. The translator must not promote a commercial statement into publisher confirmation.
Reviewer action: Keep supplier name and verification status. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 10: Regional restriction
Example source: “Access permitted only to licensed EMEA affiliates.”
Tempting but inaccurate rendering: “Global access permitted.”
Faithful English sense to preserve: “Access is limited to affiliates that meet the specified EMEA license definition.”
Regional and affiliate definitions are contractual, not cultural generalizations. Do not translate a geographic boundary into worldwide coverage.
Reviewer action: Compare defined terms in signed agreement. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 11: Metered usage
Example source: “Estimated 3,200 API units during sampled period.”
Tempting but inaccurate rendering: “Exactly 3,200 units were billed.”
Faithful English sense to preserve: “A sample-based estimate of 3,200 API units is reported for the stated period.”
An estimate may differ from invoice charges. Maintain the unit definition and sample limitations.
Reviewer action: Reconcile with metering policy and invoice. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 12: Asset exception
Example source: “Exception EX-12 approved for 30 days with mitigation.”
Tempting but inaccurate rendering: “Asset meets all controls.”
Faithful English sense to preserve: “A temporary exception exists, with a 30-day limit and defined mitigation.”
Risk acceptance under conditions is not conformity. The expiry date and mitigation are integral to meaning.
Reviewer action: Check recorded approver and expiration. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 13: Disposal request
Example source: “Retirement proposed; deletion certificate not yet available.”
Tempting but inaccurate rendering: “Device wiped and disposed.”
Faithful English sense to preserve: “Retirement is proposed and no deletion certificate is yet available.”
Proposed work and completed evidence should be translated separately. This is particularly important for storage devices.
Reviewer action: Inspect service order and deletion-evidence register. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 14: Media destruction
Example source: “Recycler collected ten drives; destruction report pending.”
Tempting but inaccurate rendering: “Ten drives securely destroyed.”
Faithful English sense to preserve: “Ten drives were collected, but destruction has not yet been reported.”
Collection is a custodial handoff. The subsequent treatment requires independent evidence.
Reviewer action: Match serials and recycler receipt. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 15: Data erasure
Example source: “Erase job completed on nine of ten drives; one failed.”
Tempting but inaccurate rendering: “All data erased successfully.”
Faithful English sense to preserve: “The erasure job completed on nine drives and failed on one.”
A partial result cannot be rounded into full success. The failed media needs explicit exception treatment.
Reviewer action: Verify item-by-item erasure status. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 16: Virtual device name
Example source: “Hostname changed; stable instance ID unchanged.”
Tempting but inaccurate rendering: “A replacement server was deployed.”
Faithful English sense to preserve: “The instance was renamed, but its stable ID remained the same.”
Renaming and provisioning are different lifecycle events. Preserve the immutable field.
Reviewer action: Compare instance ID before and after. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 17: Acquired subsidiary
Example source: “License transfer subject to publisher consent.”
Tempting but inaccurate rendering: “Licenses automatically transferred.”
Faithful English sense to preserve: “License transfer requires the publisher’s consent and is not yet established.”
Corporate acquisition does not by itself settle third-party contract rights.
Reviewer action: Read assignment clause and consent status. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 18: Audit sampling
Example source: “15 of 100 devices sampled; no discrepancy observed in sample.”
Tempting but inaccurate rendering: “All 100 devices compliant.”
Faithful English sense to preserve: “No discrepancy was observed among the 15 sampled devices.”
Sample observations cannot simply be generalized to the population without a specified statistical method.
Reviewer action: Retain sample size, selection method and reporting period. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 19: Missing invoice
Example source: “Installed product has no linked purchase record.”
Tempting but inaccurate rendering: “Software is unlicensed.”
Faithful English sense to preserve: “No purchase record is linked to the installed product in this system.”
Missing evidence is not itself conclusive proof of lack of rights. The report should trigger investigation.
Reviewer action: Check other purchasing channels and contracts. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 20: Contract cancellation
Example source: “Cancellation submitted, effective after notice period.”
Tempting but inaccurate rendering: “Subscription terminated immediately.”
Faithful English sense to preserve: “A cancellation request has been submitted; its effective date follows the required notice period.”
Submission and effective termination are different. Payment or access obligations may persist.
Reviewer action: Read the actual notice clause and dates. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 21: Maintenance coverage
Example source: “Hardware support until 31 December; software updates excluded.”
Tempting but inaccurate rendering: “Full support through December.”
Faithful English sense to preserve: “Hardware support continues through 31 December, excluding software updates.”
A general support label would overstate covered services. Preserve the exclusion.
Reviewer action: Inspect support plan and product identifiers. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 22: Warranty remark
Example source: “Warranty eligibility under review pending serial verification.”
Tempting but inaccurate rendering: “Warranty claim accepted.”
Faithful English sense to preserve: “Warranty eligibility has not been decided because serial verification is pending.”
The same claim can move through received, reviewed, eligible, approved and paid statuses. A translator cannot skip steps.
Reviewer action: Confirm the provider’s recorded decision. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 23: Inventory valuation
Example source: “Book value shown for accounting; resale value not assessed.”
Tempting but inaccurate rendering: “Market value verified.”
Faithful English sense to preserve: “The reported figure is accounting book value, not an assessed resale price.”
Different valuation bases produce different decision implications, even for the same device.
Reviewer action: Keep basis, currency and reporting date. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Case 24: Cross-system reconciliation
Example source: “Ten unmatched entries remain after import.”
Tempting but inaccurate rendering: “All records synchronized successfully.”
Faithful English sense to preserve: “Ten entries remain unmatched after import and require reconciliation.”
Technical completion of an import does not prove content reconciliation. The exception count is part of the outcome.
Reviewer action: Check error log, match policy and unresolved IDs. Confirm the recipient could take the same action from either version, including the same limits, date and decision-maker. If an essential datum is absent, label it as not supplied and request clarification rather than adding it to the target text.
Ten-stage translation and release workflow
1. Inventory the sources
Collect the controlling document, attachments, tables, system field names, version history, intended recipients and known restrictions. Do not translate from screenshots alone when a structured source is available. Mark each missing item instead of guessing its contents. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
2. Classify the content
Separate stable identifiers, numerical data, narrative explanations, decisions, labels, warnings and reusable terminology. A proper name and a sentence need different handling. Keep a record of elements that must remain character-for-character identical. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
3. Define the reader’s decision
Write down what the target-language reader will do: compare a measurement, authorize work, file a report, answer a survey, purchase equipment or interpret a warning. The chosen translation must support the same decision under the same conditions. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
4. Build a concept glossary
Record the source expression, its agreed meaning, equivalent target-language term, approved abbreviation, disallowed false friends, owner and date. Establish context before selecting a dictionary equivalent. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
5. Translate one whole unit
Work with sentences and linked tables rather than isolated tokens. Keep the actor, action, object, condition, time, quantity and evidence strength together. When a noun phrase omits a verb, preserve that omission unless the source authority clarifies it. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
6. Check numbers and codes
Use an automated or independent manual comparison for IDs, units, ranges, dates, revision letters, mathematical signs and logical operators. Preserve machine keys unchanged unless an approved localization specification requires otherwise. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
7. Review uncertainty and authority
Compare words such as proposed, observed, estimated, approved, compliant, pending and complete. A translator is not authorized to strengthen a tentative statement or replace an unknown with a convenient answer. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
8. Run a bilingual expert review
Ask an experienced subject specialist to compare representative complete records, not merely approve elegant prose. Give the reviewer the source, target, glossary, known ambiguities and decision context. Capture objections with line identifiers. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
9. Test the delivery format
Open the final file in the recipient’s real tool, printed form or interface. Check clipped labels, bidi text, accents, field lengths, table alignment, hyperlinks, accessibility and whether identifiers remained searchable. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
10. Release with a correction route
Record reviewer, version, locale, approved limitations and date. Publish a correction pathway and identify whether a later update changes only the translation or also the underlying source record. In this IT asset management context, put asset identifiers, contract rights, lifecycle states and evidence dates beside the translated text so the checker can compare meaning and evidence before release.
Frequently asked questions
Can I translate asset IDs and serial numbers?
Usually preserve them exactly as identifiers. Translate adjacent descriptions into separate fields, and confirm whether a particular system supports localized display labels. Changing a key can make an audit record irreconcilable.
Does an installation prove the company has a license?
No. Installation evidence and contractual entitlement answer different questions. You need the relevant agreement, counting rule and population before making a compliance conclusion.
What if the source calls a license a ‘seat’?
Use the contract’s defined metric. If ‘seat’ is not defined, keep it as an attributed source term, explain the ambiguity and ask the asset manager or commercial reviewer to confirm the intended unit.
Can automated translation handle an inventory spreadsheet?
It can assist with narrative cells when confidentiality and tool policies permit, but it must not rewrite identifiers, formulas, controlled states or licensing terms without validation. Test import and reconciliation after translation.
How should disposal status be translated?
Use exact stages: requested, approved, collected, erased, verified, destroyed or recycled when the evidence supports each. A disposal plan alone cannot support a claim that all data were removed.
How can a multilingual audit report avoid overstating compliance?
Preserve the sample and date range, distinguish observations from findings, name limitations and keep reviewers’ decisions separate from submitters’ assertions. Match each conclusion to its evidence pointer.
Is ISO/IEC 19770-1 a license-usage permission document?
No. It describes requirements for an organizational IT asset management system. Actual use rights come from applicable contracts and law; the standard does not replace those sources.
Should software names be translated?
Preserve product names, SKUs, edition identifiers and official legal names as required. Translated explanations can help readers, but an altered product identity could make reconciliation or entitlement checking fail.
How do I translate an unknown asset owner?
Say the owner has not been established or recorded, whichever the source actually means. Do not assign the department that appears nearest in the spreadsheet simply to fill a blank.
What is the final quality test?
Have a subject reviewer answer the same entitlement, quantity, lifecycle and disposal questions from both versions. If the two readers reach different decisions, the translation is not ready for publication.
Four-week practice plan
Week 1: Inventory and identifiers
Use a fictional register of twenty devices and five licenses. Mark immutable identifiers, descriptions, owners, custodians, dates and lifecycle states. Translate the human text into one target language while leaving keys untouched. Re-import the output and try to match every row. Resolve differences before moving forward.
Keep a short record of the source statement, your proposed translation, the identified ambiguity, the reviewer decision and the revised wording. Test a second language direction where competent reviewers are available. A successful exercise is one in which the decision and its limits remain the same, not one that merely reads elegantly.
Week 2: Entitlement and evidence
Prepare a two-page fictional licensing pack with purchase quantities, detected installations, active users and an exception. Translate it and ask another reader to say which rights are established and which questions remain. Write an issue register for ambiguous units, contracts or dates.
Keep a short record of the source statement, your proposed translation, the identified ambiguity, the reviewer decision and the revised wording. Test a second language direction where competent reviewers are available. A successful exercise is one in which the decision and its limits remain the same, not one that merely reads elegantly.
Week 3: Life cycle and disposal
Create a handover chain with loan, repair, retirement, wipe and recycler collection events. Deliberately leave two events pending. Test whether reviewers can identify the missing evidence in both languages, and revise any wording that makes future action sound completed.
Keep a short record of the source statement, your proposed translation, the identified ambiguity, the reviewer decision and the revised wording. Test a second language direction where competent reviewers are available. A successful exercise is one in which the decision and its limits remain the same, not one that merely reads elegantly.
Week 4: Audit and release
Assemble a short bilingual report with a dashboard, glossary, twenty source lines and linked evidence. Ask a subject expert to inspect numbers, contract caveats and uncertainty, then test the final file in the intended application. Record change log, sign-off and correction route.
Keep a short record of the source statement, your proposed translation, the identified ambiguity, the reviewer decision and the revised wording. Test a second language direction where competent reviewers are available. A successful exercise is one in which the decision and its limits remain the same, not one that merely reads elegantly.
How this guide fits the wider learning system
This is a focused practical translation lesson on IT asset management. It is not a replacement for ISO’s copyrighted standard, jurisdictional rules, an accredited professional judgment or the controlling documents held by an organization. The official catalogue summary establishes the standard’s general scope; examples here are independently authored illustrations and must not be presented as certification criteria. The master translation architecture explains cross-language meaning transfer; this article solves one much narrower document problem.
For broader principles, read The Master Art of Translation — complete system. For word learning, use the protected Vocabulary Learning Hub. To understand grammar, register and meaning, follow How English Works: Translation and Meaning Across Languages. These are adjacent concept owners, not pages this guide replaces.
Source for edition and public scope: ISO/IEC 19770-1:2017 — official ISO catalogue. The edition and status were checked on 5 November 2026. Where a standard has amendments or later revisions, check the purchaser’s controlled documents and current catalogue record before making a compliance claim.