Use case
A tree register a facilities
manager can actually keep up.
A university, a large private estate, an HOA, or a business park usually has one person responsible for the trees on top of a dozen other duties — not a dedicated arborist team. LogLog is built to be simple enough for that one person, or a hired consultant they bring in once, to maintain a credible tree register without a GIS degree.
Why this comes up
A sustainability or biodiversity initiative asks the facilities office "how many trees do we actually have, and what condition are they in" — and nobody has a good answer. Or an insurance audit wants documentation that trees near buildings and walkways have been inspected. Or a storm drops a limb near a dorm and the question becomes whether that tree was ever assessed.
Load the campus or estate site plan — a facilities map, a plot plan, whatever exists — into LogLog and walk the grounds pinning each tree as you go. Species, condition, and a basic risk note per tree is enough to answer "do we know what we have" the next time someone asks, without hiring a survey firm for a full engagement.
Simple enough for non-specialist staff
The mobile editor uses large tap targets and plain labels — species, DBH, condition, a photo — so a facilities staffer or a student volunteer helping with a sustainability audit can record a tree correctly without arborist training on the app itself. It won't teach anyone how to assess a tree, but it won't get in the way of someone who already knows how, either.
Credible enough for insurance and legal use
A dated, exportable record with condition and photo evidence is exactly what an insurance audit or a liability question after an incident actually needs — proof a tree was inspected, when, and what was observed, rather than institutional memory.
Fits a facilities budget line, not a procurement cycle
Estate and campus tree work usually gets a small, one-off or annual budget line inside facilities — not a dedicated software procurement process. LogLog's free tier covers a single person maintaining the register with no per-tree or per-project cost; a small team account works if two or three people share the grounds between them and need to coordinate through sync.
Handing it to a consultant later, cleanly
If facilities staff build the initial register and later bring in a consulting arborist for a full risk assessment, the consultant can open the same project and add risk fields to existing tree records rather than starting a duplicate survey from nothing. The species, DBH, and condition already recorded carry forward.
A living record, not a one-time snapshot
Because the register lives in one project rather than a document that gets emailed around and forked into copies, updating a tree's condition after a storm or an annual walkthrough keeps one authoritative version current instead of leaving three out-of-sync spreadsheets in different people's inboxes.
The old way
A spreadsheet someone built years ago, half-maintained, with no photos and no record of when a tree was last actually looked at. Nobody's sure it's current.
With LogLog
A dated register with photos, tied to the site plan, that anyone can walk and update without special training on the tool itself.
Re-walk the grounds each season, not just once
A tree register is only useful if it stays current. Re-opening the same project each season or each year to update condition notes and add any new hazard photos keeps the record meaningful instead of freezing it at whatever state it was in the year it was first built. Because the export is a clean spreadsheet each time, comparing this year's condition column against last year's is a five-minute exercise, not a data-archaeology project.
See what a basic record captures on tree data, and how a shared account works for two or three people on team accounts. Bringing in a consultant for a one-time survey? See consulting arborists.
A photo beats a memory when an incident happens
If a limb comes down near a walkway, the question that follows is almost always "when was this tree last checked, and what did it look like then." A dated photo attached to that specific tree's record answers that question directly, instead of relying on whoever inspected it last recalling the details from memory months later.
Know what trees you have.
Free forever for one person maintaining the register. No procurement process needed.