Understanding Workflows

Explanation8 min read

Translation is rarely a one-step process. A translated document typically goes through multiple rounds of review before it is ready for publication -- especially when the content carries theological, educational, or organizational weight. Workflows in Lectio formalize this multi-step process, giving your team a clear path from first draft to final product.

Why Workflows Exist#

Without a workflow, translation coordination happens through email, chat messages, and shared spreadsheets. Someone translates a document, emails it to a reviewer, waits for feedback, makes changes, sends it to another reviewer, and so on. Things get lost. Steps get skipped. Nobody is sure whose turn it is.

A workflow solves this by defining the steps in advance and tracking progress automatically. Each step has an assignee, a clear scope (what they see and what they can do), and a defined handoff to the next step. When you complete your step, the next person is notified and the document appears on their dashboard. No email required.

How Workflows Progress#

Linear Execution

Workflow steps execute in order. Step 2 cannot begin until Step 1 is complete. This ensures that each reviewer sees the most current version of the translation, not an earlier draft that has already been superseded.

When the assignee for Step 1 clicks "Complete Step," the workflow advances:

  1. Step 1 is marked complete
  2. Step 2 is activated
  3. The Step 2 assignee receives a notification
  4. The document appears on the Step 2 assignee's dashboard

Parallel Steps

Some step types -- Proofreading and Editing -- support parallel assignees. This means you can assign multiple people to the same step, and they all work at the same time. Each reviewer leaves their own comments independently.

Parallel steps are useful when you want feedback from several perspectives. For example, you might assign a theological reviewer and a language specialist to the same Editing step. Both review the document, and the translator addresses all comments in the subsequent review step.

Assignments

Each step in a workflow, for each document, has one or more assignees. When a step activates, the assignees see the document on their dashboard with a status indicator showing it is their turn to act.

Project managers assign team members to steps when setting up the workflow. Default assignees can be configured on workflow templates so they carry over automatically to new projects.

Assignment is separate from access. A person's access level (Admin, Project manager, Member) decides what they can see and manage; the steps they are assigned decide what work they do. Lectio learns who usually does what from those defaults and from recent assignments, and lists the likely people first when you assign a step — without ever limiting who can be chosen.

Completing a Step#

When you finish your work on a step, click "Complete Step" in the workspace. This signals that you are done and triggers the handoff:

  • Your step is marked complete
  • The next step activates
  • The next assignee is notified

Note: You do not need to confirm every segment before completing a step. The "Complete Step" action is based on your judgment that the work is done for your role. In a Proofreading step, for example, you complete the step after reviewing the translation and leaving your comments -- even if you did not interact with every segment.

Upstream Revisions#

Sometimes a later reviewer finds an issue serious enough that an earlier step needs to be reopened. Lectio supports this:

  1. A project manager or admin reopens a completed step
  2. The original assignee is notified that changes are needed
  3. The reopened step becomes active again
  4. Once the assignee addresses the issues and completes the step again, the workflow resumes from where it left off

This is intentionally a manual action. Casual comments should be resolved in the normal flow; reopening a step is for situations where the work needs significant revision.

Notes from the Translator#

During an active Translation step, a translator can select exact target wording and choose Comment beside Alternatives. The composer asks only for context—not a replacement—and the note remains anchored to that phrase. This is useful for an uncertain term, a deliberate tradeoff, or context an editor should know without interrupting the translation pass.

Translator notes appear in source-aware handoff steps: Translation Review, Editing, Apply Editor Feedback, AI Editing, and Review. Teammates can reply in those steps. Editing, Apply Editor Feedback, AI Editing, and Review assignees can also resolve the note once it has been addressed, so a workflow without an Editing step still has somewhere to close it. Translator notes stay out of the source-blind proofreading chain and the suggestion chain; every other kind of comment keeps the visibility it has always had. Lectio does not send a notification for each note — the normal workflow handoff and existing comment counts bring them forward.

Once a workflow finishes, the document's comment history stays readable to everyone who can open the document.

Workflow Templates#

Teams can save commonly used workflow configurations as templates. A template defines the step types and their order -- for example, "Standard 4-Step" might include Translation, Translation Review, Proofreading, and Proof Review.

When you create a new project, you can apply a template to set up the workflow instantly. Templates can also include default assignees, so the same people are automatically assigned to their usual steps.

Templates save time when your team runs similar projects repeatedly. Define your workflow once, reuse it across every project.

The Dashboard#

All your active assignments appear on your dashboard with:

  • The document name and project
  • The workflow step you are assigned to
  • A status indicator (waiting, active, or completed)
  • A progress bar showing how many segments are translated or confirmed

When a step activates and it is your turn, the document moves to the top of your dashboard with a clear visual indicator. You can click directly into the workspace from there.

Step Pairs#

Many workflow step types are designed as pairs — a production step followed by a corresponding review step:

  • Proofreading → Proof Review — A proofreader reads the translation without seeing the source text (a "blind review") and leaves comments about fluency, clarity, and naturalness. The blind review extends to comments: a proofreader sees only the comments they wrote themselves, not earlier steps' discussion of the source, and not a second proofreader's independent read when the step has parallel assignees. The translator then opens the Proof Review step, sees all those comments, makes corrections, and resolves each comment as it is addressed.

  • Editing → Apply Editor Feedback — In Comments only mode, an editor reviews the translation alongside the source and leaves comments on accuracy, completeness, and quality. The next assignee works through those comments, changes the text, and resolves the feedback in Apply Editor Feedback. If Editing uses Edit text directly, the editor can make those changes in the Editing step instead.

  • Suggest Edits → Review Suggestions — Instead of comments, the reviewer proposes tracked changes directly in the translation text. The translator sees each proposed change highlighted and decides whether to accept or reject it — similar to track changes in Word.

The key difference between a standalone step and a paired step is accountability. When someone leaves a comment in Proofreading, how do you know the translator saw it and addressed it? The Proof Review step answers that question. The translator cannot complete Proof Review without seeing every comment, and the step's completion is tracked separately. On a large team with multiple projects, this visibility matters.

Translation Review is a special case. It is not a handoff to someone else — it is a self-review step where the translator revisits their own work before the document moves on to another team member. Think of it as a built-in pause for the translator to catch their own mistakes with fresh eyes.

You do not have to use pairs. A Proofreading step works fine without a Proof Review step — the translator can read the comments and address them informally. But pairs create a formal revision stage, which is especially valuable for high-stakes content.

Designing Your Workflow#

The right workflow depends on what you are translating and how much review it needs.

Simple projects (blog posts, short articles) might only need two steps: Translation and Proofreading. The translator does the work, a reviewer reads it for fluency, and you are done.

Standard projects (book chapters, training materials) benefit from four steps: Translation, Translation Review (self-review), Proofreading, and Proof Review. This gives the translator a chance to self-review before anyone else sees the work.

High-stakes projects (theological textbooks, doctrinal materials) might use six or seven steps, adding Pre-Translation review, Editing with source comparison, and multiple review rounds.

Tip: Start simple. A two-step workflow is better than no workflow. As your team identifies where quality gaps appear -- maybe proofreaders keep finding the same kinds of issues -- you can add steps to address them. You can always adjust the workflow for future projects based on what you learn.

For a detailed list of all available step types and their permissions, see Workflow Step Types.

Need more help?

Chat with our AI assistant or create a support ticket.