Questions, answered

Click Get started, then use Proto to configure Greenhouse Management for your business. Start with one field, one crop cycle, the people who approve and perform work, one input lot and a representative harvest.

Create a separate crop cycle for each planting, linked to the field where it grows. Keep crop and variety names consistent so repeat plantings can be compared without mixing their tasks or harvests.

Yes. A field task can carry Irrigation or Feeding as its task type, with a due date, cycle, field and assigned person. The manager reviews planned work before it is marked approved.

Record the lot in input stock and link each applied quantity to both that lot and the field task. Review the lot’s unit, expiry and quantity on hand before another use.

Use a field observation for the date, type, value, unit and notes of a scouting finding. Use a nutrient reading for an applied input, quantity, unit, date, field and applicator.

Enter its date, measured quantity, unit, grade and crop cycle. A named harvest reviewer checks the live record and linked cycle before accepting the evidence.

A greenhouse zone record can hold surveyed boundary geometry, survey date and area linked to a field. Agree the field and zone naming before importing maps.

Bring one field, a current planting, the people who approve and perform work, one input lot and a measured harvest. Rehearse the handoffs before adding more growing areas.

The Field work board shows the assigned person on each task. Set up People and Users links, then rehearse the manager and grower permissions before opening task records to the wider team.