Botanical Gardens & Arboretums ยท Living collections, accessions, and plant records

AI Plant Accession Records Management for Botanical Gardens

An AI-driven use case for managing plant accessions, provenance, and records across design through safety, enhancing accuracy and traceability in living collections.

By Suhas BhairavUpdated 4 min read

AssetLiving collections, accessions, and plant records
AssetTrees, arboretum collections, and veteran trees
AssetGlasshouses, conservatories, nurseries, and propagation
AssetSoils, irrigation, water features, and composting
AssetPlant health, pests, diseases, and biosecurity
AssetSeed banks, herbarium, and conservation science
AssetGrounds, paths, buildings, machinery, and visitor safety
BusinessVisitors, education, events, and retail
BusinessHorticultural operations, workforce, and standards
BusinessFunding, membership, governance, and capital projects
1Accession Office Barcode Scanner Station2Provenance Type Archive Cabinet3Wild Origin Data Digital Cabinet4Collector Numbers Filing Cabinet5Verification Desk and Plant Verification Bench6Plant Records Server Rack

The short answer

Plant accession records management for botanical gardens uses AI to monitor accession integrity, verify provenance data, flag inconsistencies, and trigger human review. It watches barcode scans, specimen notes, and validation checks, and decisions are documented in plant records staff review.

Who it's for: Curators, horticulturists, plant records officers, and garden governance staff.

Why it matters

Without AI, mislabeling, provenance gaps, and inconsistent verification can accumulate, risking lost accessions, misassigned records, and delayed responses to plant health or biosecurity concerns.

From design to safety

  1. Design

    AI informs data model design

    AI reads proposed data model inputs: accession numbers, provenance type, wild origin data, collector numbers, verification, and plant records to validate the structure and constraints. It also maps required metadata fields to archival standards and crosswalks legacy schemes to new controlled vocabularies.

    • Accession Office Barcode Scanner Station
    • Provenance Type Archive Cabinet
    • Wild Origin Data Digital Cabinet
  2. Build

    AI supports build and labeling

    AI maps legacy records to the new schema, assigns unique accession numbers, and configures validation rules for provenance and collector numbers during labeling. It ensures label printing templates include barcodes, text blocks, and color-coding consistent with the garden's accession policy.

    • Accession Office Barcode Scanner Station
    • Collector Numbers Filing Cabinet
  3. Operation

    AI sustains daily record integrity

    AI ingests barcode scans, verifies against master lists, checks provenance type, updates plant records, and surfaces flags for verification where data diverges. It automates reconciliation tasks when minor mismatches occur and preserves audit trails for each action.

    • Verification Desk and Plant Verification Bench
    • Plant Records Server Rack
  4. Maintenance

    AI audits records and audits checks

    AI runs periodic audits of accession counts, provenance status, and wild origin entries, flags anomalies, and triggers human reconciliation workflows. It schedules quarterly data quality reviews with the records office and curatorial leads.

    • Collector Numbers Filing Cabinet
    • Plant Records Server Rack
  5. Safety

    AI enforces biosecurity and safety data

    AI monitors access to sensitive records, flags suspicious provenance or mislabeling patterns, and prompts assurance checks by the plant health officer and curator of living collections. It also logs changes for regulatory reporting and sanctions access when required.

    • Provenance Type Archive Cabinet
    • Verification Desk and Plant Verification Bench

Part by part

  1. 1

    Accession Office Barcode Scanner Station

    Watch for
    misread barcodes, mismatched accession IDs, or missing scans in daily logs
    AI action
    read barcode, compare to master, flag mismatch, prompt manual reconciliation
  2. 2

    Provenance Type Archive Cabinet

    Watch for
    inconsistent provenance type labels, missing origin notes
    AI action
    validate provenance field, enforce controlled vocabulary, trigger review workflow
  3. 3

    Wild Origin Data Digital Cabinet

    Watch for
    wild origin data gaps, incomplete collector notes
    AI action
    verify against Index Seminum, flag gaps for curator input
  4. 4

    Collector Numbers Filing Cabinet

    Watch for
    duplicate collector numbers, mismatched collector data
    AI action
    cross-check with collector logs, merge duplicates, alert records officer
  5. 5

    Verification Desk and Plant Verification Bench

    Watch for
    unverified records, mismatched plant IDs
    AI action
    generate verification task, assign to verifier, update verification flag
  6. 6

    Plant Records Server Rack

    Watch for
    unauthorized access, immutable log breach
    AI action
    log access, enforce permissions, alert governance officers

Worked example

Catching a mislabelled accession before integration

Illustrative scenario with sample data.

New accession batch arrives; records must be verified against master list, provenance documented, and labels applied correctly before planting.

Signal in

batch_id: A2026-014, accession_numbers: [A2026-014-001...A2026-014-012], provenance_type: collected, wild_origin: true, origin_notes: "Pamplona, 2018", collector_numbers: [CN-2018-07-01, CN-2018-07-02], verification_status: unverified, plant_records_id: null

System out

validation_result: pass; unknown_provenance: false; accession_ids_linked: 12; plant_records_id: PR-2026-014; next_step: apply labels and plant in designated bed T-Alpha, update Index Seminum.

Human sign-off: Head of Living Collections approves the new accession batch after all records are linked and verified.

How to roll it out

  1. Phase 1

    Weeks 1 to 4

    Baseline data model adoption, import legacy records, define validation rules, establish access controls.

  2. Phase 2

    Weeks 5 to 8

    Pilot in one living-collections zone, validate barcode workflows, verify provenance fields, train staff in verification routines.

  3. Phase 3

    Weeks 9 to 12

    Full deployment across sections, automated audits, continuous improvement through feedback and quarterly governance reviews.

Where people stay in charge

  • Decisions on record deletions or major provenance changes must be signed off by the Head of Living Collections.
  • All access to plant records must be auditable by the Garden Director and Plant Health Officer.
  • Biocontainment and access restrictions must be enforced by the Records Manager and IT Security Lead.

Questions owners and crews ask

How does AI improve accuracy of accession numbers and plant records?

AI validates barcode data against master lists, enforces unique accession IDs, and cross-checks collector numbers with provenance notes, reducing entry errors and improving traceability.

Who verifies provenance data and wild origin notes?

The curator of living collections signs off on provenance classifications, wild-origin entries, and collector data during periodic verification cycles.

What happens if a mismatch is detected?

A verification alert is raised, a reconciliation task is assigned to the records officer, and affected records are locked until review is complete.

How does the system handle access control and safety?

Access to plant records is role-based, with logs and approvals reviewed by the garden director and IT security lead to protect sensitive data.

Sources and further reading

  1. BGCI: Guide to Accessioning Living CollectionsAccessioning guide covers provenance records, verification practice, and accession number standards for living collections.
  2. CBD: Access and Benefit-SharingNagoya Protocol explains obligations, permits, and documented origins for genetic resources collected from wild populations.

Work with Suhas Bhairav

Let's find where AI pays back on your gardens.

Botanical gardens, arboretums, and seed banks bring me the problem that keeps costing them lost accessions, failed trees, or glasshouse losses. We map it to one system you can ship.

  • A 30-minute working call, not a pitch
  • You leave knowing the first system worth building
  • Built around the systems, records, and people you already have