CHAPTER
[01]

Putting It All Together

You've learned about locations, animals, observations, biosecurity, traceability, tasks, and team coordination. Each chapter (1-27) explains individual features. This chapter shows how those features work together in real operational scenarios.

The Difference:

  • Chapters 1-27: "Here's how health observations work"
  • Chapter 28: "Here's your complete morning routine: location checks, animal observations, task creation, treatment administration, follow-up scheduling"

Think of Chapter 28 as watching experienced operators work through complete scenarios. You'll see how Kora's features orchestrate together to support real operations.

What This Chapter Covers

This chapter presents scenario-based workflows showing how features integrate, what happens automatically, when decisions are required, and how teams coordinate.

Five Major Workflow Categories

28.1 Daily Farm Operations - Routine workflows that repeat daily or weekly: morning health check routines, treatment administration workflows, regular monitoring and task completion

28.2 Biosecurity Event Response - Critical workflows for disease management: suspected disease workflows (observation, diagnosis, response), quarantine initiation and monitoring, contact tracing and exposure assessment, outbreak coordination across multiple locations

28.3 Regulatory Compliance - Documentation workflows for legal requirements: pre-export preparation and verification, health certificate generation and validation, movement documentation and traceability verification

28.4 Conservation Operations - Wildlife and breeding workflows: wildlife sighting documentation and verification, population census operations, breeding programme coordination

28.5 Veterinary Consultation - Professional veterinary workflows: pre-visit preparation and history compilation, clinical examination documentation, treatment plan creation and implementation, follow-up scheduling and monitoring

How These Workflows Work

Integration, Not Repetition

These workflows reference features documented in Chapters 1-27. We won't re-explain how to record observations (see Chapter 7.1) or create tasks (see Chapter 13). Instead, we show when you record observations, why tasks are created automatically, and how different features connect.

Example: Disease Suspected Workflow doesn't re-teach you how contact tracing works (that's Chapter 11.3). Instead, it shows:

  1. Veterinarian records clinical observation with diagnosis
  2. Contact tracing automatically identifies exposed animals
  3. System recommends quarantine for high-risk contacts
  4. Health check tasks auto-generate based on disease profile
  5. Notifications sent to affected location managers
  6. Traceability events recorded for all actions

The workflow shows orchestration. Recording one observation triggers a coordinated response across biosecurity, quarantine, tasks, notifications, and traceability.

Decision Points and Branching

Real operations involve decisions. These workflows show:

When to choose option A vs. option B:

  • If severity is high, escalate to veterinarian immediately. If moderate, schedule follow-up.
  • If animal is pregnant, apply extended withdrawal period. If not, use standard withdrawal.
  • If species is endangered, CITES compliance required. If not, standard movement documentation.

What triggers automatic actions:

  • Veterinarian diagnosis triggers automatic contact tracing
  • Quarantine initiated triggers health check tasks auto-scheduled
  • Treatment recorded triggers withdrawal period calculated
  • Movement logged triggers traceability event created

What requires manual action:

  • Reviewing contact tracing results and deciding quarantine scope
  • Approving health certificates before export
  • Assigning follow-up tasks to team members
  • Confirming release from quarantine

Cross-Context Examples

Kora serves diverse contexts: farms, zoos, wildlife reserves, conservation programmes, veterinary practices, research facilities. These workflows show how the same scenario plays out differently across contexts.

Example: Morning Health Check Workflow

  • Dairy Farm: 100 cows, mob-level observations, specific milking-related checks, task assignment to farm hands
  • Zoo: 200 animals across 50 species, individual observations, enrichment notes, keeper coordination
  • Wildlife Reserve: 500 animals across territories, sighting-based observations, ranger field coordination
  • Veterinary Practice: 12 properties, multi-species clinical checks, cross-location coordination

Same workflow (morning health checks) but different implementation details based on operational context.

How to Use This Chapter

Start with Relevant Scenarios

Find workflows matching your daily operations:

  • Farm operators: Start with 28.1 (Daily Farm Operations), then 28.2 (Biosecurity Event Response)
  • Wildlife managers: Start with 28.4 (Conservation Operations), then 28.2 (Biosecurity Event Response)
  • Veterinarians: Start with 28.5 (Veterinary Consultation), then 28.2 (Biosecurity Event Response)
  • Zoo staff: Start with 28.1 (Daily Operations), then 28.4 (Conservation for breeding programmes)

Not every workflow applies to every organisation. Focus on workflows matching your responsibilities.

Follow Cross-References

These workflows reference specific chapters for detailed feature explanations:

  • "Record observation (see Chapter 7.1)" means full instructions in Chapter 7.1
  • "Initiate quarantine (see Chapter 11.2)" means complete quarantine documentation in Chapter 11.2
  • "Create recurring task (see Chapter 13.3)" means recurring task details in Chapter 13.3

