Tomato: an analysis-led 90-day nutrient program

Overview

# Tomato: an analysis-led 90-day nutrient program

## Goal and personal-program workflow

Turn nutrient work into analysis → budget → approval → recording → stage review. Use Adapt to my program to create your private farm program without a public Hub profile. Edit steps, day offsets and approved product/input quantities; preview the selected real fields and start date, then create the calendar tasks. Tasks are planned work, not evidence of application. The eight example offsets 0/1/3/10/24/38/60/90 are editable, not a universal tomato crop calendar.

## Required inputs

Confirm field ID/area, outdoor or greenhouse system, variety and actual planting date. Obtain the laboratory report/date, pH, EC and declared N/P/K units; the locally qualified expert's approved nutrient budget; credits from prior organic/mineral inputs; product-label nutrient percentages; and an authorized approver. Do not infer deficiency from a visible symptom alone or transfer regional recommendations directly to a different country.

## Budget arithmetic: an example only

If a hypothetical approved remaining need is 20 kg N/ha, a hypothetical product is 46% N and the area is 2 ha: product = 20 / 0.46 = 43.478 kg/ha; total = 86.957 kg. These numbers demonstrate arithmetic, not a tomato dose recommendation. Use your own approved need and label. Product kilograms differ from nutrient kilograms; do not mix N with P₂O₅/K₂O units. Apply rounding according to the approved plan and equipment, after calculating the unrounded total.

## Procedure and acceptance

1. Attach a unit-checked soil report and field card; record previous inputs separately.
2. Create `nutrient-budget.csv`: `field_id,area_ha,nutrient,basis,target_kg_ha,credited_kg_ha,remaining_kg_ha,product,label_fraction,planned_product_kg,approver_alias,approval_reference`. Only an approved source supplies targets/credits; record nutrient basis and prevent double counting.
3. Edit preplant/flowering/fruit-set dates to real phenology and the approved schedule. Remove unnecessary application steps or turn them into review tasks. Check product/batch, field, method and approved quantity before action.
4. Reconcile actual applications and remaining budget at each stage; obtain renewed approval for changes instead of repeating an old plan. Calendar creation does not automatically consume inventory; real stock handling requires the actual reservation workflow.
5. Close with completed/pending tasks, deviations, report/approval references and the next-period reassessment.

## Worked record and deliverables

```csv
field_id,date,stage,product,approved_total_kg,actual_total_kg,decision,reviewer
example-field,2026-04-03,preplant,example-product,86.957,86.957,approved,reviewer-01
```
This row is synthetic and belongs only to the arithmetic exercise. Real logs use actual dates, approved products and measured totals. Deliver a field/report link, approved budget, planned-versus-actual quantities, stage observations and deviation log. Accept when units and area agree, credits are not counted twice, task previews reflect real stages, actual approval is recorded separately from completion, and every uncompleted action has a next status. Measured yield needs its source/unit; this program cannot establish yield improvement.

## Privacy, references and license

Keep real report documents, personnel and precise locations private unless sharing is authorized. University of Minnesota Extension references: https://extension.umn.edu/agriculture/specialty-crops/interpreting-soil-tests-for-fruit-and-vegetable-crops and https://apps.extension.umn.edu/calculators/crop/index.html . Their regional recommendations are context-specific; linked content retains its own terms. Original program/example: AgriDigi, [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Credit the original source, link the license and record adaptations. The program does not replace laboratory analysis or an authorized field decision.

Action plan

Crop: Tomato · Duration: 90 days

1. Record soil analysis and production conditions

   Day 0

   Record report ID/date, pH, EC and the lab's N/P/K units. Verify field area, outdoor/greenhouse system, variety and actual planting date; list earlier organic/mineral inputs separately. Deliver a linked report and unit-checked field card. Accept only traceable units and inputs; a symptom alone is not a nutrient diagnosis.

2. Convert an approved nutrient budget to product quantities

   Day 1

   Record the expert-approved nutrient need and prior-input credits. Calculate product totals from the label fraction, nutrient basis, units and field area. Add the approved product/quantity to this private program step. Deliver the calculation, approval reference and planned total. Accept only approved inputs and no double-counted credits; the program supplies no automatic rate.

3. Check and record any approved preplant application

   Day 3

   Edit the day to the actual planting/application schedule. Verify product/batch, field area, method and approved quantity. Remove an unnecessary step or convert it to review. Deliver actual date, area, total and operator alias. Accept a real approval and completion record separately; inventory consumption requires the actual stock reservation workflow.

4. Review establishment observations and record consistency

   Day 10

   Observe the agreed stops, development, irrigation status and visible symptoms. Do not call a symptom a nutrient deficiency. Compare planned and actual applications and document weather/access deviations. Deliver dated observations and, where needed, an expert-review task. Accept complete evidence and an owner for unresolved concerns.

5. Review the budget and approved plan at flowering

   Day 24

   Move the day to observed phenology. If the lab/local expert requests leaf analysis, follow their sampling instruction. Reconcile past totals with the remaining approved budget. Deliver an approved continue/change decision and any updated product/quantity. Accept documented approval; the date alone is not a fertilizer order.

6. Reconcile actual inputs at fruit set

   Day 38

   Verify actual stage, product label, approved changes and application logs. Reconcile units, area and totals; do not repeat an old plan without renewed approval. Deliver actual/remaining nutrient budget and responsible person's decision. Accept traceable quantities and references, with unresolved differences recorded.

7. Compare harvest observations with the application trail

   Day 60

   Adapt the day to actual harvest. Join input logs, analyses and observations by field ID. If yield is measured, record source and unit; do not attribute improvement to this template. Deliver a traceable stage review and next inspection date. Accept only measured values or explicit unknowns.

8. Close the cycle and prepare an adapted next-period program

   Day 90

   Summarize actual quantities/dates, reports, approvals and deviations. Reschedule unfinished tasks with reasons; reassess different fields against current analysis before a new cycle. Deliver a program review and next-period copy retaining attribution. Accept complete/pending states, renewed inputs and no automatic repetition of old amounts.