Review & deliver
Team review, on the sentence
Inline threads on any sentence. Real-time presence so two reviewers don’t step on each other. An activity feed of who changed what. Translation review the way code review works — in the artifact, not in an email.
Free to begin · No card required
Featured on
Translation review still happens mostly by email. Translator finishes a draft, exports DOCX, emails it to the editor with "v3_final_FOR_REVIEW" in the name. Editor marks it up in Word, sends it back. Translator copies the edits into the master file, fixes the formatting that broke. Half a day disappears into version control. Team review in Transept moves the whole conversation into the document itself — threaded comments on any sentence, real-time presence so two editors can work in parallel, role-based permissions, an activity feed of every change. Same model as code review: comments on the artifact, resolved as the work lands, no email chain.
How do you review in the document, not in your inbox?
Most translation reviews still happen by emailing DOCX files with "v7_FINAL_final" in the name. Team review brings the conversation into the document and out of the inbox.
Invite teammates
Add team members by email; pick their role (editor or commenter). Shared resources — glossaries, styleguides — automatically apply.
Comment on any sentence
Threaded comments tied to the sentence, not the page. Mention teammates with @, resolve when the discussion lands.
Real-time co-editing
Two editors can work on different sentences in the same document at the same time. Locks happen at the sentence level so no one steps on anyone.
Activity feed and notifications
See what changed, who changed it, when. Get notified on @-mentions and resolutions. Audit any document’s history.
When are two pairs of eyes the standard?
Agencies
Translator drafts, editor reviews, project manager signs off. All in one workspace, all on the same artifact.
In-house teams
Native-speaker reviewers commenting on a centralized localization workflow without an extra tool.
Long-form collaboration
Co-translating a book or a long report with another person — sentence-level handoffs, no merge conflicts.
~1,000 calls measured
We logged the reasoning on roughly a thousand real translation calls. On plain text the pricier Pro model thinks about half as much as Flash. The harder the sentence, the more any model reasons, whatever its tier. So we spend Pro only where it earns its cost: the passages a cheaper model would fumble.
What we measured— Don’t take our word for it —
The editor, in miniature
A working slice of the real thing — Literess, glossary, styleguide, workflows, and the translation memory are all live. Click around.
Here to help you translate
A key turned in the lock and the door swung open.
У замку повернувся ключ, і двері розчахнулися.
The knock came just before midnight.
Стукіт пролунав перед самою північчю.
FAQ
- There’s no member cap. Creating a team and inviting people is free on every plan — Free users can create one team, paid plans create as many as they need. Buying seats is optional: seats only fund a shared word pool, so that team work bills from the pool instead of each member’s own balance.
- Yes — share a document, glossary, or styleguide with specific people or with the whole team, at one of four access levels: View, Comment, Edit, or Admin. Or keep it private.
- Resolved threads collapse but stay in the history. Open threads stay visible until resolved. Exporting a document doesn’t carry comments with it.
- Yes — see client review links for a per-document share that doesn’t require an account.
- No hard cap on simultaneous editors. Locking happens at the sentence level so two editors working on different sentences don’t step on each other. For larger teams, role-based permissions (editor / commenter / viewer) keep changes scoped.
- Yes — `@` mention any team member. They get a notification in-app and (optionally) an email. Mentions thread under the originating comment so the conversation stays tied to the sentence.
- Every edit, regeneration, comment, and resolution writes an activity entry. Audit any document’s history; revert any change. The feed is filterable by user, action type, and date.
- Yes — invite teammates as Editors (full editing rights), Commenters (can leave comments but not edit), or Viewers (read-only). Role-based permissions come with team membership, which is free on any plan; client reviewers can also comment via a review link without joining the team at all.
- See Client review links — share a per-document signed link that opens in any browser, no account needed. Their comments come back into your team workspace.
Keep reading around this capability
- FeatureA glossary the AI actually follows→Character names, product terms, branded phrases, client-specific vocabulary. Build a glossary once — manually, by upload, or seeded from a…
- FeatureA styleguide that steers every regeneration→Tone, register, rules, formatting conventions. Build a styleguide manually or have Transept generate one from a sample page of finished…
- Use caseTranslate the next client document→Per-client glossaries that travel across projects. Per-client styleguides that hold tone. Sentence-level review for the lines that matter.…
- Use caseLocalize the launch kit, all of it→Email, landing page, FAQ, release notes, social posts — the assets that make a launch. Run them through Transept as one bundle with a…