Aragro — Blog (English)

How to forecast a crop's harvest

2026-07-19T00:00:00Z

A harvest estimate, or yield forecast, is a pre-harvest calculation of what a crop will produce. It gives the farm a number to plan pickers, transport, storage, sales commitments and cash flow against. It is not a promise: the useful estimate is one with clear, dated assumptions that can be checked against the harvest.

What separates an estimate from the actual harvest

An estimate and a recorded harvest measure different things. The estimate measures the standing crop on a given date and projects the rest of the cycle on an explicit assumption. The US National Agricultural Statistics Service (NASS) states its own plainly: forecasts are based on conditions as of the survey reference date and assume normal conditions for the remainder of the season, and the agency "does not attempt to predict future weather conditions" (USDA NASS, Understanding USDA Crop Forecasts). The actual harvest, by contrast, measures what crossed the scale.

The gap between the two numbers has two parts: what changed after the measurement, and loss in the field. That is why the yield definition recommended in a methodological review commissioned under the FAO Global Strategy is "biological yield minus harvest loss in the field" (Hanuschak, Timely and Accurate Crop Yield Forecasting and Estimation, FAO Global Strategy). NASS measures that loss directly: once the grower has harvested, the enumerator returns and weighs the grain left on the ground. On a farm the expected-loss factor plays that role, calibrated from past harvests.

Formula and worked example

A field estimate scales a representative sample to the productive part of a plot:

Estimated yield = productive area × plant density × average yield per plant × (1 − expected loss)

Productive area is the planted area after paths, gaps and unplanted zones are removed.
Plant density is plants standing per unit of area, not necessarily the density originally planted.
Average yield per plant is the harvestable weight from the sample.
Expected loss is the share likely to be lost to drop, pests, quality rejects or handling.

Input	Value
Productive area	2 ha
Plant density	2,500 plants/ha
Average yield per plant	4 kg
Expected loss	10% (0.10)
Estimated yield	2 × 2,500 × 4 × (1 − 0.10) = 18,000 kg

The same figures are 9,000 kg/ha: 2,500 × 4 × 0.90. Keep that per-area figure as well as the total, since it makes plots of different sizes comparable.

Sampling design: where samples go and how many

Where the sample sits matters as much as how many you take. In the NASS objective yield surveys, the enumerator walks a randomly selected number of paces into the field and marks off a sample plot there "no matter what the condition of the crop at that location". The rule exists to remove the bias of picking convenient plants (USDA NASS, objective yield surveys).

A study of smallholder maize in Ethiopia, published in Food Policy, compared sampling variants against a full harvest of the plot that averaged 59.5 quintals per hectare. Mean absolute error ranged from 23 qt/ha for the farmer's own estimate to 10.6 qt/ha for a randomly placed octant. Three diagonal quadrants gave 16.1 qt/ha against 19.4 qt/ha for a single quadrant placed at the center (Kosmowski et al., 2021). Placing the sample at random improved accuracy more than multiplying quadrants in fixed positions.

Split the plot into zones that differ by soil, slope, variety or planting age, take at least one random sample inside each zone, and weight each zone by its area. Record where each sample was taken so the same design can be repeated on the next pass.

Field procedure

Before measuring, choose a fixed unit (kg, boxes or quintals) and have a scale; if boxes are used, document the assumed weight per box. Keep prior results for the same crop, plot and season when available.

Map the productive area. Subtract paths, headlands, gaps and unplanted sections.
Count the stand. Check several sections for gaps, replants and dead plants.
Take the samples the design calls for. Weigh the harvestable product from each sampled plant or unit and calculate the average.
Scale and discount. Multiply the average by standing density and productive area, then apply the expected-loss factor.
Record the result. Date the estimate and retain its area, density, sample method, units and loss assumption. An estimate at fruit set is not comparable with one made two weeks before harvest.

From sample to plot: scaling counts to hectares

A sample gives a weight per sampled unit; the estimate needs it per hectare and then per plot. That conversion is where most errors creep in.

By area. A 4 × 4 m quadrant is 16 m². If it yields 9.6 kg, that is 0.6 kg/m² and 6,000 kg/ha across the 10,000 m² in a hectare.
By row. Divide the weight by the meters of row sampled and multiply by 10,000 ÷ row spacing in meters; at 0.8 m spacing that is 12,500 meters of row per hectare.

For a farm total, add the plot totals rather than averaging their per-hectare yields. Three hectares at 6,000 kg/ha plus one at 10,000 kg/ha is 28,000 kg over 4 ha, or 7,000 kg/ha, not the 8,000 kg/ha a simple average would give.

Error, bias and reconciling with the recorded harvest

After harvest, calculate:

Error % = (actual harvest − estimated yield) ÷ estimated yield × 100

A negative result means the estimate was too high. Compare estimates and actuals only within the same crop, plot and season; a greenhouse tomato cycle is not a benchmark for coffee.

Cycle	Estimated	Actual	Error
1	18,000 kg	15,900 kg	−11.7%
2	16,000 kg	17,000 kg	+6.3%
3	20,000 kg	18,600 kg	−7.0%

