Labor
Time on task. And the hours next month needs.
Labor is the biggest line in indoor farming. This is the module that says where it went — and where it is going.
Labor is the largest cost in indoor farming and the least attributed. A payroll total tells you what you spent. It does not tell you that harvest is eating 40% of it, that the seeding line is over-staffed on Tuesdays, or what a pound of basil owes to the people who actually grew it.
Time is logged against the task, and every task already knows the department it belongs to. Apply that department's rate and the hours become a cost — against the cycle, against the harvest, and against the pound. Not allocated by a percentage somebody chose. Allocated by hours actually worked on that batch.
It also reads forward. The production plan already knows the task load next month will generate, so the platform can tell you how many hours that plan is going to demand before you commit to it — which is while a staffing problem is still cheap to solve.
Questions
The things people actually ask.
How does labor get attributed to a batch?
Time is logged against tasks, and tasks are generated against cycles. So the hours a harvest actually consumed are the hours that harvest carries in its COGS — no allocation percentage, no month-end guess.
Is this a time clock on our people?
It is time on task, by department, and it exists so that the cost of a pound is real. It is not a surveillance product and it does not follow anybody around between tasks.
How is the hours forecast built?
From the plan. The production schedule generates the task load for a period, and the forecast is what that load will take at your department rates — so a staffing gap shows up before the month does.
See Labor on a real farm.
We'll walk an order all the way through to its margin — on live farm data, not a slide.