Lab workflows
Create and use SOPs
Standard Operating Procedures (SOPs) in xPlant document repeatable laboratory procedures and keep them connected to your culture work. They help teams follow consistent steps while preserving a record of how procedures were carried out over time.
Why SOPs matter in tissue culture
Consistent procedures
Documented SOPs give team members a shared procedure to reference during repeated laboratory work, helping reduce unnecessary variation between operators.
Reviewable execution history
Each SOP run records its status, start and completion times, notes, and any linked Plant, Explant, or run-code context. The SOP detail page keeps these runs together as a reviewable history.
Onboarding and training
SOPs give new team members a documented procedure to reference before carrying out laboratory work. Execution logs also help teams review how procedures were performed over time.
Traceability for troubleshooting
When contamination or unexpected culture outcomes occur, SOP history can provide useful context about which procedure was used and whether any deviations were recorded.
Creating an SOP
Create an SOP from the SOPs section, then document the procedure with a clear title, status, description, and ordered steps. Add the additional controls that matter to your laboratory workflow.
| Field | What to enter |
|---|---|
| Title | A short, specific title, such as “MS Multiplication Subculture” |
| Status | The current publication or workflow status of the SOP |
| Description | What the procedure covers and when it is intended to be used |
| Category | The laboratory workflow category the SOP belongs to |
| Document Type | SOP, Protocol, Guide, Procedure, Checklist, Note, or the appropriate document type |
| Media Recipe | Optional Media Recipe associated with the procedure |
| Equipment | Equipment used by the procedure |
| Estimated Time | Approximate procedure duration |
| Steps | Ordered instructions with optional timing, notes, safety warnings, and supporting images |
| Notes | Additional laboratory or procedure context |
| Tags | Tags for organizing and finding the SOP |
| Reviewer / Review Due | Optional reviewer and next review date |
Keep SOP titles short and specific so they are easy to recognize when linking procedures to Plant or Explant records and when starting an SOP run.
Logging an SOP execution
SOP runs can be recorded from the SOP itself or from a Plant or Explant where the SOP is available. Each run stores its execution context separately from Transfer history.
| Run field | What to enter |
|---|---|
| SOP | The SOP being performed |
| Plant / Explant | The relevant culture record when the run is associated with one |
| Run Code | Optional identifier for the SOP run |
| Status | Pending, In Progress, On Hold, Completed, Failed, Cancelled, or Archived |
| Started At | Date and time the SOP run started |
| Completed At | Optional date and time the SOP run completed |
| Notes | Procedure observations, deviations, or follow-up context |
| Explant Notes | Optional Explant-specific notes when an Explant is selected |
Reviewing SOP history
Open an SOP to review its run history, including recorded statuses, start and completion times, users, run codes, and notes. This history provides procedure context when reviewing repeated laboratory work.
When an SOP run is linked to a Plant or Explant, that execution context stays connected to the corresponding culture record for later review.