Bias is the average signed error: (−11.7 + 6.3 − 7.0) ÷ 3 = −4.1%. A persistent sign points to a systematic issue in sampling or the loss factor. Mean absolute error ignores signs: (11.7 + 6.3 + 7.0) ÷ 3 = 8.3%. It shows the uncertainty to allow when committing volume. No system removes that error: the Global Strategy methodological review reports that the US corn forecast, an expensive and mature program, carries a root mean square error of about 6.3 percent four months before harvest, falling to 3 percent two months out. The point of reconciling is not to be right, but to hold a verifiable track record between forecast and final harvest that can correct the method.

Limits of the method and when to re-estimate

Representative sampling cannot remove every limitation: uneven stands or sampling too early can invalidate the assumptions. Volume also does not predict grade, size or price. Do not compare fresh kilograms, 20 kg boxes and quintals without a fixed conversion, and do not mix moisture or quality bases.

That same review puts it simply: the confidence band around a forecast is wider the further it sits from harvest. So re-estimate after establishment, at flowering or fruit set, and one to three weeks before harvest. Repeat it after drought, flooding, hail, a pest outbreak or an irrigation failure. Treat each revision as a new measurement and keep field sheets in your own records.

When an estimate changes, note what changed in the stand, sample or loss factor, and whether the revision reflects a scheduled observation or an event. That way a later error review can separate a weak sampling method from conditions that genuinely changed after the original measurement.

Harvest estimates in Aragro

Aragro's Estimados de cosecha stores the result of the field procedure for a crop cycle alongside the harvest you record. Enter the estimated yield per unit of area (such as 9,000 kg/ha) and the cycle's effective area; an optional unit conversion can reconcile an estimate in one unit with harvest in another. Aragro multiplies yield per area by effective area to show the estimated total beside recorded harvest. Each cycle has one current estimate, while dated field sheets stay in your records. Aragro does not create or revise a field estimate from plant samples, weather, imagery or activity history: sampling, standing counts and expected loss remain field decisions.

Recorded harvest progress makes it possible to compare completed work with the current estimate.

Enter the current estimate and effective area in the crop cycle, then record harvests against it. Estimados de cosecha is a Spanish product guide. See the product overview, plans and pricing, and how to run farm payroll for the connected planning context; availability depends on plan and permissions.

How to run farm payroll

2026-07-20T00:00:00Z

Farm payroll calculates and pays what workers earned for a period: time or completed work, applicable bonuses and lawful deductions. It also establishes the farm's labor cost. Because it is recurring and regulated, record the work as it happens rather than rebuilding it from memory at month-end.

This is general guidance, not legal, tax or accounting advice. Payroll requirements vary by country and change over time; confirm current local rules with the labor authority or an accountant.

Pay models, formulas and example

A farm may combine three pay models: day rate (jornal) for each day worked, piece rate (destajo) for each agreed unit completed, and a monthly salary for a fixed period, usually for permanent staff. Overtime, premiums and contractual or statutory bonuses may apply to any model.

Gross pay = units worked × rate + bonuses

Net pay = gross pay − deductions

For a day rate, units are days; for piece rate, they are boxes picked, rows weeded or other agreed units; for salary, they are the pay period. What comes off the worker's wage and what the farm pays on top of it are separated further down.

All three models share a legal floor. The ILO defines a minimum wage as "the minimum amount of remuneration that an employer is required to pay wage earners for the work performed during a given period, which cannot be reduced by collective agreement or an individual contract" (ILO, How to define a minimum wage?). Piece rate does not remove that floor: the ILO notes that in various countries "the legislation stipulates that pieceworkers' wages may not be lower than the applicable minimum wage", and the employer covers the gap (ILO, Piece rate pay). Setting the rate per unit is covered in piece-rate pay in agriculture.

Line	Value
Days worked	24
Daily rate	100
Bonuses	250
Gross pay	24 × 100 + 250 = 2,650
Worker deductions	120
Net pay (what the worker receives)	2,650 − 120 = 2,530
Employer contributions	300
Total cost to the farm	2,650 + 300 = 2,950

The deduction and contribution figures are illustrative: local law sets their rates. For piece rate, replace days worked × daily rate with units completed × agreed price per unit.

What data each run needs

A payroll run is only as accurate as the records feeding it:

Input	Source	What it drives
Worker classification and terms	Registration or contract	Which rules and contributions apply
Pay model and agreed rate	Contract or task agreement	Gross pay, and a reproducible calculation
Days worked and absences	Daily attendance	Day wages and absence deductions
Accepted units per worker	Count at the work point	Piece-rate pay
Overtime and premiums	Working-time record	Overtime paid at the local premium
Field and activity	Work order	Labor cost landing on the right field

An input that does not exist on the day of work gets rebuilt from memory on payroll day, and that is where disputes start.

A checkable payroll workflow

