BidScript supports international tenders and regional submission requirements in two different ways. Which one you use depends on a practical question: how comfortable is your team writing and editing in the submission language?
Generate in the target language | Drafts are produced in the submission language from the start. Best when your team can review and edit confidently in that language. |
Draft, then translate | Drafts are produced in your team's working language, collaborated on and finalised, then translated shortly before submission. Best when your team works most effectively in a different language from the one the buyer requires. |
Both are supported, and you can use them on different projects - or different questions - as it suits you.
Which to choose
The second method exists because reviewing is harder than reading. A team can often read Spanish comfortably but still write, challenge and refine much faster in English.
If your team collaborates most naturally in English and the submission must be in Spanish, generate the drafts in English, run the whole review and refinement cycle in English, and translate into Spanish only once the answer is final. You get the quality of a team working in its strongest language, and a submission in the language the buyer asked for.
If your team is genuinely fluent in the submission language, generating directly in it avoids the extra step altogether.
Method 1 - Generate in another language
Open the Language Selector in the draft configuration modal
Choose your output language.
Generate the draft.
The default follows your team's configuration, which is English (UK) until changed. Team defaults are set in Settings → Teams.
Confirm the language before you generate. Changing it afterwards means regenerating the draft or translating it.
Languages available for generation
English (UK) | English (US) | German | French |
Italian | Spanish | Dutch | Norwegian |
Danish | Czech | Swedish |
|
Method 2 - Translate an existing draft
Once a draft exists, you can translate it from within the Answer Workspace. You can translate the whole answer, or only a passage you have selected.
Open the question's Answer Workspace.
In the top toolbar, click Tools.
Click Translate.
Choose whether to translate the entire answer or a selected area of text.
Choose the language to translate into.
Languages available for translation
English | American English | German | French |
Italian | Spanish | Dutch | Norwegian |
Danish | Czech | Swedish |
|
You can also ask BidBot to translate individual sections while keeping their tone and structure. See BidBot in the Answer Workspace.
Best practice
Decide which method you are using at the start of the bid, not partway through it.
If you are translating, do it once the answer is final. Translating a draft that is still changing means translating repeatedly.
Have someone who reads the submission language check the translated output before it goes out, particularly for technical or compliance wording.
Confirm your generation language before generating — correcting it afterwards costs a regeneration.
Related articles
Generating drafts — first drafts, bulk generation and draft configuration.
BidBot in the Answer Workspace — translating individual sections while preserving tone.
Exporting Your Final Answers — producing the submission once the language is right.