Crop planning

A crop plan records the selected field, crop variety, planting date, expected harvest date and planned area. Farm Manager reviews that intention alongside the field register. The crop cycle follows the season that proceeds, keeping the crop name and variety with the field and its current stage.

Field Operator submits the plan through the authorized crop-plan command. The command validates the request before saving, creates or reuses a matching crop cycle and returns source links. Repeating the same field, variety and planting date returns the original plan. An operator recovering from an uncertain response can identify the saved intention before the manager prepares field work.

• Planting intention. Keep the chosen field and variety with the planting and expected harvest dates. The planned area describes the scope of this planting. Farm Manager compares it with the field’s recorded area and agrees whether the intention fits the operating situation.
• Season record. Follow the crop-cycle detail returned by the command. Check the crop name, variety and field before attaching tasks. Planned, Planted and Growing describe the recorded crop progress. Harvesting and Closed belong to the later harvest handoff.
• Source continuity. Use the saved plan’s source links when following the command result. If the operator repeats a submission after losing the response, recover the original plan and inspect the linked work before making another planting decision.

Agree the farm’s variety names and how staff select a field. Use the same vocabulary in the plan and crop cycle so a manager can recognize a match. Determine the area convention used for planning, and decide how Farm Manager compares the planting intention with the plot’s area in hectares.

Set up command access for the intended Field Operator account. Farm Manager manages crop plans; the operator’s submission route needs its own access rehearsal. Decide how existing crop cycles will be recognized and review the returned source links with the people preparing work. Resolve an unexpected cycle match before any task is attached.

Plan a bean variety for East Plot using reviewed planting and expected harvest dates. Submit through the crop-plan command, open the saved plan and follow the returned crop cycle. Farm Manager checks the field and variety, then reviews the area before preparing planting work. A saved plan records an intention; the manager still records actual planting progress when it occurs.

Repeat the same field, variety and planting date. Confirm that the original plan is returned. Inspect its source links before moving on to task preparation. Then attempt submission with an account that lacks command authority and check that the refusal leaves the plan and cycle records unchanged. Agree how a changed planting intention will be handled separately from recovering an earlier request.

• Crop Plan Calendar — Planting and expected harvest dates with the selected field, variety and planned area.
• Active Crop Cycles — The season records behind those plans, with current stages and recorded planting and harvest dates.

Use field to crop cycle, then move the selected cycle into approved field work.