Manage the work, share the memory.
Assign documents with due dates and watch the progress arrive as the work happens. Publish a translation memory or a term base and it is consulted on every teammate’s machine — end-to-end encrypted, if you turn it on. Everyone still translates in their own app, on their own machine.
Nobody should have to ask how it’s going
Chasing a status is a message the translator has to stop and answer, and an answer the manager has to remember to ask for. Contextra reports progress as the work happens, so the board is already right when you look at it.
Assign
A manager uploads the document, sets the language pair and a due date, and it appears in that translator's app.
Watch it happen
Progress reports itself as the work goes: how much is translated, and within that, how much has actually been looked at.
Hand back
Complete unlocks only when every segment is translated and reviewed, and what it delivers is a translated .docx the manager can open.
Cartório Silva · certified translations
- Certidão de nascimento — Silva.docxIn progressopenPT-BR → EN due 12 Aug· 184/231 translated · 96 reviewedCompleteGo to
Complete: 47 segments still to translate
- Procuração — Meneses.docxTo dooverduePT-BR → EN due 28 JulStart working
- Escritura — Ribeiro.docxCompletedPT-BR → EN due 21 Jul· 412/412 translated · 412 reviewedReopen
Check a segment without writing it into your memory
Accepting a segment also records it in your translation memory. That is what you want for work you will reuse, and not what you want for a phrasing that suited this one document. So the two are separate: opening a segment and moving on marks it reviewed, accepting it also writes to your memory, and the progress bar shows both. You keep control of what your memory learns, and your manager still sees that the document was actually checked — where counting acceptances alone could show 21 of 231 on a document someone had read end to end.
Your colleague’s work, in your matches
Shared memories and term bases
Publish a translation memory or a term base and it is consulted on every teammate's machine, ranked beside their own. What one of you settles, the rest of you get — and no client document goes anywhere to make that work.
Yours stays yours
A memory you follow is read-only, so a sync can never overwrite something you typed. You decide whose memory is consulted first. And if you stop sharing, your copy and every entry in it stay with you.
A server-hosted memory makes you wait for every segment, and stops being there the moment your connection does. These sync to your machine and are matched locally, so a shared memory is exactly as fast as your own and works offline the same way.
- TMCertidões e procuraçõesPT-BR → EN · 4,182 entriesShared by youUnshare
- TMContratos — Marina R.PT-BR → EN · 9,540 entries · marina@Following · 1stUnsubscribe
- TBTerminologia societáriaPT-BR → EN · 612 terms · joão@Subscribe
Turn on encryption and we stop being able to read it
A shared memory holds your clients’ sentences, so sharing one normally means trusting whoever stores it. Every vendor prints “end-to-end encrypted” — here is what it means here, in four specifics you can hold us to. It is opt-in per team, and once a team turns it on it stays on.
- Each entry is sealed here, before it is sent
- The team key never leaves
j0Rk9vQ2… 4f1a·b77e- Stores it, holds no key
- Indexed under a keyed hash — nobody can test a guess against it
- Opens it on their machine
- Matches locally — no call per segment
Write this recovery code down now — it is shown only once.
It is the only way back into your team’s shared memories if every member loses their device. Neither Contextra nor we can recover it for you.
k7fq · 2m8d · rv04 · xz91CopyI’ve saved itThe key is made on your computer
It is generated by the app, never sent to us, and every entry is sealed before it goes anywhere. What reaches our storage is ciphertext.
New teammates are let in by teammates
A colleague who already holds the key passes it to a new computer automatically, the next time their app syncs. Until then that machine says so plainly rather than showing an empty memory that looks broken.
Nobody can test a guess against the index
Encrypted entries still have to be findable, and a plain hash would let anyone holding the database ask “does this team have an entry for this?” — which, for legal boilerplate, is most of the sentence. Contextra indexes under a keyed hash, so that question cannot be asked without the key.
One recovery code, and we mean one
Shown once, when you switch encryption on. It is the only way back if every member loses their device, and we cannot recover it for you — which is the same fact as not being able to read your memories, stated from the other side.