LogLog vs. clipboard,
Excel, and camera roll.

Here's what a 60-tree residential survey looks like with paper and a spreadsheet. You print the site plan at the office — assuming you have one, and it's the right revision. On site, you walk the property, find each tree, and mark an X on the printout with a number next to it. You write species, DBH, condition, and notes on a second sheet, or in the margins if there's room. You take three or four photos per tree, because you're not sure which angle the report will need.

Back at the office, you retype everything. Fifty, sixty trees, each one typed from your own handwriting — which was written in gloves, in the rain, or balanced on a clipboard against your knee. Then you go through the camera roll and try to match photos to tree numbers. Tree #23 and tree #31 both got photographed near a similar-looking fence, and it's been three days.

Then someone has to redraw the plan, digitally or by hand, so the client gets something legible instead of your field markup. For a small job this is an evening. For a full-time survey practice, it's the difference between billing for site time and losing margin to unpaid office time.

Load the same PDF site plan into LogLog before you leave the office — any PDF, any scale, multi-page if the drawing has more than one sheet. On site, you tap the plan where the tree is. That tap drops a numbered pin and opens the record for that tree: species (autocompleted against roughly 120 common and botanical names), DBH in cm, ownership, a six-value condition rating, action, and whatever else your practice tracks — preservation category, crown spread, risk fields, heritage flag. Photos attach directly to that tree's record. Not a camera roll. That tree's folder.

No signal required — the app runs on Dexie and OPFS storage on the device itself and doesn't need a connection to save a single field. When you're done, you export. One ZIP: a spreadsheet (both CSV and XLSX), an annotated copy of the site plan with the same pins baked onto it, every photo named and folder-sorted by tree number, a one-page PDF summary, and a manifest listing what's inside. Nothing to retype. Nothing to match up later.

It doesn't replace judgment — you still decide the condition rating, still write the notes that matter. It just removes the second pass where you re-enter what you already recorded once.

For a five-tree job you're walking in twenty minutes, a printed plan and a pen genuinely might be faster than opening any app — there's no argument to be made against zero setup time. And if you don't have a digital site plan at all, LogLog needs a PDF to annotate; it's not going to help you if the client only gave you a hand-drawn sketch on a napkin. In that case, the spreadsheet method is still the right call for that one job.