Questions we get asked

Yes, and this is the part people test first. Every entry saves to a queue on the phone the moment you tap save, photos included. You can assess an entire site in flight mode. When you drive back into range the queue empties into your SharePoint site by itself, and the project list shows you what has gone and what is still waiting.

As accurate as the phone in your hand, which under dense canopy usually means a few metres rather than a few centimetres. It is good enough to tell four trees apart on a plan and to prove where a photo was taken. It is not survey grade and we will not pretend otherwise. If you need survey accuracy you should be picking up coordinates with survey equipment, and TIMBR will happily sit alongside that.

In your own Microsoft 365 tenant, as SharePoint lists and files. There is no TIMBR database holding your projects. Your permissions, retention rules and backups apply to it exactly the way they apply to everything else you keep in SharePoint.

Nothing happens to it. It is already in your tenant in standard formats, so you keep every assessment, every photo and every report right where they sit. There is no export to request, no migration project and nothing for us to hold onto.

Yes. It shows the reference Notional Root Zone and Structural Root Zone worked out from the trunk diameter measurements you enter, using the method in AS 4970:2025. If you learned this standard before the 2025 revision, the NRZ is the figure you knew as the TPZ.

They are labelled as reference figures on purpose. The app does arithmetic, it does not do professional judgement. Under the 2025 standard the Tree Protection Zone is the area actually protected on site, which the project arborist sets.

Yes. Where a tree forks below 1.4 m you enter each stem separately and the app combines them as the square root of the sum of the squares, which is what the standard requires. Adding the diameters together, which is the intuitive thing to do, substantially overstates the zone.

Yes. TIMBR Field signs in with your Microsoft 365 accounts and writes into your SharePoint site. If your consultancy already runs on Microsoft 365, and most do, setup takes minutes and your IT people have nothing new to assess. If you are not on Microsoft 365 then this is not the right tool for you yet.

Yes. Because the records are SharePoint lists you can open them in Excel whenever you like. TIMBR Hub and the QGIS plugin read the same data for plans and reports. If your drafting still happens in a CAD package you are happy with, keep using it. We are trying to fix the front half of the job, not force you to replace the back half.

It runs on iOS and Android, so yes, on the phone you already carry. There is no proprietary hardware and nothing to buy.

Pricing is not settled while we are in private beta, and we would rather say that than publish a number we then change. Consultancies in the beta will see pricing before anything is ever charged, and will keep beta pricing for the first twelve months after launch. It will be in Australian dollars.

The beta is capped at ten consultancies and there are five places left. You get help setting it up against your own tenant, a walk through with an arborist rather than a support script, and a direct line to the person writing the code. In return we want to hear what is broken and what is missing.

We keep the number low because the onboarding is done personally, not because we are pretending to be exclusive. If that sounds like more involvement than you want right now, say so in the form and we will tell you when it opens up properly instead.