Set terms before work starts. Record each worker's classification, pay model and agreed rate. Agree piece rates contemporaneously, not after the output is known.
Record the work when it happens. Capture day wages, accepted units, absences and overtime at the work point, linked to the field and activity.
Close and calculate the period. Apply rates, bonuses and applicable overtime, then separate worker deductions from employer contributions.
Review before payment. Check new workers, terminations, unusual totals, manual adjustments and the evidence behind them.
Pay, give a clear statement and retain records. Keep them for the locally required period: they settle a dispute and show the real cost of a crew against the harvest estimate.

Have the worker and supervisor resolve a questioned tally or rate while the work is fresh. A payroll run is not the place to change a rate or an agreed deduction without notice.

Worker deductions and employer contributions

Gross pay splits into three destinations a payslip should never blur:

What the worker receives: net pay, in cash or by transfer.
What the employer withholds from the wage: the worker's social-security share, tax withholding where it applies, agreed advances and loans, and other authorized deductions.
What the farm pays on top of the wage: the employer social-security quota, contributions to funds or institutes, and payroll taxes.

Only the second group reduces net pay: shifting an employer charge onto the worker underpays the wage. The Protection of Wages Convention, 1949 (ILO, No. 95) permits deductions "only under conditions and to the extent prescribed by national laws or regulations or fixed by collective agreement or arbitration award" (article 8), and asks employers to tell workers those conditions and give them, at each payment, "the particulars of their wages for the pay period concerned" (article 14). The practical rule: no deduction should ever appear for the first time on a payslip.

From net pay to the real cost of labor

Labor cost is what the employer spends to employ work, not what the worker takes home.

Labor cost = gross pay + employer contributions + benefit accruals + other employer charges

The international classification of labour cost, adopted by the Eleventh International Conference of Labour Statisticians in 1966, groups that spending into direct wages, remuneration for time not worked (vacation, holidays, severance), bonuses, payments in kind, housing, employers' social security expenditure, training, welfare services and taxes regarded as labour cost (ILO, Resolution concerning statistics of labour cost). That list doubles as an inventory of the lines farms forget when they budget a crew.

For planning, also split the fixed payroll from the variable one. FAO's farm-management extension guide treats payment for permanent labour as a fixed cost, and labour hired for tasks such as weeding and harvesting as a variable cost that rises with the area worked and with the yield (FAO, Economics for market-oriented farming, 2008). The full cost, not net pay, is what you allocate to the field: how it accumulates is covered in how to calculate production cost per field.

Local rules to verify

Before the first run, verify current local rules for:

worker classification
minimum wage
working-time and overtime rules
statutory bonuses
social-security registration, rates and bases
income-tax withholding
payslip and payment requirements
record retention
termination, seasonal-worker and migrant-worker rules

Keep the confirmed rules with the rates you use, so a legal change can be traced to the affected payroll line. Operating in Guatemala? See how to run farm payroll in Guatemala for the 2026 figures.

Mistakes that break farm payroll

Mistake	Consequence	Fix
Rebuilding attendance at month-end	Inaccurate pay and disputes with no evidence	Record attendance and units the same day
Treating net pay as labor cost	Short budgets and unreal margins per field	Add employer contributions and accruals
Charging an employer cost to the worker	An underpaid wage and legal exposure	Keep deductions and contributions on separate lines
Closing the period with work orders still open	Costs landing in the wrong cycle	Complete the operational record before calculating

Payroll in Aragro

Aragro connects employee records to payroll calculation in the web app. Employees hold positions, wage terms and salary structures. Activities and work orders record who worked on what, and activity payments can be configured for piecework. From completed work records and configured salary structures, Payroll calculates a run for you to review and complete. Once work orders and payroll are complete, labor cost reaches the linked cost centers, fields and activities.

Configured daily and piecework rates make each payroll run reproducible.

Aragro calculates and documents; it does not execute the payment or comply on your behalf: it does not move money, does not file with social-security or tax authorities, and does not guarantee statutory compliance. You can preview and print a payslip, but confirm that delivery and archiving meet local requirements. Attendance by day and activity and the salary book come with the Cultivo plan; basic payroll and piecework wages with Cosecha; advanced payroll with statutory benefits is a conversation with sales.

Configure positions, wage terms and salary structures, then record work against fields and activities. Planilla and Empleados are Spanish product guides. See the product overview and plans and pricing for availability.

How to run farm payroll in Guatemala

2026-07-22T00:00:00Z

Farm payroll in Guatemala starts from recorded work, day wages, piecework or monthly salaries, and applies the current agricultural minimum wage, the statutory incentive bonus, two annual bonuses (Bono 14 and aguinaldo) and IGSS social-security contributions. This guide collects the 2026 figures with their legal sources; how to run farm payroll covers the general recording and settlement workflow.

Three institutions govern those figures. The Ministry of Labor and Social Welfare (MINTRAB) sets the minimum wage by government accord and authorizes the wage book. The Guatemalan Social Security Institute (IGSS) registers employers, receives the monthly payroll filing and collects social-security contributions, including the amounts it passes on to IRTRA and INTECAP. The Tax Administration Superintendency (SAT) administers income-tax (ISR) withholding on salary.

