For collectors managing several carnivorous plants over weeks or months, it is easy to lose track of which specific plant was fed, what type of prey was used, and whether the plant actually exhibited a response. Without a structured log, identifying which traps are functioning effectively and which have become dormant becomes a matter of guesswork rather than data-driven observation.
What This Article Covers
This article outlines the essential data points for maintaining an organized feeding history. It provides a standardized list of record fields that allow collectors to track the efficacy of feeding sessions and the activity levels of individual traps within their collection.
Essential Record Fields for a Feeding Log
To move beyond general memory, each feeding event should be documented using specific fields. This structure ensures that the data remains comparable across different plants and time periods.
| Field | What It Captures |
|---|---|
| Plant | The specific individual in the collection that the entry belongs to. |
| Date Fed | The exact date the feeding session occurred. |
| Prey Type | The specific type of prey used: Fruit fly, Mealworm, Cricket, Bloodworm, Liquid fertilizer, or Other. |
| Prey Size | The size of the prey categorized as Small, Medium, or Large. |
| Trap Used | A free-text identifier for the specific leaf or trap number (e.g., “Pitcher #4” or “Newest leaf”). |
| Response | A simple Yes/No/Unknown status indicating if the plant responded to the prey. |
| Response Time | The duration, recorded in hours, for the plant to complete its response. |
| Notes | A free-text area for additional observations regarding the session. |
The Value of Linking Entries to Specific Traps
Linking feeding entries to a specific plant and a designated trap—rather than keeping general, collection-wide notes—allows for the identification of long-term patterns. By reviewing these records, a collector can determine which traps are actively catching and digesting prey versus those that may have become dormant or unresponsive. This level of detail transforms a simple list into a functional history, making it easier to see how individual specimens are behaving over time.
Streamlining History with TrapNote
We developed the Feeding Log feature within TrapNote to handle these specific data clusters natively on iOS. Instead of recording feedings in a generic notes app where data can become lost, TrapNote allows you to attach every feeding event directly to a plant’s profile. The interface includes dedicated selectors for Prey Type and Prey Size, and tracks Response Time and trap identifiers, ensuring your grow list remains a comprehensive and searchable record of every trap’s activity alongside its growth records.
For a broader look at why keeping this data in one place beats a spreadsheet, see One App or a Spreadsheet? What Carnivorous Plant Collectors Should Actually Be Recording.
Summary
Maintaining a detailed feeding log is a critical component of professional collection management. By standardizing fields such as prey size, trap identification, and response time, collectors can move away from fragmented memory and build a reliable history of their plants’ activity. Structured record-keeping ensures that every feeding session contributes to a clearer understanding of the collection’s development.
Consult a specialist or supplier before making decisions about your plant’s growing environment or care.
This article organizes information from a recording and organizing perspective. If you notice an error or outdated information, please contact us. Last verified: July 2026
