ADMAS Start a project
Freelancer templates · Practical guide

Translation delivery note & handoff checklist

Deliver files with version, language, checks, known issues, terminology updates, reviewer status, installation instructions, and a clear acceptance path.

Published
2026-08-20
Updated
2026-08-20
Last verified
2026-08-20
Review cadence
Every 365 days
Disclosure
none
Version 1.0 · CC BY 4.0

Use the worksheet

Inputs stay on this page and are not submitted or saved.

Download the delivery-note template

Use references that match the quote and invoice.

List path, filename, format, locale, version, and status.

Record linguistic, terminology, tag, placeholder, layout, timing, format, build, and accessibility checks as relevant.

Name reviewers, dates, pending market approval, and provenance.

Give severity, affected locale or asset, owner, workaround, and next action.

Include environment, order, dependencies, and rollback.

State the review window, contact, and information required for a report.

A delivery is more than an attachment

The receiver should be able to identify what was delivered, install or import it correctly, understand its review status, and find unresolved questions without reconstructing the project history.

  • Use stable filenames and checksums where appropriate
  • Keep locale labels consistent
  • Identify the exact source version
  • Separate final, reference, and working files
  • State what was tested and what was not
  • Give one route for defect reports

Compact status language

READY — reviewed and passed the stated acceptance checks
READY WITH NOTE — usable; named non-blocking issue remains
REVIEW REQUIRED — delivered for client or market review, not publication
BLOCKED — incomplete or unsafe to publish; reason and owner named

Frequently asked questions

Should the delivery note include every QA check?

Include the checks promised in the scope and any result that changes how the client should use the delivery. Attach detailed reports when the summary would become unreadable.

How should corrected files be delivered?

Issue a new version, preserve the prior delivery reference, list changed files and defects, rerun affected checks, and make the current approved version obvious.

How this was built

Admas designed this plain-language working template for transparent language-service delivery. The downloadable file contains no macros, remote formulas, tracking links, or hidden fields. Adapt it to the project, jurisdiction, client requirements, tax rules, language pair, service, and professional advice relevant to you.

Source register

Official and primary references reviewed for this page.

  1. Guide to Buying Translation ServicesAmerican Translators Association · verified 2026-08-20
  2. Creative Commons Attribution 4.0 InternationalCreative Commons · verified 2026-08-20