Business supplies and services: Enquiry form for localisation providers
An enquiry form for localisation providers that gathers source strings, screen context and release details, so the language team knows where every string appears before translation starts.
What makes an enquiry complete for localisation providers.
A localisation enquiry often arrives as an export file full of lines and the question of whether it can be ready in a handful of languages for the next release. What is missing is exactly what translators need: which screen a string is on, whether it is a button, a heading or an error message, how much space there is, and what that variable in the middle of the sentence stands for. Localisation providers who start from such a file end up with a list of questions for a developer who has already moved on to the next release. An intake has to collect that context before work begins, without burying the product team in an endless form.
Enquiry form for localisation providers
Example- 1
Describe product and release
DoneThe form first asks about the product, the target languages, the expected release date and whether this is a first localisation or an update.
- 2
Supply strings with context
In progressNext the team uploads the source strings and indicates how context is available: screenshots, a test environment, comments in the source file or a mix.
- 3
Hand over to the language team
NextThe project manager receives a summary with languages, volume, available context and open questions.
From form to assessed enquiry.
Describe product and release
The form first asks about the product, the target languages, the expected release date and whether this is a first localisation or an update. For an update it asks about the previous version, so earlier translated strings are recognised. A product manager can answer all of this without pulling in a developer.
Supply strings with context
Next the team uploads the source strings and indicates how context is available: screenshots, a test environment, comments in the source file or a mix. The form also asks about character limits and whether strings contain variables or plural forms. Missing context becomes a point of attention rather than a blocker.
Hand over to the language team
The project manager receives a summary with languages, volume, available context and open questions. They see straight away whether strings lack context, whether character limits are known and whether terminology exists from earlier projects. With that they can assemble the language team and ask the developer targeted questions.
Enquiries in one place, not the inbox.
Product teams supply strings as an export from their codebase, through a translation platform or sometimes as a spreadsheet. The form accepts those forms and asks for a sample if the format is unfamiliar. Screenshots can come as a folder or link. The product team owns the source strings and release planning; you own the translation memories and terminology that grow out of the work. The enquiry goes to the system where you manage projects.
Screenshots or test environment access
Screenshots are quick to supply and safe, but go stale as soon as the interface changes. Access to a test environment gives current context but requires accounts and directions to each screen. For small updates screenshots usually suffice; for a first localisation or a major redesign, test environment access is worth the effort.
One enquiry or one per language
A product team wanting several languages at once prefers to submit a single enquiry. Still, languages sometimes have their own timeline, for example because one market launches later. The form allows a separate date per language within the same enquiry, so the language team knows which take priority without spawning separate projects.
Supply terminology or build it
Some product teams have a glossary with fixed terms and translations. Others have nothing, or only a brand guide in the source language. A supplied glossary brings consistency quickly but sometimes needs cleaning up. Building one during the first project takes a little more review time but yields a list that fits the product.
How it already runs at similar businesses.
IP Camera Installatie
From camera system to installation. Everything connected.
Read the storyMaison Vert
From bouquet to delivery. Thoughtfully connected.
Read the story
MJ Tattoo Studio
From inspiration to a personal consultation.
Read the storyWhich questions the form asks.
From the start the form asks for product and release details, strings and context as uploads, character limits and variables, and produces a summary for the project manager. Together we send through an ordinary update of a web application in a few languages, and a first localisation where the context consists only of loose screenshots. Fetching strings from your translation environment and recognising strings from a previous version can be switched on later.
View pricingHosting and careGood to know.
Explore pricing and optionsWhat if the product team has no screenshots?
The enquiry can still proceed. The form flags strings without context and the project manager asks specifically for a few screens or temporary access to a test environment. Meanwhile translators can start on strings whose purpose is clear from the key name or comment.
Can we recognise which strings were translated before?
Yes, if you know the previous version. The form asks which version the update builds on, and on arrival unchanged, modified and new strings are separated. The project manager sees immediately how much genuinely new work there is.
How do we handle character limits?
The form asks whether limits exist and how they are supplied, for example as a column in the file or a comment per string. If they are unknown, it becomes a point for screen testing. Translators see the limit next to the string as soon as it is available.
Can a developer add files after submitting?
Yes. After submission the product team can add extra strings or screens through a link. These are attached to the enquiry as additions with a date, so the project manager sees what came in after the first overview and whether it affects the schedule.
What often connects to this.
- Website for localisation providersA website for localisation providers that explains how software, apps and help content are translated and tested per release, so a product team knows what to supply and when.
- Quotation software for localisation providersQuotation software for localisation providers that prices word volume, previously translated strings and testing per language separately, so a product team sees where release costs come from.
- AI enquiry assistant for localisation providersAn AI enquiry assistant for localisation providers that answers translators and product teams about string context, terminology and per product arrangements, using approved sources only and handing over when unsure.
Enquiries that arrive complete.
Start with a short intake. Then we schedule a call to show the software with your services, team and way of working.
WhatsAppinfo@vorlyo.com Enquiry form for localisation providers: source strings, screen context, target languages and release date in one enquiry, complete for the language team.
- Describe product and release
- Supply strings with context
- Hand over to the language team