What should I do?

Try it before you commit to it.

Pick a crop and how much land. You get the full span the crop table allows — a bad year, a good year, and the middle — carried through the sums. Anything the table cannot support is listed as refused instead of filled in with a guess.

Crop

Area (hectares)

Fodder Maize over 1.00 ha

This crop projects on time and inputs, but not on yield.

What this would need and produce. Every row is a range, never a single number.
Quantity	Low	Central	High	Where this came from
Seed	50.0 kg	—	60.0 kg	seed rate, “50–60 kg”, multiplied by area
Season water	4,000 m³	—	6,000 m³	“400–600” mm/season × 10 m³ per mm per hectare
First harvest	Nov 2026	—	Nov 2026	60–70 days from today

This is out of window today.

The reference states a sowing window of Jun–Jul, Feb. Today is September.

What this refused to guess at

Yield — this crop is measured in something other than tonnes (timber volume, stems, blooms, or fresh fodder), and multiplying it by an area would produce a confident wrong number.
Revenue — no price registry is answering for this crop, and a made-up price is the fastest way to make every other figure here worthless.

Refusing is the point. Each of these could be filled in with a sensible-looking default, and once it had been multiplied by your area you would have no way of telling it from a real measurement.

Commit this to memory

Saving this records what you meant to do, on how much land, on what date, and against which numbers. At the end of the season you then have something to compare the real result against. That comparison is the only way this system gets better at your farm rather than at farms in general.

Nobody is identified on this request, so this is kept in this browser only — it is not sent anywhere and it will not follow you to another device.