Industry field guide
Other poultry cohort and inventory records for AI
An inventory correction can refer to a cohort without documenting an actual transfer.
- 2022 NAICS
- 112390
- Practice pack
- Example and answer key (JSON)
- Updated
What this guide tests
Which inventory changes are supported, and which records actually document a transfer rather than a count correction?
See the specimen and fields · Work through the fictional records
Task and source context
An inventory correction can refer to a cohort without documenting an actual transfer. USDA APHIS publishes poultry industry materials. A producer can simulate a small event sequence to test whether a model distinguishes the recorded count from an observed movement. USDA APHIS poultry industry manual
Create two imaginary cohorts with similar labels. Add a dated count correction for one and a verified transfer for the other. Ask which entries changed the practice inventory and whether the records support a transfer. Include a case with no independent verification so the answer must acknowledge uncertainty.
Use no actual animal health records, facility details, supplier identities, live footage or worker data. Use independently written values and have a reviewer check the mock sequence.
Industry research
The U.S. Census Bureau’s industry definitions establish which activities these codes cover. The workflow sources in this guide describe the task or record type. Fiund’s pilot below uses fictional material to test a specific decision within that scope.
112390 · Other Poultry Production
This industry comprises establishments primarily engaged in raising poultry (except chickens for meat or egg production and turkeys).
Build a pilot sample
Set up this pilot
Build mock cohort counts with a corrected duplicate and a separately authorized transfer. Grade inventory movements by event type and retain the count correction separately.
Prepare the test packets
- Start with the worked case. Use the fictional record types below as a guide to the source files you need. Give each packet a stable ID and save its source versions with it.
- Change one fact. Make one packet with enough evidence to answer the question and one where the evidence points to a different answer. Keep the other fields fixed so a reviewer can tell what changed.
- Remove the decisive evidence. Give the reviewer a third packet with a plausible near-match in its place. Have them write what can still be established and what evidence would resolve the rest.
Fields the reviewer needs
- Cohort and reference date
- Defines the count.
- Correction reason versus movement type
- Distinguishes different causes of record change.
- Verification and source/destination reference
- Supports or limits a transfer claim.
Use Plan a farm, forest or fishery AI data sample to turn the specimen into a brief with a defined task, source and review owner.
Fictional exercise
A corrected count is not itself a recorded transfer
Two imaginary poultry cohorts have artificial counts and original event cards. No animal handling, health information, facility detail or live footage is involved.
| Record ID | Source | What it records |
|---|---|---|
| PC1 | Cohort A count | Day 1 inventory 20. Reviewed correction replaces it with 18 and says earlier count error; no movement event associated. |
| PC2 | Cohort A2 transfer | Distinct cohort A2 begins at 30; verified fictional transfer of 4 to destination D on day 2, leaving 26 at source. |
| PC3 | Unverified note | Says 'A moved 2' without date, source document or reviewer confirmation. No destination receipt supplied. |
Question for the model. Which inventory changes are supported, and which records actually document a transfer rather than a count correction?
Show the reference answer
PC1 supports replacing A's erroneous day-1 count with 18, but explicitly supplies no movement. PC2 documents a four-unit transfer for separate cohort A2 and its resulting source count of 26. PC3 is an unverified, undated note and cannot explain PC1's correction as a confirmed two-unit transfer. Keep corrected counts, documented movements and unresolved notes distinct rather than assuming every numerical change represents an observed movement.
How to check the result
Ask for the answer, the record IDs that support it and any fact the evidence leaves unresolved. Have a reviewer compare the response against the reference before deciding whether the sample is ready to expand.
Errors to flag in this case
- Turning a count correction into a transfer event.
- Merging similarly named cohorts or using an unverified note to create a destination history.
Change the inputs and run it again
Add a signed mock correction confirming PC3's date but not its cohort identity. Require the identity conflict to remain open.
Score the decision and the evidence separately
Save the reviewer’s expected answer, supporting record IDs and unresolved fields in a separate answer key. Score the model on the decision, its citations and its handling of the deliberate gap. A correct answer citing a different case counts as an evidence error.
Before expanding collection, have a second reviewer run the same checks on the held-out packet. Keep related versions, views and exports of the same case together so they stay on one side of the training and evaluation split.
Check permission and scope
Use independent fictional values and reviewer keys. Exclude actual health, supplier, worker and facility information; no animal decision is made.
Use owner-approved administrative records or staged material. Exclude unnecessary animal, farm, staff and customer identifiers.
Describe an authorized archive through Fiund’s existing-data assessment, or describe a new capture capability through the collection brief. The contributor agreement covers the terms for participation.
Sources and further reading
Resources for this workflow
Company and program reviews
Use these reviews to compare sourcing, capture or evaluation approaches. Confirm the applicable program, accepted sources and terms with the provider.
Compare the approach
truelabel review for teams collecting physical AI data
Compare how a capture team specifies devices, processing and quality review for an outdoor recording pilot.
Compare the approach
Graviti review for workplace video and multimodal training data
Compare a catalog with commissioned multimodal collection when a particular crop, setting or viewpoint matters.
Related industry examples
Industry guide · NAICS 112340
Poultry hatchery tray lineage records for AI
A tray may change rooms while retaining its link to the source flock.
Industry guide · NAICS 112310
Egg shell inspection images for evaluating AI
An exterior image and a candled image reveal different evidence.
Industry guide · NAICS 112320
Broiler and turkey water-meter data for AI review
A meter reset can appear as a sudden drop in a poultry house’s cumulative water reading.