Plant the block. Keep the count. Lose the signal.
The same offline map, with the planting kit inside: the heli plan, a live count of the trees left, pay plots and the tally card, all synced to the crew boss and the office. No login in the bush, no licence server, no spinner.
Watch the bars go.
A planting show runs on the blocks, the caches, the plot grid and the day's heli plan, and all of it is already on the phone. Nothing waits on a tower.
Tomorrow's plan, set tonight.
Every day on a planting show has its own plan. Step forward to tomorrow and the caches, the crews and the nets are tomorrow's, not today's. The crew boss sets it at camp, on the same phone they planted with.
The ground left picks the caches.
Each cache serves the ground nearest it. The server reworks what is still unplanted after every sync, so the boss sees 6.2 hectares behind Cache C against 5.6 behind Cache A, and stocks them in that order. Long-press the cache with the most ground left, drag it to the top of tomorrow's drop-off, and let go to save it.
Put the planters where the trees are.
Every tally card writes a row a day: the planter, the block, the species, the trees. Average them and you have what each planter actually puts in the ground. Four averaging 1,880 out-plant three averaging 2,140, so the biggest piece gets four and all three caches run out of ground at about the same time.
Finalise it, and the whole crew has it.
It goes out with the next sync, so every planter knows their cache and their nets before the first lift, and the pilot flies the order as saved. Drag it in the morning and the change comes back the same way.
Every track becomes planted ground.
Each planter's GNSS track is buffered by 2.7 m and laid over the block. Ground planted without a track is closed off with a last-line-planted edge. What's left uncovered is the remaining area, and remaining hectares times the block's density gives the trees left. The server reworks it on every sync, and every phone pulls the new layer.
One pay plot a hectare. Quality on the strip.
The plot grid is laid out before the crew arrives, one plot per hectare, numbered in a serpentine. Walk within 30 m and the app opens the planned plot. Satisfactory over planted rolls up per block on the strip: green at 93%, amber at 85%. Every plot records the account, fix and accuracy it was taken with.
The block’s number, while the block is still open.
Every plot anyone saves rolls into the block the moment it syncs: satisfactory over planted, across every plot the crew has done, not just yours. The strip sits on the map and changes colour as the number moves — green at 93, amber at 85, red below. PU12-04 went amber on the second plot and came back on the eighth. Nobody had to finish the block to find that out.
The block assessment writes itself.
Plots done, trees in plot, satisfactory, faults, and the faults split by Schedule B code. It is the same addition the strip is already doing, laid out as the assessment, with the block, the species, the area and the dates taken from the bundle. You check it. You don’t type it.
And the master sheet keeps up on its own.
The season’s workbook gets the block’s row rewritten each time the plots come in: plots done, trees in plot, satisfactory, quality, and the time it last changed. Nobody re-keys a quality number off a paper card, which is where quality numbers go wrong. The season total moves with it, so a block sliding is visible from the office the same day.
Lock the glass. Keep tracking.
Rain on a capacitive screen types for you. Touch goes dead, Home and Recents do nothing, and the screen stays on, while the GNSS keeps logging the planter's track.
The tally card, one bag-up at a time.
Start a bag-up, count boxes or bundles, end it. Trees per bundle is sticky, so the next bag-up is two taps. Bag-ups counted some other way go in as totals by block and species. Every card syncs, so the crew boss has it without asking.
Everyone's data on every phone. The paperwork fills itself.
With no cell coverage, phones on the same block pass tallies, plots and tracks to each other over Bluetooth, so the crew boss has the whole day before anyone leaves. At the first bar of signal it goes to the office: management sees the same numbers, and the daily report is already filled in.
One crew, one block, your own geodatabase.
We publish your blocks and caches from your gdb, lay out the pay-plot grid, set roles for the crew, and plant a day with you, paperwork included. If it doesn't beat what you have, you owe us nothing.
Book a pilot