Team Plasmid Map Review: An Implementation Checklist

Implementation checklist for team plasmid-map review is a meeting with a freeze-or-reject gate, not a prettier canvas. Do not freeze a map until a named reviewer who is not the designer states a conflict or an explicit no-conflict on a version ID. Emailing a screenshot is not that meeting. Shared-review software selection is a different page. Collaborative workspace language is also a different page.

Do Not Freeze a Map Until the Reviewer Named the Conflict

The outcome is a frozen or rejected version ID plus a stored sentence. Prerequisites are a candidate file with a version ID, a designer, a second person assigned as reviewer, and a one-sentence job for the construct — what host, what insert, what the map is supposed to do next week. If any of those are missing, cancel the meeting. You do not have a review. You have a hallway conversation.

A design-handoff checklist already insists on a version match before wet work. Use that bar inside the team meeting. The reviewer compares the file on the table to the current approved record, not to a memory of last Thursday's email. Cross-site collaboration guidance adds the packet: purpose, fixed version, critical junctions, open questions, requested decision, and a deadline. A local team still needs that packet. Time zone is not the reason. Missing context is the reason.

Run the Review: Roles, Version, Conflict, Decision

Execute the meeting in this order. Do not skip to freeze because the map looks familiar.

1. Assign roles in writing. Name the designer, the reviewer, and the owner who is allowed to freeze or reject. The designer may present. The designer may not be the only person who names the conflict.
2. Freeze the candidate identity, not the science. Record the filename or object ID, the timestamp, and the hash or export you will actually open. If two people have different files, stop. You do not yet have a version.
3. State the job in one sentence. Host, insert, and the next wet step. If the reviewer cannot repeat that sentence, the packet is incomplete.
4. Reviewer names the conflict — or names "no conflict found" as an explicit sentence. A useful conflict points at a junction, a frame, a marker, an origin, a missing feature, or a stale parent ID. "Looks fine" is not a named result.
5. Designer responds on that sentence. Accept, fix on a new ID, or withdraw the candidate. Do not edit the frozen candidate in place and keep the old ID.
6. Owner decides freeze or reject on that exact ID. Frozen means oligos or fragments may be ordered from this ID. Rejected means this ID is not an order file. Record the decision beside the conflict sentence.

A cloning workflow that treats in-silico assembly as a gate says the same thing without a meeting: catch a short homology arm or an internal site before anyone synthesizes an oligo. The team review exists to force that gate to have a second pair of eyes. If the lab's usual chemistry is restriction or Gibson, simulate that job on the frozen ID. Official Zetta simulation coverage is restriction, Gibson, and homologous alignment. Golden Gate is not a Zetta feature. Do not write it into the meeting as one.

Expected Result and Verification

Expected result: one version ID is marked frozen or rejected; one conflict-or-no-conflict sentence is stored where the next person can find it; no oligo, fragment, or gene-synthesis order cites a rejected ID; the designer and the reviewer are two different names.

Verification: open the record tomorrow without asking either person. You should be able to read the ID, the sentence, and the decision. If the only evidence is a chat scroll, the review failed even if everyone felt aligned. If a freeze exists and the conflict field is empty, unfreeze it. A freeze without a named conflict is the failure mode this checklist exists to stop.

Common failures: the designer "reviewed" their own map; two people opened different exports; someone ordered oligos during the meeting from a draft filename; a reject was spoken and never written; the owner froze v3 while the reviewer had read v2. Rollback is simple. Withdraw the freeze. Restore the previous frozen ID or return to draft. Do not patch a frozen ID.

This Is Not the Software Page

Choosing comment threads, locks, and identity for map software is the Wave6 selection page. Planning the construct before order is the planning checklist. Sequence-level base-by-base review is a later sibling, not this meeting. After roles are assigned, ZettaGene can be the shared map the team opens. It is the surface, not the reviewer. If the team still cannot name a conflict on a version ID, changing the canvas will not create a review. Assign the second person first.

Frequently Asked Questions

Can the designer also be the only reviewer on a team plasmid-map review?

No. A team review needs a second named person. The designer can present; they cannot be the only conflict-namer.

What output must exist before anyone orders oligos?

A frozen version ID plus a stored conflict-or-no-conflict sentence. A rejected ID is not an order file.