# Breeding plan brainstorm

**URL:** <https://farmos.discourse.group/t/breeding-plan-brainstorm/2303>\
**Category:** Development\
**Tags:** feature-request\
**Created:** [May 21, 2025, 1:09pm UTC](https://farmos.discourse.group/t/breeding-plan-brainstorm/2303 "2025-05-21T13:09:43Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![BOTLFarm](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/botlfarm/32/74_2.png) [@BOTLFarm](https://farmos.discourse.group/u/BOTLFarm)\
**Post date:** [May 21, 2025, 5:11pm UTC](https://farmos.discourse.group/t/breeding-plan-brainstorm/2303/6 "2025-05-21T17:11:01Z")

</div>

> [@mstenta](#):
>
> This would extend the plan in the other direction (before insemination), I imagine. Would love to hear more about what these requirements/use-cases might look like in the UI / data model, as I don’t have experience with this myself.

For me if I’m breeding a sow that has had a break I typically will track 2 or more heat cycles before breeding. This will let me better gauge when the sow will be I heat next so I can order semen for the correct time.

> [@mstenta](#):
>
> These kinds of schedules feel like they could be generalized to all types of activities

Agreed. This reminds me of a discussion years about about time tracking, reoccurring tasks, and timmers. [Additional log "time" features - any interest?](https://farmos.discourse.group/t/additional-log-time-features-any-interest/519)

---

_[View the full topic](https://farmos.discourse.group/t/breeding-plan-brainstorm/2303)._