Agree on quality standards and data handling before delivery.
LIG builds content purpose, review scope and data requirements into project preparation. We agree with clients how content will be handled, how quality will be assessed, and who will review and approve it.
A quality process from brief to delivery
1 Confirm requirements: define target markets, languages, purposes, content volume, timing and acceptance criteria in a project brief.
2 Prepare terminology and materials: confirm terms, style, reference files, tool permissions and questions the client needs to answer.
3 Produce the draft or content: use human translation, AI assistance, original writing or multimedia production as agreed, keeping versions aligned.
4 Review and revise: check meaning, facts, terminology and expression within the agreed scope, record issues and make changes. Refer matters needing professional judgement to the client.
5 Check before delivery: review key figures, omissions, formatting, variables and display issues, and verify how feedback and the delivery checklist have been handled.
6 Deliver and maintain versions: submit the work and agreed issue records, support client review, and maintain terminology and content resources for later updates.
AI use and human responsibility
Each project can specify permitted tools, content categories and processing steps, along with the extent of human editing, sample checking or full review. Specialist approval of financial, medical, legal and other important content rests with the client and relevant professionals.
Data handling and access
For personal data, business secrets or unpublished materials, first confirm processing purposes, authorised people, service providers, locations and transfer methods. Model calls, file storage, technical support, logs and backups are included in project discussions.
If external AI use must be restricted, tell us before the project begins. We will confirm suitable processing environments, tools and human-led options. Without project approval, we do not submit client materials to external AI tools that have not been agreed.
Retention, reuse and deletion
Both parties agree on retention periods and maintenance purposes for source files, translations, termbases, translation memories and content resources. Additional uses such as reuse across projects, model training, public case studies or demonstrations require separate permission and confirmation of applicable conditions.
Supplier assessment and incident communication
If a project requires procurement or security assessment, provide the requirements early so we can check them against actual systems and delivery conditions. Project documents can define confidentiality duties, subcontracting, incident contacts and notification processes.
Protecting information in website enquiries
For an initial enquiry, a brief project outline and contact details are enough. Please do not send identity, account, transaction or other sensitive data through the general enquiry form. We can agree on a file-submission method after discussing your needs.