How to Set Up Workflows
A workflow is a multi-step pipeline that routes a document through stages like pre-translation review, translation, editing, proofreading, and final review. Each step has an assignee who receives a notification when it is their turn to work. Workflows keep your translation process organized, accountable, and moving forward.
Creating a Workflow#
Every new project already has a workflow: your team's default workflow, the team's first workflow if none is marked as the default, or the Solo Freelancer preset. To change its steps:
- Open your project and go to the Workflow tab.
- Click Edit steps. (If the project's workflow was removed, click Set Up Workflow, then Use Team Template or Build Custom.)
- Click + Add Step and choose from the 12 step types (the list shows the ones not already in the workflow). Workflows begin with Bible Verse Review, which lets every team paste and protect exact Bible wording. You can remove it, but while it is in the workflow it stays first.
- Drag steps into the order you want them executed. Bible Verse Review stays first. For an existing project, the new order applies to documents that have not reached the affected steps.
- Click an Editing or Proofreading step, choose Read only, Comments only, or Edit text directly under Text access, then click Done.
- Click Save Changes. Review how many documents will use the new order and how many will keep their existing order, then click Apply to remaining documents. New documents also use the new order.
Each step represents a distinct phase of work. You choose only the steps that match your process — there is no requirement to use all 12.
Changing the Order After Work Has Started#
You can move AI Editing before Editing even when some documents have moved further through the project. In Workflow → Edit steps, drag AI Editing into position and save. The preview shows which documents can change order.
Documents that have reached an affected human step keep their existing sequence, assignments, and progress. For example, a document already in Editing continues through its earlier workflow; a document still in Translation uses AI Editing before Editing. Check each document’s steps on the Documents tab to see its sequence.
An AI Editing step can be ready to start without having run. That ready state alone does not prevent a reorder. A queued or previous AI Editing run, a saved edit, or a comment counts as work, so affected documents keep their sequence. Human review is treated as started once its step becomes active, because reading and reviewing do not always produce saved edits.
Parts that follow different workflow orders must stay separate when merging parts or moving content between them. Documents with a saved individual order must stay in their current project; moving them to another project would replace that sequence.
Completed work is not reopened by a reorder. To deliberately repeat finished work, use Reopen on the affected document instead.
To add or remove a step and change the order, add new steps at the end and save the added or removed steps first, then reorder. Steps with active or completed work cannot be removed.
Using Presets#
When you create a team workflow (team page → Workflows → Create Workflow or + New Workflow), Lectio offers four built-in presets under Start from a preset:
Solo Freelancer
Bible Verse Review → Pre-Translation → Translation → AI Editing → Review
For individual translators working without a team. The AI reviews your translation and leaves comments, then you address them in a general Review step.
Small Team
Bible Verse Review → Pre-Translation → Translation → AI Editing → Editing → Apply Editor Feedback → Review
For teams of 3-4 people. Combines AI review with a human editor pass and a final review step.
Full Team / TEP
Bible Verse Review → Pre-Translation → Translation → Translation Review → AI Editing → Editing → Apply Editor Feedback → Proofreading → Proof Review → Review
The most thorough option, following the Translation-Editing-Proofreading model. Each production step has a paired review step. Best for high-accuracy projects like theological training materials, Bible study curricula, or doctrinal resources.
Track Changes Review
Bible Verse Review → Pre-Translation → Translation → Suggest Edits → Review Suggestions → Review
For teams that prefer a track-changes style review. The reviewer proposes edits as tracked changes, and the translator accepts or rejects each one.
Select a preset as your starting point, then add, remove, or reorder steps to match your process.
The team’s Default review-step text access setting determines the initial choice on newly added Editing and Proofreading steps. Each saved step keeps its own access, so changing the team default does not alter existing workflows.
Tip: Start with the Solo Freelancer or Small Team preset if you are unsure. You can always add steps later as your team identifies where quality gaps appear.
Assigning Team Members#
Each step in the workflow needs an assignee for each document:
- On the Documents tab, click a step in a document's row of steps, or the document's amber Assign button for its current step (for example, Assign Editing) when nobody holds that step.
- Pick the team member who will handle that step for that document. To set one person for a step on every document, use Manage Assignments on the Workflow tab.
- When one step is marked complete, the next assignee receives a notification that it is their turn.
This sequential handoff means no one has to wonder when to start — the system tells them.
Assignment lists put the likely people first. Under Usually does {Step} you will see anyone who is a default assignee for that step, followed by people who did that step recently, each with the reason ("Default for Editing", "Did Editing 3 days ago"). Everyone else on the team is listed below, so you can always pick anyone. Your own name appears at the top of its group as Assign me.
Who Usually Does What#
If the same people usually handle the same steps, set default assignees. They exist at two levels:
- Team workflow — on the team page under Workflows, open Who usually does what for a workflow. New projects that use that workflow start with these people.
- Project — in the project's Workflow tab, click Manage Assignments and use Add under Default Assignments. New documents in that project are assigned to them automatically, and you can also tick Also make them the default while assigning a single document.
Defaults are suggestions as much as automation: assignment lists show these people first, and anyone on the team can still be picked.
Note: Setting a project default also assigns that person right away on every existing document that has nobody on that step, as well as on new documents. On a step that takes one person, documents someone else already holds keep that person. For team defaults, Sync to projects adds missing default assignments to projects that use the workflow without changing existing ones.
Step Progression#
Steps advance sequentially. A step cannot start until the previous step is marked complete. This prevents anyone from working on a version that is still being revised upstream.
The current active step for each document is highlighted on the project page, so you can see at a glance where every document stands. Team members see only their own documents there, grouped as Your Tasks (their step is active now), Coming Up (waiting on an earlier step), and Completed. When someone holds more than one step of a document, it is listed under the step that matters now.
Reading a Document After a Handoff#
The workspace shows the step you opened, who is working on the document now, and your next assigned step. You can keep reading a completed step. If your next step is still waiting, the current assignee needs to finish first.
Comments only means you can select wording and leave feedback without changing the translation. Suggesting changes means your edits are proposals for the next reviewer to accept or reject. An AI check finishing does not complete its workflow step: the assignee still needs to review its findings and finish that step.
If the workflow changes while your workspace is open, editing access refreshes when you return to the tab or reconnect. A change that cannot save appears under Unsaved drafts, separately from the saved document.
- Read the workflow explanation to see why editing stopped.
- Choose Copy my text or Download draft text to keep a text copy, or choose Compare with saved text to check your draft against the latest saved paragraph.
- Once the original step is open for you again, compare the versions and choose Apply draft and save. If someone has changed the saved paragraph since your comparison, compare again before applying.
- Choose Discard draft… only when you no longer need that unsaved change.
A draft labelled kept in this browser is available to your account on the same browser until you apply or discard it. It does not sync automatically or transfer to another device. Clearing browser data can remove it. If browser storage is unavailable, copy the draft before leaving the tab. Formatting and tracked suggestions stay with the recoverable draft; Download draft text exports its wording only.
Resolve unsaved drafts before completing a step. Completing a review saves your pending work first, then explains who receives the document. If another person is still reviewing the same step, your part can be finished while the document waits for them.
Reopening Steps#
Reopening a finished step sends every later step back to the start, so project managers, admins, and the project owner decide when to do it. To reopen a step:
- On the project page, click the finished step in the document's workflow bar.
- Choose Reopen followed by the step name — for example, Reopen Translation.
- Read the confirmation. It lists the later steps that have already started or finished, and who holds them. The people working on those steps cannot continue until the reopened step is completed again. Steps that were already finished will need to be completed again afterward. Saved text and comments will be kept.
The person who did the step is notified that it is back with them, and the people on the next step are told it was reopened. Later steps wait until the reopened step is completed again.
Members who open a step they finished see it read only, with a note to ask a project manager or admin if it needs to change.
Workflow Templates#
If your organization runs similar projects regularly, team workflows are your templates. Create them on the team page under Workflows and give each a name — something like "Standard 4-Step Review" or "Full Theological Review." Tick Use as the team default for the one new projects should start with.
A project without a workflow can pick one with Set Up Workflow → Use Team Template → Apply Template.
Team workflows include the step types and their order, plus any default assignments. They are available to all projects within your team.
Next Steps#
- Review and Proofread to learn how to work through review steps
- Manage Your Team to add members before assigning them to workflow steps