Workflow Step Types

Reference6 min read

Lectio offers 12 workflow step types that you can arrange into a translation pipeline. Each step type controls what the assignee sees, what they can do, and whether the step supports multiple assignees.

Step Reference#

StepDescriptionSees SourceSees TranslationCan EditCan CommentCan Resolve CommentsParallel
Bible Verse ReviewFind Bible quotations, paste exact target-language wording, and protect it from AI rewritingYes--Paste protected textYes----
Pre-TranslationReview terminology, glossary matches, and TM entries before translation beginsYes----------
TranslationCore translation work. Write the translation and leave anchored context for downstream editorsYesYesYesYes----
Translation ReviewSelf-review your translation with source referenceYesYesYesYes----
ProofreadingRead the translation without seeing the source (blind review)--YesConfigurableConfigurable--Yes
Proof ReviewAddress proofreader comments and make correctionsYesYesYesYesYes--
EditingReview the translation alongside the source for quality and completenessYesYesConfigurableConfigurable--Yes
Apply Editor FeedbackAddress editor comments, make corrections, and resolve feedbackYesYesYesYesYes--
AI EditingAutomated AI pass that detects translation issues and leaves comments for reviewYesYesYesYesYes--
Suggest EditsPropose tracked changes to the translation. Edits appear as suggestions the next reviewer can accept or rejectYesYes--Yes----
Review SuggestionsAccept or reject tracked changes from a Suggest Edits stepYesYesYesYesYes--
ReviewGeneral-purpose review step. Edit, comment, and resolve -- all in one stepYesYesYesYesYes--

Text access: Every Editing and Proofreading step has its own setting: Read only, Comments only, or Edit text directly. The team setting controls the starting choice for new steps; changing it does not rewrite existing workflows.

Translator notes: In an active Translation assignment, comments are note-only and must be anchored to selected target text. They follow the document into Translation Review, Editing, Apply Editor Feedback, AI Editing, and Review. Proofreading, Proof Review, and suggestion steps keep their own comment chains separate.


Step Pairs#

Several step types are designed to work as pairs — a production step where a reviewer leaves feedback, followed by a review step where the translator addresses that feedback and resolves comments.

Production StepReview StepHow They Work Together
ProofreadingProof ReviewProofreader reads the translation without seeing the source and leaves comments, seeing only their own. Translator addresses those comments in Proof Review
EditingApply Editor FeedbackIn Comments only mode, the editor reviews against the source and leaves comments. The next assignee makes corrections and resolves them in Apply Editor Feedback
Suggest EditsReview SuggestionsReviewer proposes tracked changes to the translation. Translator accepts or rejects each suggestion in Review Suggestions
TranslationTranslation ReviewThese are not a handoff pair — both are done by the same translator. Translation Review is a self-review step where the translator revisits their own work before handing off; anchored translator notes remain visible

In each pair, the review step grants Can Resolve Comments permission so the translator can mark feedback as addressed. The production step does not have this permission because comment resolution belongs to the person doing the revision, not the person leaving feedback. Translation-origin notes are the exception: Editing can resolve them after the handoff even though it does not resolve other comment types, and every step that already resolves comments and can see them — Apply Editor Feedback, AI Editing, and Review — can close one too.

You do not have to use pairs. A Proofreading step works fine on its own — the translator can address comments informally. But adding the paired review step creates an explicit revision stage with its own assignment and tracking, which is especially valuable on larger teams.


Choosing Steps for Your Project#

The right workflow depends on your quality requirements and team size.

Blog post or short article (2 steps)

  1. Translation -- one translator does the work
  2. Proofreading -- a second person reads the result for fluency

Book chapter or training material (4 steps)

  1. Translation -- translator works through the document
  2. Translation Review -- translator self-reviews before handing off
  3. Proofreading -- a reviewer reads for natural language flow
  4. Proof Review -- translator addresses reviewer comments

High-stakes theological content (6-7 steps)

  1. Pre-Translation -- team reviews glossary terms and TM matches before work begins
  2. Translation -- translator produces the initial draft
  3. Translation Review -- translator self-reviews
  4. Editing -- a subject-matter expert reviews for accuracy against the source
  5. Apply Editor Feedback -- translator addresses editor comments
  6. Proofreading -- a native-speaker reviewer reads for fluency
  7. Proof Review -- translator addresses final comments

Using AI Editing

Insert an AI Editing step after translation to have the AI automatically flag potential issues. The AI leaves comments that you address in the next step. This works well between Translation Review and Proofreading to catch issues before a human reviewer sees the document.

Using Suggest Edits

Suggest Edits followed by Review Suggestions is useful when you want a reviewer to propose changes rather than directly editing. The translator sees each proposed change and decides whether to accept or reject it.

Tip: Start with a simple workflow and add steps as your team identifies where quality gaps appear. A workflow that is too long slows everyone down; one that is too short lets mistakes through.

Need more help?

Chat with our AI assistant or create a support ticket.