Transept

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.

Start translating→

Free to begin · No card required

In context✦

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.

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.

  1. Invite teammates

    Add team members by email; pick their role (editor or commenter). Shared resources — glossaries, styleguides — automatically apply.

  2. Comment on any sentence

    Threaded comments tied to the sentence, not the page. Mention teammates with @, resolve when the discussion lands.

  3. 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.

  4. Activity feed and notifications

    See what changed, who changed it, when. Get notified on @-mentions and resolutions. Audit any document’s history.

Transept editor with inline comment threads on translated sentences

When two pairs of eyes is 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.

Footnotes✦

Questions, answered without the fluff

  • Free and Starter plans support up to 3 members; Pro covers larger teams; custom team plans available for agencies.
  • Yes — share a document with specific people; or with the whole team; or keep it private. Role-based permissions (editor/commenter/viewer) coming soon.
  • 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 are part of the Pro and Team plans.
  • 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.
Related✦

Keep reading around this capability

❧

Stop emailing DOCX files with v7_FINAL_final

Start translating→

Free to begin · No card required