This is general guidance with figures current at publication, not legal, tax or accounting advice. Rules change, including the minimum wage each year; confirm every figure with the Ministry of Labor, IGSS or a Guatemalan accountant before applying it.

The 2026 agricultural minimum wage

The government published Acuerdo Gubernativo 256-2025 on December 22, 2025; it took effect on January 1, 2026 and sets the minimum wage by activity and economic circumscription:

Agricultural activity, 2026	Daily	Monthly
Economic Circumscription 1 (Guatemala department)	Q124.64	Q3,791.20
Economic Circumscription 2 (rest of the country)	Q119.21	Q3,625.89

The circumscription follows where the work happens, not where the company registers. These amounts exclude the incentive bonus, which employers pay on top. The government usually publishes the next calendar year's accord in December, effective January 1: check for it before budgeting payroll.

The incentive bonus: Q250 per month

Every private-sector worker receives a Q250 monthly incentive bonus alongside the salary. Decreto 78-89 created the bonus and Decreto 37-2001, article 1, fixed the amount.

Article 2 of Decreto 78-89 keeps it out of almost every calculation base: the incentive bonus carries no employer or worker contributions to IGSS, IRTRA or INTECAP, and it does not raise the salary used for severance or aguinaldo, except when computing the seventh day. Record it as its own payslip line, separate from ordinary salary, so every base stays visible and auditable.

Bono 14 and aguinaldo: two extra salaries a year

The two annual statutory bonuses each equal 100% of one month's ordinary salary:

Bonus	Legal basis	Calculation	Payment
Bono 14	Decreto 42-92	Average ordinary salary of the year ending in June	First half of July
Aguinaldo	Decreto 76-78	One month's ordinary salary for a year of continuous service, proportional if shorter	50% in early December, 50% in late January (or 100% in December)

Employers pay both proportionally when the employment relationship runs shorter than a year. Aguinaldo carries no IGSS, IRTRA or INTECAP contributions (Decreto 76-78, article 15), and the same exemption extends to Bono 14 through the supplementary-application rule in Decreto 42-92, article 5; confirm the treatment with IGSS. For field workers on intermittent contracts, the aguinaldo law sets its own threshold: 150 worked days or tasks in the year earn the benefit (Decreto 76-78, article 10).

IGSS, IRTRA and INTECAP

Ordinary salary carries four contributions, and only one of them comes out of the worker's pay:

Contribution	Rate	Who pays it
IGSS worker quota	4.83%	The farm withholds it from each payment
IGSS employer quota	10.67%	The farm, with no deduction from the worker
IRTRA (Decreto 1528, article 12)	1%	The farm
INTECAP (Decreto 17-72, article 28)	up to 1%	The farm

Employers pay IRTRA and INTECAP together with the employer quota, and IGSS passes each amount on to the corresponding institute. Two agricultural details matter here. The INTECAP organic law applies the rate only to permanent workers and exempts agricultural businesses with fewer than 10 permanent workers (article 28, paragraph 2). And since January 2023, Acuerdo 1529 of the IGSS board requires employer registration from the first worker, not from three as before. Confirm current rates, bases and coverage with IGSS before configuring payroll.

Income-tax (ISR) withholding follows SAT rules and depends on each worker's annual income. Decreto 13-2026, approved in April 2026, created an extraordinary deduction of Q3,024 that applies to fiscal year 2026 only; the new deduction equal to 12 non-agricultural monthly minimum wages including the incentive bonus takes effect on January 1, 2027. Confirm current values with SAT before calculating any withholding.

Labor-code rules that shape farm payroll

The labor code (Decreto 1441) adds rules payroll must reflect:

Working time: an agricultural worker's ordinary daytime week runs 48 effective hours (article 116), except on farms employing 500 or more workers, where the general 45-hour rule applies; overtime carries at least a 50% premium (article 121), and the daily total may not exceed 12 hours (article 122).
The seventh day: the weekly rest day earns pay, and workers on piece rate also earn an extra one sixth of the week's total (article 126). Article 88 recognizes piecework as payment by unit of work; piece-rate pay in agriculture covers how to set rates and record units.
Records and frequency: from 3 to 9 permanent workers, a farm keeps payroll sheets following IGSS models; from 10 onward, a wage book authorized by the Ministry of Labor (article 102). Manual workers collect their pay at least every fortnight (article 92).
Vacations: 15 paid working days after each continuous year; a worker whose contract does not require full hours or all days must reach at least 150 days worked in the year, and an agricultural or livestock business calculates the pay on the average of the last 3 months (articles 130, 131 and 134).

Worked example: one month in quetzales

A permanent agricultural worker in CE2, full month, no overtime and no ISR withholding, on a farm with 10 or more permanent workers:

