Plan Breedings, Litters And Shows5-10 minutes per breeding

Plan Breedings And Track Fertility Over Time

Log pairings, keep breeding timelines organized, and use the breeding planner to keep due dates and outcomes visible.

What This Helps You Do

Create a breeding record the right way so milestones, tasks, and later litter work all stay connected and understandable.

Estimated Time

5-10 minutes per breeding

Exact Navigation Path
Desktop

Desktop: Open Breedings from the left sidebar.

Mobile

Mobile: Tap the menu button, then tap Breedings.

Before You Start
  • Make sure the doe and buck already exist in the Rabbits list.
  • If you use automated breeding tasks, make sure your breeding-related settings are roughly correct first.
breedingpairingpalpationkindlingfertilityplanner

Overview

  • The breeding planner turns each pairing into a trackable timeline instead of a note you have to remember later.

When To Use

  • You are scheduling pairings, tracking fall-offs, checking fertility, or reviewing breeding outcomes.

Step-By-Step Guide

1

Start a new breeding record

Begin from the Breeding Planner so the pairing is created in the workflow built for it.

1.1 Open Breedings

Open Breedings from the sidebar or mobile menu.

What You Should See
  • You should see the breeding planner page and an action to add or plan a breeding.
1.2 Create the pairing

Use the add or plan breeding action to open the breeding form.

What You Should See
  • You should see fields for doe, buck, pairing date, and breeding details.
You Should Now Have
  • You are now in the correct place to record the breeding.
2

Fill in the pairing accurately

This is the part that drives later dates and selector behavior.

2.1 Choose the doe and buck

Select the correct doe and buck from the available rabbit selectors.

If You Don't See This
  • If one of the rabbits is missing, stop and verify that rabbit is saved in the herd and has a status that fits breeding workflows, such as Active or Co-Breeding.
2.2 Enter the pairing date

Set the real pairing date, not the date you happen to be entering the record later.

Watch For This
  • Automated milestone dates depend on the pairing date, so guessing here causes confusion later.
2.3 Save the breeding

Save the record so it appears in the breeding planner timeline.

What You Should See
  • You should return to the breeding planner and see the pairing listed.
You Should Now Have
  • The breeding record now exists and should be driving its timeline.
3

Check the timeline before moving on

This catches bad dates or wrong rabbits before you build more records on top of the breeding.

3.1 Review the saved timeline

Look at the saved breeding entry and confirm the due dates, planned milestones, and rabbit names make sense.

What You Should See
  • You should see milestone dates or planner information tied to the breeding.
3.2 Add notes or outcome updates later

Return to this record as the breeding progresses to log fall-offs, failures, or eventual outcomes.

Why This Step Matters
  • Do not delete unsuccessful breedings just because they did not result in a litter. They are still useful records.
You Should Now Have
  • You now have a breeding record that can support litters, tasks, and later fertility review.

You're Done When

  • The breeding appears in the planner after saving.
  • The correct doe and buck are attached to it.
  • The resulting dates look reasonable for your program.

Common Mistakes

  • Only recording successful pairings and losing insight into repeated failures or timing issues.
  • Forgetting to review due dates after changing your operational settings.

FAQ

Should I log failed breedings?

Yes. Failed pairings help you spot timing, fertility, and match-up patterns that disappear if you only save the successful ones.

When To Contact Support

  • A saved breeding does not appear in the planner.
  • Automated milestone dates look obviously wrong even after re-checking your settings and pairing date.

Still Stuck?

If the guide got you close but the app still does not match what this tutorial says should happen, contact support and mention the article title, the exact step where you got stuck, and what you saw instead.