Task Orchestration
The plan writes the day.
Seeding, transplanting, harvest and sanitation generate themselves from the schedule — assigned by role, timed to your shifts.
The daily task list is where most farms quietly lose the plan. It gets rebuilt every morning on a whiteboard, from memory — so what gets skipped is whatever nobody happened to think of at six in the morning, and nobody can tell you afterwards that it was skipped at all.
Tasks are not typed in here. They fall out of the schedule. A cycle due to transplant on Thursday generates a transplant task on Thursday, sized to the trays involved, assigned to the role that does transplanting, and placed in a shift that actually exists. Seeding, harvest and sanitation work the same way.
The crew sees a list for today, on a tablet in the room. You see whether the plan actually happened. And because time is logged against the task, the same completion that closes out the day is what tells you the labor in a pound.
Questions
The things people actually ask.
Can we still create one-off tasks?
Yes. Ad-hoc tasks can be raised by hand, and CultivAid can propose them. Generating the recurring work from the plan is about making sure the predictable jobs do not depend on somebody remembering them.
What happens to the tasks when the plan changes?
They follow it. The schedule is the source, so moving a transplant date moves the transplant task rather than leaving a stale one on somebody's list.
Does the crew need a computer?
No. The platform is a web app and the task list is built to be used on a tablet on the floor, which is where the work actually happens.
See Task Orchestration on a real farm.
We'll walk an order all the way through to its margin — on live farm data, not a slide.