Line	Calculation	Value
Ordinary monthly salary	CE2 agricultural minimum	Q3,625.89
Incentive bonus	Decreto 78-89	Q250.00
Total earned	3,625.89 + 250	Q3,875.89
IGSS worker quota (4.83%)	3,625.89 × 0.0483	−Q175.13
Net pay to the worker	3,875.89 − 175.13	Q3,700.76
IGSS employer quota (10.67%)	3,625.89 × 0.1067	Q386.88
IRTRA (1%) and INTECAP (1%)	3,625.89 × 0.02	Q72.52
Bono 14 accrual (1/12)	3,625.89 ÷ 12	Q302.16
Aguinaldo accrual (1/12)	3,625.89 ÷ 12	Q302.16
Monthly cost to the farm	3,875.89 + 386.88 + 72.52 + 604.32	Q4,939.61

The example makes one point: the farm spends 27% more than the total-earned line shows. The annual bonuses account for Q604.32 a month of that gap and the employer contributions for another Q459.40. Neither reaches the worker's pocket that month, yet both are real cost of the field where the work happened. The example omits overtime, vacations, severance and any collective agreement; the Bono 14 and aguinaldo accruals are an accounting practice to spread the cost, not a monthly payment to the worker. Verify rates and bases with IGSS and SAT before applying it.

How this works in Aragro

Aragro builds Guatemalan payroll from the daily record. Work orders capture day wages, piecework units and attendance by field and activity, at the rates agreed at the time. In salary structures you define your payroll's Guatemalan components, each with its formula and base: ordinary salary, the incentive bonus kept out of the contribution base, the IGSS worker-quota deduction, and the Bono 14 and aguinaldo accruals. The payroll run fills the structure's employees with completed work for the period, calculates every component and stays open for your review; closing it sends labor cost to the cost centers of the fields worked.

Aragro does not file with IGSS or SAT, does not pay workers, and does not guarantee legal compliance. It calculates and documents so your accountant can review and your own process can pay. You configure the legal figures (minimums, percentages) and update them when December brings the next year's accord. Payroll and piecework availability depends on the plan.

If you operate in Guatemala, see Aragro for Guatemala and plans and pricing, and validate your component configuration with your accountant before the first run.

How to calculate production cost per field

2026-07-22T00:00:00Z

Production cost per field is the sum of labor, inputs, machinery and allocated overhead assigned to one field over a crop cycle, reported three ways: absolute, per hectare and per unit produced. Without it, the farm knows its overall spending but not which field earns money and which loses it.

Which costs belong in production cost

A complete production cost includes everything the field consumed, not only what the farm paid in cash. The FAO Handbook on Agricultural Cost of Production Statistics starts from a simple principle: measure every cost, purchased or owner-supplied, and if production needs it, put a value on it. That handbook calls farm-produced inputs and unpaid family work non-cash costs, and treats depreciation on owned machinery as a separate line. For managing a field, four categories are enough to start:

Labor: day wages, piece rates and salaries for work done on the field, at full employer cost, not just net pay. How to run farm payroll explains the difference.
Inputs: fertilizer, crop protection, seed and materials, priced at the warehouse cost of what the crew actually applied, not what the farm bought.
Machinery: machine hours on the field, priced at an hourly rate that covers fuel, operator and maintenance.
Allocated overhead: administration, security, shared irrigation and other services that belong to no single field.

The first three are direct costs: they attribute unambiguously to the field that consumed them. The fourth groups the indirect costs, which the FAO defines as costs that several production processes share and that no one product can claim unequivocally. Where each expense falls decides what you record directly and what you prorate. Labor tolerates a rough record least of all. Across the 1,283 coffee farms in the Costos de producción de café, Colombia 2024 study by the Acuerdo de Café, Bosque y Clima, harvesting alone accounted for 54% of cost per kilogram.

Formulas: per field, per hectare and per unit

Three figures answer three different questions:

Total field cost = labor + inputs + machinery + allocated overhead

Cost per hectare = total field cost ÷ field area

Cost per unit = total field cost ÷ units harvested

The total shows how much capital the field consumes. Cost per hectare is that total divided by the field's area: it measures investment intensity per unit of area and compares fields of different sizes. Cost per unit is the total divided by the units harvested, per kilogram, box or bag. That is the figure you set against the sale price, and it decides whether the cycle was profitable. Calculate all three per crop cycle, not per calendar year, so cycle-to-cycle comparison stays clean.

The two derived figures do not rank producing units the same way. In the Costos de producción de café, Colombia 2023 study, farms with more than 10 hectares in coffee spent COP 14,082,000 per hectare against COP 11,980,800 on farms under 5. They still produced more cheaply per kilogram: COP 8,590 versus COP 8,830. Read cost per hectare alone and you blame the wrong field, so the three figures belong together.

Worked example

A 2-hectare field over one full cycle:

Category	Cost
Labor (employer cost)	38,400
Inputs applied	21,600
Machinery (hours × hourly cost)	6,000
Allocated overhead	9,000
Total field cost	75,000
Area	2 ha
Cost per hectare	75,000 ÷ 2 = 37,500
Harvested output	15,000 kg
Cost per unit	75,000 ÷ 15,000 = 5.00/kg

