A trial season, in the order you run it
Design the protocol, walk the plots, close the season. Two surfaces share one dataset: the field app for assessments, the console for design, monitoring and export.
Design the trial
Set up in the console before anyone walks a plot.
Randomised layouts
Complete block, split plot, split-split or latin square, with reps and plot dimensions you set. The map is generated, not drawn.
Treatment list
Products, rates, timings and controls, held as codes so the field app can hide them during assessment.
Assessment schedule
Assessments pinned to dates or growth stages, each with its own scale, range and units.
Protocol reuse
Duplicate last season's trial and keep the schedule and scales. Randomisation regenerates for the new site.
Walk the plots
The tablet screens used between the gate and the last plot.
Plot map and walk order
Serpentine or row order, with assessed, current and remaining plots visible at a glance.
Blind assessment
Plot, rep and assessment only. Treatment codes stay hidden until the trial is unblinded.
Plot photos
Photos attach to the plot and the assessment, with the date and growth stage already on them.
Offline queue
No signal at the site is the normal case. Values queue on the device and sync on the way home.
Close the season
Monitoring, quality checks and the handover dataset.
Quality flags
Out-of-range values, missing plots and duplicate entries surface while you can still walk back to the plot.
Treatment means
Means and standard errors per assessment, so you can see the trial separating before the season ends.
Dataset export
CSV by plot and assessment for your stats package, or a PDF summary for the sponsor.
Audit trail
Who recorded what, when, and every unblinding event — the record an audit asks for.