Subject and audience
Describe the product or process and whether readers are specialists or general users.
Document types / technical
Manuals, specifications, and product documentation rely on consistent terminology. Give us the subject area, intended reader, and any reference material so the scope can be reviewed.
Updated 8 October 2026
Start here
Include the approximate length, recipient, and deadline if you know them. We’ll review your request and may contact you by email about next steps.
What to know
Technical projects often include text outside the main paragraphs. Calling it out early avoids gaps in the quote.
Describe the product or process and whether readers are specialists or general users.
Mention labels, diagrams, tables, screenshots, or interface strings that need translation.
Share existing Slovak product copy, a term list, or style guidance if you have it.
Document guide
These notes help you describe your request. The receiving organization’s current instructions should guide the final requirements.
A maintenance technician, installer, support agent, and end user may need different terminology and detail. Describe the product, model or software version, and what the Slovak reader must be able to do. Say if the document is instructional, descriptive, or a record of tests or specifications.
List labels in diagrams, safety messages, UI strings, tables, captions, screenshots, callouts, units, and part numbers. Explain which items must be translated and which codes or product names must remain unchanged. Counting only body text can miss a meaningful part of the job.
If available, identify the approved revision, editable source files, terminology list, product screenshots, earlier Slovak releases, and a contact who can answer technical questions. Note whether referenced figures or linked documents are part of the requested scope.
Tell us whether the translation will be reviewed by a subject specialist, entered into software, published as a manual, or filed with another party. Clarify required output files and target date. If a safety or regulatory review is needed, arrange that review with a qualified party; a translation request alone does not establish compliance.
16 guides
Find preparation guidance for the current manual, product record, or controlled procedure. Include embedded text, annexes, and the responsible technical or regulatory reviewer when defining scope.
No guide matches that search. Try a broader document name, or describe your document in the quote form.
How it works
Tell us what the document is, who needs the Slovak translation, and when you need it. The first form does not require a file.
Choose the type and tell us where the translation will be used.
Include the approximate length, deadline, and any instructions from the recipient.
We review the request and may contact you by email if more detail is needed.
Frequently asked
Answers to common questions before you request a quote.
Tell us which layout elements are important. File type and editable source material affect what is practical.
Yes, identify every image with text and whether you need the words translated, the image recreated, or a separate text list. The requested output affects scope.
Tell us which identifiers are controlled and whether units require any change for the target reader. Do not assume a unit conversion is part of translation.
Ready when you are
Start with a few details. No file upload is needed for the first step.