In many bid teams, the same few people pass answers between them. One person drafts, a colleague picks it up and reworks it, and someone else gives it a final read. In BidScript, how you set that up depends on one question: is the next person editing the answer, or reviewing it?

Getting this right means nobody is blocked from making the changes they need to make, and the question table always shows who is responsible for what.

Editors and reviewers work differently

Assignee (editor)	Writes and edits the answer freely while it is In Progress. Assignees can also change the question's status.
Reviewer	Works on the answer once it has been submitted for review. While a question is In Review, a reviewer's changes are made as tracked changes: suggestions the author accepts or rejects. Reviewers cannot freely rewrite the answer.

So if the next person needs to rework the answer, rather than suggest changes to it, they are not really a reviewer. They are a second-round editor, and should be set up as an assignee.

Hand over to a second-round editor

When one person has drafted an answer and a colleague is taking it on to rework it:

Add the colleague as an assignee on the question, alongside or instead of the original author. Do this in the question's row in the question table, or click the ⋯ menu on the question and choose Configure.
Keep the question In Progress. Do not submit it for review just to hand it over. In review, the colleague could only suggest changes.
Let the colleague mark it Completed when they are done, or submit it for review if someone still needs to check it. Only assignees can change a question's status, which is another reason to add them as one.

To hand over several questions at once, select them, click Bulk Edit, change the assignees, and save. See Managing the question table.

Use review for genuine review

Submit an answer for review when someone needs to check it and propose changes for the author to accept or reject, such as a director signing off a scored question, or a subject matter expert checking technical accuracy.

Add that person as a reviewer on the question.
When the answer is ready, the author submits it for review.
The reviewer makes their changes as tracked changes.
The author accepts or rejects each suggestion, and the question is marked Completed.

Use statuses as signals

Statuses are how the whole team can see where each answer stands. They only work if everyone uses them the same way.

Not Started	Nobody has begun work on the answer yet.
In Progress	The answer is being written or reworked by its assignees, including any second-round editors.
In Review	The assignees have finished. A reviewer is suggesting changes.
Completed	The answer is finished.

Two habits to avoid:

Leaving everything In Progress. It hides which answers are ready, and nobody can tell from the question table what is left to do.
Using Submit for Review to mean "I'm done". If an answer needs no further review, mark it Completed. If someone else needs to rework it, add them as an assignee instead.

When to move to workflows

Assigning people question by question works well for small teams. Consider workflows when:

Different groups of questions need different reviewers, such as quality questions going to one team and requirements matrices to another.
You are assigning the same reviewers question by question on every bid, and it is becoming repetitive.
You need to enforce that an answer cannot be completed until it has been approved.

See Configuring Workflows and Workflow Groups.

Best practice

Decide whether the next person is editing or reviewing before you hand an answer over.
Make second-round editors assignees, not reviewers.
Keep reviewers for genuine checks, where suggestions are the right tool.
Move statuses as the work moves, so the question table always tells the truth.
Resolve every suggestion before an answer is marked Completed.

Managing the question table - assigning people and updating statuses.
Roles and collaboration in the Answer Workspace - what assignees and reviewers can do.
Configuring Workflows - review gateways and approvals.
Workflow Groups - assigning a review stage to a set of people.
Version control - snapshots and reverting an answer.

Editing and reviewing answers: best practice