Timber chain of custody
The register your buyer and your auditor will accept — and it works where there is no signal.
Crews record every tree, log and load on devices that work without signal. The office gets one register that adds up: signed by whoever entered each record, and ready for the forestry office, your buyer and your auditor.
- Works offline in the forest
- History that is never overwritten
- Free seats for your auditor
- ForestStanding
- ForestFelled
- LandingBucked
- TruckOn a truck
- MillAt the saw
Try it
The device and the office, live in your browser
Fell a tree on the device, buck it, load the truck, and watch the panel see it. Made-up data that never leaves your browser.
Made-up data, in your browser only. Nothing is sent anywhere, and a reload starts over.
The interactive demo needs JavaScript. Here are the same screens, taken from the product:
How it works
Each record is made where the work happens, and keeps who made it, on which device, and when.
-
1Forest
Find the tree
Type the number from the stamp. The tree’s page says what is done and what comes next.
-
2Forest
Fell and buck
A photo of the stamp and the location with the felling, then each log’s length and diameter. The volume adds up as you type.
-
3Truck and yard
Load and receive
Logs go on a load with the driver and the plate. The yard checks each load in, and a load received differently is flagged.
-
4Office
Close the lot
One page sets the office’s estimate beside what was recorded, shipped, received and sawn.
Paper and spreadsheets, or one register
Most operations still run on notebooks, spreadsheets and photos in a chat. The losses are real, and nobody sees them until the numbers fail to add up.
| What happens | On paper | With Tomruq |
|---|---|---|
| A tree is felled but never written down | Found at the end of the lot, if at all | Every tree on the office’s list has a status, so the gap shows |
| A diameter is keyed wrong | Copied into the next sheet, and the next | Typed once; a correction is kept beside the original |
| A log leaves the landing and never arrives | Nobody notices until the count fails | The yard checks each load in; a difference is flagged |
| No signal in the forest | Notes in a notebook, typed up later | Recorded on the device, sent when there is signal |
| The auditor asks who recorded what | A shoebox of notes and chat photos | Each record names the account, the device and the time |
| A buyer asks where the timber was harvested | Searched for in notebooks | Each felling carries its location and a photo |
| Closing the lot | Days of matching tallies | One page: estimate, recorded, shipped, received |
The proof
One page that closes the lot
The forestry office’s estimate beside what was recorded, shipped, received and sawn, with the trees that need a second look.
- Utilization against the estimate, per tree and per lot
- Loads received differently, and codes nobody accounted for
- Recovery at the saw, per log
- Exported as a workbook for the office or your buyer
Lot reconciliation
Example lot
| Measure | Volume |
|---|---|
| Forestry office estimate 1 204 trees on the tree list | 1 850.000 m³ |
| Recorded at felling and bucking Utilization 92.6% | 1 712.480 m³ |
| Shipped 31 loads | 1 698.205 m³ |
| Received at the yard 1 load received differently | 1 694.940 m³ |
| Into the saw 2 210 logs | 1 650.300 m³ |
| Sawn Recovery 61.7% | 1 018.700 m³ |
Flagged for a second look
- Low utilization 7
- Codes not accounted for 2
- Loads received differently 1
Illustrative figures from a synthetic lot.
Offline first
Works where there is no signal
Every record is saved on the device first and sent when there is a connection, minutes or days later. Two devices that worked on the same lot offline are merged without losing either one’s work.
- Saving never waits for a connection
- Records, photos and the tree list are kept encrypted on the device
- An outage on our side does not stop your crew
For everyone who handles the timber
-
Owners
What each lot produced against the estimate, and where material went missing, without waiting for the month’s end.
-
Managers
Import the tree list, set up crews and devices, fix what needs fixing, export what the office asks for.
-
Crews
Large targets, a number pad and few steps, in English or Turkish. A look for bright sunlight.
-
Auditors
A free read-only seat with the full history: who recorded what, when, on which device.
Questions
Does it work without signal?
Yes. Everything is saved on the device first and sent when there is a connection, minutes or days later. Nothing waits for the network.
Which devices does the app run on?
Android, and iOS through Apple’s TestFlight. The console runs in a browser, on a computer or a device.
Can we bring the forestry office’s tree list?
Yes, as CSV, Excel or JSON, in whatever shape it comes. For a pilot we do the first import for you.
Who owns the data?
You do. An owner exports the lot workbooks and downloads the organization’s complete archive from the console whenever they like, without asking us.
Where is the data kept?
The service and its database run in Frankfurt, Germany. Photos, files and backups are stored in the EU.
What does a pilot cost?
Nothing. One lot for 60 days from its first felling; we import your tree list and train the crew at the landing.
Is the demo the real app?
It is a recreation of the device app and the console that runs in your browser, with the product’s own words and made-up data. Nothing you do there is sent anywhere.
Start with one lot
A free pilot covers one lot for 60 days from its first felling. We import your tree list, train the crew at the landing, and finish with the reconciliation page for that lot.