Cross-references connect workflows to feature documentation. Follow them when you need more detail about specific steps.

Adapt to Your Context

These workflows show common patterns, not rigid procedures. Adapt them to your specific:

  • Species and management system: Individual tracking vs. mob management
  • Team size: Solo operator vs. large coordinated team
  • Regulatory requirements: Country-specific compliance needs
  • Operational complexity: Simple vs. complex facilities

Use these workflows as templates, then modify them for your situation.

Understanding Automatic vs. Manual Actions

Kora automates extensively while preserving professional judgement.

Automatic Actions (Kora Handles)

When veterinarian diagnoses disease:

  • Contact tracing automatically identifies exposed animals
  • Risk scores calculated based on location sharing and proximity
  • Quarantine recommendations generated using disease profiles
  • Health check schedules created based on incubation period
  • Notifications sent to affected location managers
  • Traceability events recorded

When treatment is recorded:

  • Withdrawal period calculated from medication data
  • Expiry alerts scheduled
  • Treatment cost calculated and logged
  • AMR data recorded for stewardship monitoring
  • Task created for follow-up assessment

When movement is logged:

  • Traceability event created in immutable chain
  • Animal location updated automatically
  • Population counts adjusted at origin and destination
  • Movement certificate linked to traceability record
  • Biosecurity status evaluated if crossing zones

Manual Actions (Your Decisions)

Professional judgement required:

  • Deciding quarantine scope (all contacts vs. high-risk only)
  • Approving health certificates (veterinarian verification)
  • Determining treatment approach (which medication, dosage)
  • Escalating to veterinarian (when observation requires professional consult)
  • Assigning tasks to team members (who handles what)

Context-specific decisions:

  • Breeding pair selection (genetic considerations)
  • Grazing rotation timing (pasture condition assessment)
  • Wildlife intervention (when to intervene vs. observe)
  • Culling decisions (economic vs. health vs. welfare factors)

Kora provides data, calculations, and recommendations. You make the final decisions based on your expertise and operational context.

Workflow Categories Explained

Daily Operations (28.1)

Routine workflows forming the operational backbone: morning health checks, treatment administration, regular monitoring. These workflows repeat daily or weekly and become second nature with practice.

Focus: Efficiency, consistency, team coordination

Key Integration: Animals, Observations, Tasks, Treatments, Team coordination

Biosecurity Response (28.2)

Critical workflows for disease events: from initial suspicion through diagnosis, contact tracing, quarantine, and outbreak management. These workflows activate during health crises requiring rapid, coordinated response.

Focus: Speed, accuracy, compliance, stakeholder communication

Key Integration: Observations, Veterinarian, Biosecurity, Quarantine, Contact Tracing, Notifications, Traceability

Regulatory Compliance (28.3)

Documentation workflows ensuring legal compliance: export preparation, health certificate generation, movement documentation. These workflows support trade, regulatory inspections, and certification programmes.

Focus: Accuracy, completeness, audit readiness, verification

Key Integration: Health, Traceability, Movements, Certifications, Documentation

Conservation Operations (28.4)

Wildlife and breeding workflows supporting conservation goals: sighting documentation, population census, breeding coordination. These workflows balance scientific rigour with practical field operations.

Focus: Scientific accuracy, data quality, conservation impact

Key Integration: Wildlife, Locations, Breeding, Habitat, Population Analysis, CITES

Veterinary Consultation (28.5)

Professional veterinary workflows: pre-visit preparation, clinical documentation, treatment planning, follow-up scheduling. These workflows support veterinarian-client coordination and clinical record integrity.

Focus: Clinical accuracy, professional documentation, owner communication

Key Integration: Veterinarian, Observations, Treatments, Tasks, Notifications, Traceability

Tips for Success

Start Simple: Don't try to implement every workflow immediately. Start with one daily routine (e.g., morning health checks), master it, then add complexity (biosecurity response workflows).

Follow the Cross-References: When a workflow references another chapter, follow that link to understand the feature fully. These workflows assume you know basics from Chapters 1-27.

Adapt to Your Reality: These workflows show common patterns. Your operation may need variations. Use these as templates, not rigid scripts.

Practice Before Crisis: Learn biosecurity response workflows before you need them. Practice quarantine initiation, contact tracing, and outbreak coordination during calm periods so you're prepared during emergencies.

Involve Your Team: Share relevant workflows with team members. Morning health check workflows benefit from consistent execution by all staff members.

Use Mobile in Field, Desktop for Planning: Most workflows involve both devices. Record observations mobile in field, then review and plan follow-up actions on desktop.

Trust Automatic Actions: Kora's automatic actions (contact tracing, task generation, notification sending) are based on professional workflows developed with veterinary and biosecurity expertise. Trust the automation while exercising professional judgement on decisions.

WORDS
[1,426]
READ TIME
[8m]