At a sale price of 6.50/kg, the field's margin is 1.50/kg before selling costs. The same structure on another field producing at 7.20/kg shows immediately where the problem is, even when both "look fine" from the road. Cost per unit connects directly to the harvest estimate: an inflated estimate hides a higher real unit cost.

Cost centers: assigning each expense to its field

A cost center is the account where everything a field consumes accumulates; every productive field should have its own. The operating rule is to assign the cost when the work happens: the recorded task names the field, and the day wages, piece-rate units, applied inputs and machine hours travel with it. How to organize that daily record (work orders, progress and returns) is the subject of how to control field operations; here the outcome is what matters: every completed task leaves its cost in the right field's cost center.

Assigning at month-end from memory or from invoices does not work: invoices say what the farm bought, not where the crew applied it, and memory averages things out. The FAO handbook treats this as part of the method rather than an operational detail: allocating costs gets easier as a farm's recordkeeping practices improve. Cost per field is only as good as the daily record feeding it.

Splitting shared and indirect costs

Part of the cost never belongs to a single field: administration, irrigation serving three fields, a crew task that moved through several fields in one day. To split it, choose an allocation basis and keep it for the whole cycle:

By area: useful for stable general costs (administration, security). Each field takes its share of hectares.
By hours worked: useful for shared tasks; the field where the crew spent more hours absorbs more cost.
By progress or output: useful at harvest; the field that delivered more kilograms absorbs more of the shared task's cost.

No basis is "the correct one", and that is not a licence to improvise. The FAO states in its cost-of-production handbook that no "true" or "false" way to split joint costs exists. What the method always demands is two things: a uniform algorithm, and transparency about which one you used. What invalidates comparison is switching bases mid-cycle or leaving them undocumented. Note the chosen basis with the cycle's closing figures.

Common errors that distort the cost

Omitting employer cost: counting only workers' net pay understates labor.
Valuing inputs at the latest purchase price instead of the warehouse cost of what was applied.
Ignoring non-cash costs: family labor and farm-produced inputs make fields look "cheap" when they are not.
Mixing cycles: charging the new cycle for inputs the previous one consumed.
Comparing different units: fresh kilograms against dried bags, or different moisture bases, without a fixed conversion.
Changing categories between cycles: if one cycle includes overhead and the next does not, the "improvement" is arithmetic, not real.

How this works in Aragro

In Aragro each field links to a cost center, and cost accumulates from the operational record: completing a work order pushes its labor, inputs and machinery hours into the cost centers of the fields it touched, splitting them by hours, by progress or by harvested output, depending on the task type. Completed payroll adds employer-side labor cost to the same work orders, and inventory prices the warehouse issues. The Field report totals those three recorded categories, labor, inputs and machinery, per field and per unit of area, ready to compare against recorded harvest.

The field report separates labor, inputs and machinery, with total and per-hectare cost.

The Field report covers the recorded operating cost; the method's allocated overhead, administration and general services, does not enter that report, and its proration remains your step. Aragro also does not estimate costs for tasks that were never entered. Availability of cost centers, payroll and budgets depends on the plan.

Create one cost center per field and start recording tasks against them. See the product overview and plans and pricing for availability.

How to control field operations

2026-07-23T00:00:00Z

Controlling field operations means closing the loop between the plan and the work actually done: every task carries an owner, a crew, authorized inputs and an actual cost known when it closes, not months later. The instrument that holds that loop together is the work order.

Why farms lose control of field tasks

The pattern repeats on farms of every size: the supervisor hands out the day's tasks verbally in the morning, inputs leave the warehouse with a scribbled note or none, and nobody records how many people worked on which field. The consequences arrive in pieces: someone rebuilds payroll from memory, the warehouse never reconciles against what the crew applied, and cost per field, if anyone calculates it at all, arrives when no decision can change it.

The FAO handbook on agricultural cost of production statistics (2016) describes where that gap leads. When a farm does not record how much labor went into each task, labor cost no longer maps directly onto the tasks, and the farm has to spread it with allocation keys instead. Spreading it is estimating it. The problem is not lack of effort but lack of a unit of control: something connecting the plan, the execution and the cost of one same task.

The control cycle in six steps

Plan the task with a budget. Which activity, on which fields, in which date window, at what expected cost of labor, inputs and machinery.
Issue the work order. Turn the plan into a document with an owner: the task now exists, has a number, and someone answers for it.
Assign crew, machinery and inputs. The order names the workers and machines; the crew requests inputs from the warehouse against that order, with dose or quantity per field.
Execute and record the same day. Crew attendance, progress or piecework units per worker, machine hours and real consumption per field.
Return and close. Unused product goes back to the warehouse on the record; the order closes with actual quantities, not requested ones.
Approve and compare. The owner reviews the records, completes the task, and compares its actual cost against the budget from step 1.

Each step produces a record the next one needs; skipping one breaks a chain nobody can rebuild afterwards.

The work order: the unit of control

