# Plans with checklists

**URL:** <https://farmos.discourse.group/t/plans-with-checklists/2527>\
**Category:** Using farmOS\
**Created:** [May 25, 2026, 9:09pm UTC](https://farmos.discourse.group/t/plans-with-checklists/2527 "2026-05-25T21:09:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pat](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/pat/32/1050_2.png) [@pat](https://farmos.discourse.group/u/pat)\
**Post date:** [May 25, 2026, 9:09pm UTC](https://farmos.discourse.group/t/plans-with-checklists/2527/1 "2026-05-25T21:09:46Z")

</div>

I’m working with new ideas on my pig management in farmOS, and I try to make some checklists.

From another module I create an animal (flock) asset for each batch, and try to collect all relevant registrations and sensor data within it’s proper animal asset.

There are tasks to do for each batch, and a checklist would be nice. Not sure how I should plan for this, but I think a plan could work.

I tried adding a plan type for this, and a quickform that creates a handful of pending activity logs.  
The plan has a checklist view that lists these logs with a “Mark done” button.

 ![image](https://global.discourse-cdn.com/free1/uploads/farm_os/original/2X/9/9116a6eb3490018570d96043b5160ac4f0b91feb.png)

It will aggreagte quite a few logs over time. When the bach is “closed” I could melt all these logs into one with a note summary.

Is this a proper way to make such a list, or are there other ideas?

---

<div class="post-metadata">

**Author:** ![pat](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/pat/32/1050_2.png) [@pat](https://farmos.discourse.group/u/pat)\
**Post date:** [May 25, 2026, 11:36pm UTC](https://farmos.discourse.group/t/plans-with-checklists/2527/2 "2026-05-25T23:36:42Z")

</div>

Hm.. another approach:

The [farm\_rotation](https://farmos.discourse.group/t/a-solution-to-repeating-events/2519) module for repeating tasks could perhaps do this too.  
This approach would add logs of desired types with duedates relative to the events in the plan.  
This will not clutter the rotation schedule itself.

Maybe also add a taxonomy to each log for filltering options later.

Might be a bit complex to setup and make changes, but very flexible.

 ![image](https://global.discourse-cdn.com/free1/uploads/farm_os/original/2X/b/b3d552e012f8bf75dfef7929d1c72e44091dd8ab.png)

---

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [June 8, 2026, 12:37pm UTC](https://farmos.discourse.group/t/plans-with-checklists/2527/3 "2026-06-08T12:37:08Z")

</div>

This reminds me of the Template module use-case that @paul121 was working on: [Template module](https://farmos.discourse.group/t/template-module/2054)

> [@Template module](https://farmos.discourse.group/t/template-module/2054/1):
>
> - Use templates in plans. The idea is that you want to configure a plan at the beginning of the year with various templates for the actions to take throughout the year, perhaps on a recurring schedule. The plan will house the templates/logs and track progress. Templates can be re-used across plans. **Some of this is implemented but needs more work**