Automatic Documentation of Everything That Matters

Every significant activity in an animal's life creates a traceability event. This is a permanent record documenting what happened, when it happened, where it happened, and who was involved. The key principle: you do not create traceability events manually. They are created automatically as you use Kora's regular features.

Record a movement using Kora's movement system (Chapter 7.3)? Movement event automatically added to the traceability chain. Administer a vaccination using the treatment system (Chapter 10.2)? Vaccination event automatically recorded. Document a health observation (Chapter 10.1)? HealthCheck event appears in the chain. Initiate quarantine (Chapter 11.2)? Quarantine event is there.

This automatic recording is what makes Kora's traceability effortless. You work normally, and compliance documentation happens behind the scenes.

Event Categories: What Gets Recorded

Kora recognises over 30 different event types organised into nine categories covering an animal's complete lifetime from birth to disposal.

Lifecycle Events

Lifecycle events document major milestones in an animal's existence:

Birth: Automatically recorded when animal is created with "Birth" as acquisition source. Documents birth date, birth location, maternal and paternal lineage (if known), and birth circumstances.

Death: Automatically recorded when animal status is set to "Deceased." Documents death date, cause of death (if known), and location. Creates permanent record for regulatory compliance and disease monitoring.

Disposal: Automatically recorded when deceased animal disposal is documented. Records disposal method (burial, rendering, cremation, other), disposal location, and responsible party.

Example birth event:

Event Type: Birth
Date: 2025-01-15 06:30
Location: North Pasture, Calving Paddock
Description: Calf born naturally, healthy condition
Recorded By: Farm Manager

These events appear automatically based on animal lifecycle status changes. You do not create them separately.

Identification Events

Identification events track how animals are identified throughout their lifetime:

InitialIdentification: First identification method assigned to animal (RFID tag, microchip, ear tag). Automatically recorded when animal is created with identification details.

IdentifierAdded: New identification method added (second RFID, microchip implant, visual tag). Automatically recorded when you add identifiers to animal profile.

IdentifierRemoved: Identification method removed or deactivated (lost ear tag, failed RFID). Automatically recorded when deactivating identifiers.

IdentifierReplaced: Identification method replaced (new ear tag after loss, replacement RFID). Automatically recorded when replacing identifiers.

Example identifier replacement:

Event Type: IdentifierReplaced
Date: 2025-03-10 14:15
Description: Ear tag A123 replaced with A456 (original tag lost)
Old Identifier: A123 (Visual Ear Tag)
New Identifier: A456 (Visual Ear Tag)
Reason: Tag lost in field
Recorded By: John Smith

Identification events maintain complete audit trail showing every identification method used throughout the animal's life. Critical for regulatory compliance when identifiers are lost or replaced.

Movement Events

Movement events are automatically created every time you record animal movements:

Movement: Routine movement between locations. Automatically recorded when you use Kora's movement system (Chapter 7.3). Documents from-location, to-location, movement date, reason, and responsible party.

Import: Animal imported from another country or region. Automatically recorded when movement is marked as "Import" type. Includes source country, import permit details, and quarantine requirements.

Export: Animal exported to another country or region. Automatically recorded when movement is marked as "Export" type. Documents destination country, export certification, and health certificate details.

Quarantine: Animal enters quarantine. Automatically recorded when quarantine is initiated (Chapter 11.2). Documents quarantine reason, expected duration, and isolation location.

QuarantineRelease: Animal released from quarantine. Automatically recorded when quarantine is completed. Documents release date, health status, and authorisation.

Example movement event:

Event Type: Movement
Date: 2025-02-20 09:00
From: North Pasture, Subdivision A
To: South Pasture, Subdivision B
Reason: Rotational grazing
Distance: 2.3 km
Recorded By: Farm Manager
GPS Coordinates: -1.2345, 36.7890 (destination)

Every movement you record creates a traceability event automatically. No separate traceability entry required. This creates complete movement history for disease investigation, regulatory audits, and export documentation.