An agricultural work order is the document that authorizes a task before the crew starts it and records how the crew carried it out. A complete order contains: activity and category, field or fields, dates, an owner, assigned workers, machinery, requested inputs, and the progress units the crew will measure, such as rows, plants, boxes and hectares. Its lifecycle mirrors the real flow: it opens at planning, may take a scheduled date, moves to in progress once work starts and the crew requests inputs from the warehouse, and completes once the records close. That passage through states is what separates "we told them to do it" from "they did it, with these resources, at this cost".

That structure is exactly the point. A 2024 review of on-farm recordkeeping in the journal Precision Agriculture explains why. Free-form recordkeeping leaves data capture to whatever the worker happens to be thinking about, so something genuinely important may never come to mind and never reach the record. A document with fixed fields does not rely on anyone remembering.

The work order is not bureaucracy if it replaces papers that already exist: the supervisor's note, the warehouse slip and the attendance sheet become one thing when they live in the same document.

Inputs: the request-use-return cycle

The most expensive hole in field-operations control is usually the warehouse. The rule that closes it: the warehouse issues only against a specific task, and the crew returns what it does not use, on the record. The request starts on the work order with quantities per field; the issue deducts stock against that order; at closing, the surplus comes back with a return entry. Real consumption per field equals what left the warehouse minus what came back. Without this cycle, inventory "reconciles" only on physical-count day, and input cost per field stays an estimate.

That same record serves more than one purpose. The FAO good agricultural practices training manual (2022) asks farms to log every agrochemical application per crop: the product used, the reason for the application, the treatment location, the date, the rate, the method, the weather conditions and the operator's name. It also asks for a separate store record with product name, date and quantity. A properly filled work order produces almost all of those fields with no extra work.

Record what happened, not what was planned

The plan says 12 workers and 40 liters; the field says 9 workers, 34 liters and one field the crew did not finish. Control exists only when that second version reaches the record:

Resource	What the supervisor records in the field	What it enables at closing
Crew	Who attended, on which task and field, with their units when the task runs on piece rate	Labor cost per field and correct pay for the worker
Progress	Finished units per field	Knowing whether the task tracks the plan
Machinery	Hours per machine and per field	Machinery cost charged to the field that used it
Inputs	Real consumption per field after returns	Actual input cost instead of an estimate

Record at the work point, the same day: Friday's memory averages what Monday knew exactly. The same Precision Agriculture review puts it bluntly: data quality drops when nobody records in real time, and a logbook that lives in the office ends up depending on the workers' memory and motivation.

From closed task to actual cost

Every completed order produces a composite cost: labor at employer cost, inputs at warehouse cost and valued machinery hours. If the order touched several fields, it splits the cost on an explicit basis, such as hours, progress or output. The FAO cost handbook frames the measurement ideal in the same terms: record the time each employee spends on each specific farm activity, then multiply it by the wage rate in their contract. That is what lets a farm allocate labor cost across its activities and crops.

The sum of the cycle's closed tasks is the field's operating production cost, before allocated overhead; the full costing method is in how to calculate production cost per field. The plan-versus-actual comparison, task by task, is what teaches: the big difference almost always sits in two or three activities, not spread across all of them.

How this works in Aragro

Aragro's work orders implement this cycle with a state machine: an order opens, may take a scheduled date, and moves to in progress when work starts. Starting triggers the inventory request to the warehouse; at closing it passes through a brief completing state until completed, and a supervisor can revert a completed order when something went in wrong. Each order carries its crew with attendance and progress per field, its machines with hours, and its inputs per cost center, with the request-and-return cycle built in: the order cannot complete while inputs remain unresolved. On completion, Aragro distributes the actual cost across the fields worked by hours, progress or harvested output into their cost centers; crew payments flow to pre-payroll.

A completed work order brings together progress, crew, and actual labor, input, and machinery costs.

Recording remains field discipline: Aragro structures and calculates, but it does not invent data for the task nobody entered. Feature availability, including progress tracking, piecework, planning and budgets, depends on the plan.

Pick a single activity next week and control it end to end with one work order, from plan to cost. See the product overview and plans and pricing for availability.

Piece-rate pay in agriculture

2026-07-24T00:00:00Z

Piece-rate pay is wage payment for completed units of work, such as boxes picked, rows weeded or bags collected, instead of for time worked. Managed well, it aligns the worker's income with the task's progress; managed badly, it produces tally disputes, rates changed after the effort and quality sacrificed for speed.

What piece rate is and when to use it

Piece rate is pay per unit of work performed, in the ILO's definition, and the ILO lists agriculture among the sectors where it is common. Labor codes recognize it: Guatemala's labor code, for example, expressly allows pay "by piece, task, flat rate or piecework" (article 88). In farm practice it dominates wherever the unit is countable and individual pace matters: harvest, weeding by row, pruning by plant.

The practical rule: piece rate when you can count the unit and verify its quality at the work point; day wage when quality outweighs speed or the outcome does not depend on individual effort. Many farms combine both in the same week, and farm payroll must settle the two models together.

