Energy & environment
translated for every reader
A wind or solar project writes for a permitting authority, for its neighbours, for its lenders and for the crews who will maintain it โ often in the same week. We translate all four, in four registers, off one glossary.
- Impact assessments and permit files
- Grid connection and tender packs
- Operation and maintenance manuals
- Community and stakeholder material
- One term list across the whole project
Get your quote
Send the file, or the part of it you can share, and we will reply with a fixed price.
Received!
Our team will get back to you very shortly.
Four readers, one set of terms
A renewable project produces, in the same week, documents for people who have nothing in common except the project. The permitting authority reads for form: the right file, in the right language, with the annexes it expects, and it will send the whole thing back over any of the three. Landowners and neighbours read to find out what is going up beside them, and they read closely. Investors and lenders read for risk, and read fast. The maintenance crews read the manual with gloves on, at the top of a tower or inside a substation.
Four registers, then. The leaflet that lands in a letterbox cannot be written like the technical annex, and the annex cannot be written like the leaflet. What has to be identical across all four is the terminology. If a component, a connection point or a habitat is called one thing in the application and another in the annex behind it, somebody asks which one you meant โ and that question gets asked on the record, at the worst possible moment.
So the term list is settled before the first document goes out, and everything after it draws from the same list: the application, the annexes, the tender pack, the land agreements, the leaflet, the manual that stays in the substation. It lives in a termbase and a translation memory we maintain for the project, so version three of a document costs the difference from version two, and a term agreed in year one is still the term in year six.
Happy to be of service,
Gabriel Brunner, Founder
Documents we translate
From a two-page grid application to a consent file with every specialist annex attached. If yours is not listed, send it anyway.
Four steps to your translation
- 1
Send us the file
The whole consent file, a single annex, or the manual. Tell us the market it goes to and who reads it โ the register follows from that.
- 2
Receive your quote
A fixed price and a delivery date, confirmed before you commit, with repetition and anything already translated for the project discounted.
- 3
Approve the quote and the term list
Say yes and we start. We send the terminology we propose; your engineers correct it once, and from then on it is fixed for every document in the project.
- 4
Receive your translation
In your source format, revised by a second translator, with figures, units, coordinates and site names checked twice.
What holds a project file together
One glossary, four registers
The application, the technical annex, the investor summary and the leaflet are written for different people and should not sound alike. The words for the things in them do not change.
Filed in the language it is read in
Authorities expect filings in the language of the market. We ask what the receiving office wants, and in what form, and confirm it before you commit to anything.
Material a neighbour can read
Consultation notices, leaflets and hearing material in plain language โ using the same terms as the technical file, so nobody can argue the two describe different projects.
Terminology that stays with the project
Your term list and past translations are kept on file, so the manual written in year six matches the permit filed in year one, and text you have paid for is not charged twice.
