Protocols, not scattered spreadsheets

Turn breeding plans into workflows the team follows

Stages, timing, and required traits are defined once, so every evaluation run matches your SOP, data stays structured, and you can show what happened when it matters.

What is a crop protocol?

Think of a crop protocol as a shared playbook for one breeding path: the stages you always run (from germination or clone through evaluation, lab work, or compliance checks), what must be recorded at each step, and when a stage is done. Templates are versioned so everyone follows the same rules; when you attach a protocol to a program or trial, the app guides the team stage by stage instead of leaving steps in email or notebooks.

How it flows in practice

  1. 1

    Start from a template

    Choose a template for your crop (cannabis, hops, tomato, strawberry, and more) or define your own. Tune stages, timing, and required traits to your program.

  2. 2

    Attach it where work happens

    Attach the protocol to a program or trial so pheno hunts, evaluations, and selections follow one roadmap.

  3. 3

    Record as you go

    Technicians and breeders log traits and observations against the active stage. Required fields and completion rules mean nothing important slips through.

  4. 4

    Advance with confidence

    When stage rules are met (every required trait, enough observations, or a manual sign-off), you move forward with a clear record.

Why teams use it

  • Same process for every run: less drift between sites or seasons.
  • Compliance and quality gates land on the right stage, not as an afterthought.
  • Audit log ties every change to who and when, alongside programs, trials, inventory, and the rest of your data.