Health Events

Health events document medical care and health status:

HealthCheck: Routine or clinical health assessment. Automatically created when you record health observations (Chapter 10.1). Documents condition, symptoms observed, severity level, and follow-up requirements.

Vaccination: Vaccination administered. Automatically recorded when you document vaccinations in treatment system (Chapter 10.2). Includes vaccine type, batch number, dose, administration route, and withdrawal period.

Treatment: Medical treatment administered. Automatically created when you record treatments. Documents medication, dosage, treatment reason, responsible veterinarian, and antimicrobial resistance considerations (Chapter 19).

Surgery: Surgical procedure performed. Automatically recorded when treatment type is "Surgery." Includes procedure type, surgeon, anaesthesia details, and post-operative care requirements.

Diagnosis: Veterinary diagnosis of disease or condition. Automatically created when veterinarian records diagnosis through veterinarian observations (Chapter 10.1). Includes disease identified, diagnostic method, confidence level, and recommended actions.

TestResult: Laboratory or diagnostic test result. Automatically recorded when test results are documented. Includes test type, result value, interpretation, and testing laboratory.

Example vaccination event:

Event Type: Vaccination
Date: 2025-01-20 10:30
Vaccine: Clostridial 7-in-1
Batch Number: VAC-2024-12345
Dose: 2 mL subcutaneous
Withdrawal Period: 21 days (ends 2025-02-10)
Administered By: Dr. Sarah Johnson (Vet Licence #VET-12345)
Purpose: Annual vaccination programme

Health events create comprehensive medical history supporting treatment compliance, antimicrobial stewardship, withdrawal period verification, and disease investigation.

Breeding Events

Breeding events document reproductive activities:

Mating: Natural breeding event. Automatically recorded when you document mating. Includes sire, dam, breeding date, and observation details.

ArtificialInsemination: AI procedure performed. Automatically created when you record AI treatments. Documents sire genetics, semen batch, AI technician, and procedure date.

PregnancyConfirmed: Pregnancy diagnosis confirmed. Automatically recorded when pregnancy testing results are documented. Includes testing method, expected due date, and pregnancy status.

BirthGiven: Dam gives birth. Automatically created when offspring birth is recorded with maternal link. Documents offspring details, birth complications (if any), and maternal health.

Weaning: Offspring weaned from dam. Automatically recorded when weaning event is documented. Includes weaning age, weaning weight, and post-weaning management.

Example AI event:

Event Type: ArtificialInsemination
Date: 2025-01-10 08:00
Sire: Registered Bull ABC-123 (Angus)
Semen Batch: SEMEN-2024-456
AI Technician: Jane Doe (Certified AI Technician)
Expected Due Date: 2025-10-17 (285 days gestation)
Notes: First AI attempt, excellent condition

Breeding events support genetic management, pedigree documentation, and studbook compliance (Chapter 16).

Ownership Events

Ownership events track custody and ownership changes:

OwnershipTransfer: Permanent ownership transfer (sale, gift). Automatically recorded when you document animal sales or ownership changes. Includes buyer/recipient details, transfer date, price (if applicable), and transfer documentation.

CustodyChange: Temporary custody change without ownership transfer. Automatically created when animal custody is transferred. Documents custodian, custody reason, expected duration, and return conditions.

Loan: Animal loaned to another party. Automatically recorded when loan arrangements are documented. Includes borrower, loan purpose, loan period, and return conditions.

Return: Loaned animal returned to owner. Automatically created when loan completion is recorded. Documents return date, animal condition, and any changes during loan period.

Example ownership transfer:

Event Type: OwnershipTransfer
Date: 2025-03-15 14:00
From Owner: John Smith (Original Breeder)
To Owner: ABC Feedlot Ltd
Transfer Type: Sale
Price: $2,500
Transfer Documentation: Bill of Sale #2025-045
Reason: Commercial sale for finishing

Ownership events create complete chain of custody for legal disputes, export documentation, and market traceability.

Compliance Events

Compliance events document regulatory inspections and certifications:

Inspection: Regulatory or veterinary inspection. Automatically recorded when inspections are documented. Includes inspector details, inspection type, findings, and compliance status.

Certification: Official certification issued. Automatically created when health certificates (Chapter 12.3) or other official certifications are generated. Documents certificate type, issuing authority, validity period, and certificate number.

PermitIssued: Movement or activity permit issued. Automatically recorded when permits are documented. Includes permit type, issuing authority, validity dates, and permit conditions.

PermitExpired: Previously issued permit has expired. Automatically created when permit expiration date passes. Alerts to compliance gaps requiring permit renewal.

ComplianceViolation: Compliance violation identified. Manually recorded when violations are identified by inspectors or management. Documents violation type, severity, corrective actions required, and resolution timeline.

Example certification event:

Event Type: Certification
Date: 2025-02-10 11:00
Certificate Type: Export Health Certificate
Certificate Number: EHC-2025-00123
Issuing Authority: Government Veterinary Services
Issued By: Dr. Michael Chen (Official Veterinarian)
Valid Until: 2025-03-12 (30 days)
Purpose: Export to European Union
Covered Diseases: Foot-and-Mouth Disease, Tuberculosis, Brucellosis

Compliance events provide evidence of regulatory adherence for audits, export approvals, and food safety investigations.

Welfare Events

Welfare events document animal welfare assessments:

WelfareAssessment: Formal welfare evaluation. Automatically created when Five-Domain Welfare Assessments (Chapter 10.3) are completed. Documents welfare score, domain scores, and welfare concerns identified.

BehaviouralObservation: Behavioural changes or concerns. Automatically recorded when behavioural observations are documented. Includes behaviour type, severity, frequency, and welfare implications.

EnvironmentalChange: Significant environmental change affecting animal welfare. Manually recorded when environmental conditions change. Documents change type, welfare impact, and mitigation measures.

Example welfare assessment:

Event Type: WelfareAssessment
Date: 2025-02-05 10:00
Assessment Type: Five-Domain Model
Overall Score: 82/100 (Good)
Nutrition Domain: 85/100
Environment Domain: 80/100
Health Domain: 75/100
Behaviour Domain: 88/100
Mental State Domain: 82/100
Assessed By: Dr. Sarah Johnson (Veterinarian)
Concerns: Minor lameness noted, treatment recommended

Welfare events demonstrate animal welfare commitment supporting premium market access, certification programmes, and social licence.

Administrative Events

Administrative events document record management and verification:

DataCorrection: Correction to previously recorded data. Manually created when errors are corrected (see Chapter 12.1 for correction process). Documents original error, correction details, and correction reason.

RecordMerge: Multiple records merged into single record. Automatically recorded when duplicate animal records are merged. Documents merged records and consolidation reason.

ChainVerification: Traceability chain integrity verified. Automatically created when regulatory authorities or administrators verify chain integrity. Documents verification level, verification result, and verifying authority.

AuditPerformed: Formal audit of traceability records. Automatically recorded when traceability audits are conducted. Includes auditor, audit scope, findings, and compliance determination.

Example verification event:

Event Type: ChainVerification
Date: 2025-03-01 15:30
Verification Level: Full Chain Verification
Verification Result: Valid - All events verified
Chain Integrity: 100% (0 issues found)
Event Count: 47 events verified
Verified By: Regulatory Authority Inspector #RA-567
Verification Method: Cryptographic hash verification

Administrative events maintain transparency in record management and provide audit evidence.

Automatic vs. Manual Event Recording

The vast majority of traceability events are created automatically:

Automatic Events (95%+ of Events)

Created automatically when you use Kora's regular features:

• Movement events - Created when you record movements (Chapter 7.3)
• Health events - Created when you document observations (Chapter 10.1) or treatments (Chapter 10.2)
• Identification events - Created when you add/remove/replace identifiers
• Lifecycle events - Created when you update animal status (birth, death)
• Quarantine events - Created when you initiate/release quarantine (Chapter 11.2)
• Certification events - Created when health certificates are generated (Chapter 12.3)
• Breeding events - Created when you document breeding activities
• Ownership events - Created when you record sales or ownership changes

You do not create these events separately. They appear automatically in the traceability chain as you work normally.

Manual Events (5% of Events)

Occasionally recorded manually:

• DataCorrection: When correcting errors in previous records
• ComplianceViolation: When documenting regulatory violations
• EnvironmentalChange: When significant environmental changes occur
• CustomEvent: For unusual circumstances not covered by standard event types

Manual events are the exception, not the norm. Traceability is designed to be automatic.

Evidence Attachment

Events become more valuable with supporting evidence:

Photo Evidence

Attach photos to events documenting visual evidence:

• Identification photos: Show ear tags, brand marks, or physical features
• Health condition photos: Document injuries, symptoms, or treatment sites
• Location photos: Show movement destinations or environmental conditions
• Facility photos: Document housing, equipment, or biosecurity measures

Photos are attached when recording the underlying activity (observation, movement, treatment) and automatically linked to the corresponding traceability event.

Document Evidence

Attach official documents providing regulatory proof:

• Health certificates: Automatically attached when generated (Chapter 12.3)
• Test results: Laboratory reports, diagnostic results, veterinary certificates
• Permits: Movement permits, import/export permits, activity authorisations
• Inspection reports: Regulatory inspection findings, compliance audits
• Bills of sale: Ownership transfer documentation, purchase receipts

Documents provide legal evidence supporting traceability events for regulatory compliance and dispute resolution.

Automatic Document Attachment

Some documents are attached automatically:

• Health certificates generated in Kora automatically attach to corresponding Certification events
• Permit documents automatically link when permits are issued
• Test results automatically attach when results are recorded

Other documents can be manually uploaded and linked to specific events providing comprehensive documentation.

Event Timeline: Viewing Complete History

Every traceability chain includes a complete event timeline showing:

• All events in chronological order from chain creation to present
• Event details (type, date, description, location, responsible party)
• Attached evidence (photos, documents, certificates)
• Cryptographic verification (event integrity status)
• Event relationships (which events triggered which automatic events)

The timeline provides instant access to complete lifetime history for regulatory audits, disease investigations, export documentation, or operational analysis.

Example timeline excerpt:

📅 Traceability Chain Timeline: KEN-FRM-2025-000001

Jan 15, 2025 06:30 - Birth
    Calf born naturally, North Pasture Calving Paddock

Jan 15, 2025 08:00 - InitialIdentification
    RFID Tag: 982-123-456-789-012 assigned

Jan 20, 2025 10:30 - Vaccination
    Clostridial 7-in-1 administered, 21-day withdrawal

Feb 10, 2025 11:00 - Certification
    Export Health Certificate EHC-2025-00123 issued

Feb 15, 2025 09:00 - Movement
    From: North Pasture → To: South Pasture (rotational grazing)

Feb 20, 2025 14:00 - HealthCheck
    Routine assessment, excellent condition, no concerns

Mar 01, 2025 15:30 - ChainVerification
    Regulatory authority verified chain integrity (100% valid)

This timeline is automatically populated as events occur. No manual compilation required.

Event Severity Levels

Events can have severity levels indicating importance:

• Information: Routine events with no concerns (normal movements, scheduled vaccinations, routine health checks)
• Low: Minor issues not requiring immediate attention (minor behavioural changes, low-priority corrections)
• Medium: Moderate concerns requiring monitoring (health observations with follow-up, permit expirations approaching)
• High: Significant issues requiring prompt attention (disease diagnoses, compliance violations, failed inspections)
• Critical: Emergency situations requiring immediate action (emergency quarantine, critical health deterioration, serious compliance breaches)

Severity levels help prioritise attention when reviewing event timelines and support automated alerts for critical events.