Research has measured what piece rate does to work pace. The University of California surveyed California grape growers about the 1990-1991 season and compared the two systems in pruning. In wine and raisin grapes, hourly-paid crews needed an average of 26 labor hours per acre; piece-rate crews needed 19, or 37% faster (Billikopf and Norton, California Agriculture 46(5), 1992). Pay method did not appear to affect the quality of the work for two thirds of the respondents, and the remaining third preferred the quality of hourly-paid work. That speed gain is not automatic, though: growers' most common objections to incentive pay include poor-quality work, difficulty setting standards and excessive record-keeping (UC ANR, Labor Management in Agriculture, "Incentive Pay" chapter). Farms that sustain piece rate over time control quality as well as speed, and that control starts with how you set the rate.

How to set the rate per unit

A defensible rate starts from the target daily income, not from habit:

Rate per unit = target daily wage ÷ units an average worker completes in a workday

With a target day wage of 120 and an average output of 80 boxes per day, the rate is 1.50 per box. Three decisions accompany the formula:

Measure average output under real conditions: the same crop yields differently with fruit load, slope and weather. A rate set on the best field punishes everyone else. Without a history to draw on, time the task yourself or pay a temporary crew an inflated rate purely to establish the standard. UC ANR warns that whoever will later do the work, or anyone with a stake in the result, must not run that trial.
Define the quality standard with the rate: decide what counts as an "accepted" box (ripeness, cleanliness, fill level) beforehand, not at delivery.
Check the legal floor: how the minimum wage applies to work paid by the unit is a local rule. The ILO describes three common approaches across national law. The piece rate may not fall below the applicable minimum wage, or the minimum is set against a production quota, or the law requires a fair wage for anyone paid by the unit. In Guatemala, for example, minimum-wage setting must expressly protect workers paid by piece or piecework (labor code, article 103). The risk is real: in the same vineyard survey, 8% of the growers paying piece rate had pay scales below the minimum wage, against 4% of those paying by the hour. Confirm minimums, paid rest days and premiums with the labor authority or an accountant.

Adjust the rate when conditions change, such as at the start or peak of harvest or for a difficult field, and agree on it before work starts. The rule cuts one way only: once you set the standard you may loosen it, never tighten it. UC ANR records the case of a grower who cut the rate after the crew earned more than he expected; he lost credibility, morale collapsed and many workers left. Changing the rate once you know the output destroys the trust that makes the model work.

Recording units without disputes

Piece rate is won or lost in the record. A workable tally meets four conditions:

At the work point: the checker counts, weighs or measures the units where the crew produces them, with the worker present.
Per worker and per task: each record names who, which activity, on which field and how many accepted units.
With a receipt: the worker gets proof of the day's tally, and both sides clear up differences the same day rather than at payout.
With the rate fixed in advance: the record stores the rate in force at the time of work, so the settlement stays reproducible even if the rate changes later.

This same record feeds two immediate outcomes: the worker's pay and the field's labor cost, covered in how to calculate production cost per field. Over a longer horizon it feeds a third: the output history you will set next season's rates from. UC ANR puts it plainly: keeping performance records establishes the base lines a farm needs for setting future standards, whether or not it pays an incentive.

From units to pay and to cost

The period's settlement gathers the daily records:

Gross pay for the period = Σ (accepted units × the rate in force for each task)

The locally applicable rules are then applied to that gross: mandatory bonuses, paid rest days, social-security deductions and whatever wage floors local law provides. In Guatemala, for example, a worker paid by unit of work receives an extra one sixth of the week's earnings for the weekly rest day (labor code, article 126). A worker can accumulate day wages on one task and piecework on another in the same week; the settlement adds them separately and presents them on one payslip.

For the farm, the same calculation at full employer cost is the labor cost that lands on the field and activity where the crew produced the units.

Benefits, risks and mitigations

Risk	Mitigation
Quality sacrificed for speed	Quality standard agreed in advance with the rate; rejections recorded and resolved with the worker the same day
Tally disputes	Counts accepted at the work point with a daily receipt
Rates perceived as arbitrary	Known rate formula; average output measured and communicated
Earnings below the legal minimum	Check at every settlement of the local minimum-wage rule that applies to piece rate
Pressure on slow or new workers	Training on a guaranteed day wage until the worker masters the quality standard, and only then a move to the piece-rate crew (practice documented by UC ANR)

How this works in Aragro

In Aragro, you configure piecework as per-activity payment rules: each rule sets the rate per unit tied to a metric (boxes, kilograms, rows) and can be segmented by position, farm or crop. On the work order, the supervisor records units per worker; Aragro calculates the pay (units × rate), surfaces it in the pre-payroll report for review, and settles it in payroll together with day wages and salaries. When the order and payroll complete, the cost lands in the field's cost center.

Daily and piecework payment rules for the same harvest activity.

Aragro records and calculates; it does not move money and does not by itself verify your country's legal minimums. That validation belongs to your payroll review. Piecework wages depend on the plan.

Define the unit, rate and quality standard for your next harvest task, and record units per worker from day one. See the product overview and plans and pricing for availability.