Skip to content

The SOP Review Workflow

Tailwind CSS chat bubble component

How should an SOP change move from idea to official procedure?

Instead of editing the main branch directly, follow a structured workflow.

Proposed Workflow

  1. Create a branch for the modification:

    Terminal window
    git checkout -b improve-dna-lysis-step
  2. Edit the SOP in Markdown.

  3. Commit changes with explanation:

    Terminal window
    git commit -m "Increase lysis time to improve yield"
  4. Push the branch to the remote repository:

    Terminal window
    git push
  5. Open a pull request for review.

The main branch represents validated procedures.

Direct modification can:

  • Introduce un-reviewed errors
  • Reduce trust in official protocols
  • Create confusion about approval status

Branching separates experimentation from validation.