Parallel abstract text sheets and term cards illustrating a translation delivery package.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

Before quoting a translation, agree on the source version, language pair, intended reader, purpose and delivery format. A useful offer explains how you will handle terminology, questions, checking and later source changes. Knowing two languages does not, by itself, establish that you can translate a particular technical or regulated document accurately.

This is a preparation workflow for a small written translation assignment. It is independent editorial guidance, not a report of a Fovza client project, translator certification or marketplace approval. The sample below is invented to explain decisions. It contains no customer documents or tested earnings.

Define the task before you quote

The American Translators Association's project checklist asks translators to clarify the service, whether files can be opened and read, the translation's purpose and its audience. It also raises tools and editing responsibilities. The article dates from 2017; we use it for those general scoping questions, not as a current fee schedule or contract template.

Source: ATA's questions before accepting a translation project. Read 2026-10-26.

Write a brief that someone else could check against the finished files. “Translate our website” leaves too much unresolved. Specify which pages and embedded elements are included, which source language and target locale apply, and whether the client expects translated text only or also work in a publishing system.

Ask who will read the result and what they need to do. A product support page, an internal training note and advertising copy can use the same vocabulary for different purposes. Identify the person authorized to answer questions and approve the final wording. If the subject exceeds your competence, narrow the assignment or decline it before a deadline creates pressure to guess.

Inspect the source package

Make an inventory before measuring the job. Open each file, check whether its text is editable, and note tables, diagrams, captions, links and text inside images. A word count from the main document may omit several of those items. Record what is missing instead of quietly treating it as excluded.

Keep the source supplied for the quote separate from later revisions. Give the working copy a clear version identifier and date, and agree on a cutoff for changes. If the client replaces a page during translation, compare the replacement with the agreed version and explain the effect on scope and delivery time.

Check that you can return the requested format. Text pasted into a document differs from a translated design file whose line breaks, fields and images must still work. Test a small export with your own material. Do not promise that a format will survive conversion without examining it.

Use terminology resources with judgment

ProZ describes language-professional directories, job listings and terminology resources. Those resources may help you investigate usage or locate professional contacts. A glossary entry or directory profile does not establish that a term fits your client's context, that a listing will lead to work, or that your own qualifications meet a project's requirements.

Source: ProZ's service overview. Read 2026-10-26; this guide has not tested membership, applications or paid assignments.

Prepare a small term list for the actual project. Include the source term, proposed target term, context and decision status. Add the client's preferred wording when supplied, but flag a choice that seems inconsistent with the intended meaning. Keep a question separate from an approved decision so an unresolved suggestion does not become the default through repeated copying.

For names, measurements and placeholders, decide what must remain unchanged and what needs localization. A replacement such as a date format can be technically correct yet unsuitable for the intended reader. Never invent a stronger product claim to make the target wording sound smoother.

Build a practice delivery package

For an invented sample, imagine a short help page for a reusable lunch container. Create your own source text rather than taking a manufacturer's description. The exercise is to return a useful package, not to suggest that you translated a real product or validated a safety claim.

Your practice package could contain:

  • The translated page, with a version identifier matching the source.
  • A term list covering the product name, parts and repeated actions.
  • An open-question sheet listing ambiguous source phrases and their locations.
  • A delivery note explaining what was included and what still needs approval.

Suppose your invented source says “close firmly.” The surrounding instructions do not explain how the user knows the closure is complete. Record the ambiguity rather than adding an unsupported mechanism. This example tests how you preserve meaning and ask a useful question; it does not supply wording for a real product instruction.

If your sample contains a placeholder, link or numbered step, check that it remains in the right place. A fluent paragraph with a broken variable can still fail as a deliverable. Keep the exercise outside specialist material whose mistakes could affect health, legal rights or safety.

Separate review passes

Review the translation against the source for missing content, changed meaning and unresolved questions. Then read the target text on its own for coherence, consistent terminology and the intended tone. A final file check should cover layout, links, placeholders and the exact version being delivered.

These are proposed review passes, not a claim that following them guarantees accuracy. If the scope includes an independent editor, arrange that review and its cost before accepting the work. Do not describe your own second reading as independent review.

Use the question sheet to make the remaining decisions visible. Group questions by location and explain what information would resolve each one. Avoid sending a vague request such as “please check the translation” when the client needs to decide between two meanings in the source.

Agree on revisions and release

Distinguish corrections to the agreed translation from changes to the source or a new preferred tone. Set a review window, the person who can consolidate feedback and the format for returning it. Several reviewers editing separate copies can create conflicting instructions; a named approval route helps expose those conflicts.

Quote for the work you have actually scoped, including file preparation, terminology research, communication, checking and any agreed second reviewer. This guide gives no market rate or income prediction. Confirm payment terms and local business requirements for the actual engagement before accepting it.

Ask permission before uploading confidential material to an external tool or sharing it with another person. Agree on delivery, retention and deletion arrangements. A convenient application is not automatic authorization to process someone else's files.

Decide whether you are ready to offer the service

Use your practice package to identify gaps: a term you cannot justify, a format you cannot preserve, or an instruction you cannot explain without guessing. Improve those parts before offering the same scope to a client. Keep a portfolio sample only when you have the rights and permission to show it.

For broader options, see remote side hustles. If the task is checking already written text rather than translating it, compare the boundaries in proofreading services. Your next step is a clear sample brief and delivery package, not a promise of demand or admission to a marketplace.