LRL Associates · FieldLog

Less time
wrangling files.
More time on site.

Field documentation that doesn't fight you back. Photos stay where you put them. Signatures land where you need them. Reports write themselves.

Stakeholder briefing

1

Sound familiar?

Field paperwork shouldn't take longer than the field work.

"Where did Tuesday's photos go? They were on Sam's phone." — PM, Friday afternoon
"I've emailed this PDF to the client three times this week." — Office admin
"The Dropbox link expired before they downloaded it." — Designer
"Compiling the weekly summary takes my whole Friday morning." — Project coordinator
"Did the inspector show up Tuesday? I have no proof either way." — Owner's rep
"When did Bob actually approve this? It's not in my inbox." — GC, mid-dispute
"The form got rained on. We're guessing at half the readings." — Field tech
"Three apps, one folder server, two email threads. For one site." — New hire, week one
2

What FieldLog gives back

One place for what happens on site.
One person in control. No more chasing.

📷

Every photo, in the project folder

Every image, every voice note, every plan pin — saved with the project, the date, the person who took it. Findable in seconds.

✍️

Multi-party signatures, no chasing

Send a link. They sign on their phone. You get the signed file back, automatically, with a record that it really was them.

📄

PDF reports, generated automatically

The PDF, the archive, the email to the client — all generated from the submission, the same way every time. No Friday-morning ritual.

🔍

Tamper-proof audit trail

Who did what, when. Permanent. Sortable. There when warranty calls or somebody disputes a date.

3

Photos that don't go missing

The Tuesday-afternoon photo hunt. Solved.

Today With FieldLog
On the inspector's phone — until they leave. Saved with the submission, automatically.
In a thread of text messages. Filed by project, date, and inspector.
On a memory card someone took home. On your own server — not a vendor's.
Maybe in last month's Dropbox folder. Searchable from the office in seconds.
4

Plan-and-pin photo requests

Tell the field exactly what to photograph.

You know the photos you need from the GC tomorrow morning. They shouldn't have to guess. Drop pins on the plan, send one link, every pin comes back fulfilled — labeled, timestamped, and dropped into the project folder, in order.

Real example

Concrete pour, Tower 2 Level 14

The job: 230 cu yd slab pour, 7 am Tuesday. Concrete truck arrives in four hours. Before it does, the engineer needs photo verification of 14 specific items: form alignment at gridlines 1 / 2 / 3, embed plates at C2 / D4 / E6, stop-end seals on the perimeter, rebar density at the column drops, two safety items.

Without FieldLog

Text the GC the list on Monday night. Get back 30 photos with no labels, three of the items missing entirely. Spend Wednesday morning calling the foreman to ask "which one is this?" Sign off the pour from memory.

With FieldLog

Drop 14 pins on the slab plan, label each ("Form A1 alignment, gridline 1", "Embed plate C2", "Stop-end seal, west edge"). Send one link to the GC's foreman. He opens it on his phone, sees the slab plan with red pins, taps pin 1, snaps a photo, leaves a 10-second voice note ("aligned, no gaps"), swipes to pin 2. Every photo lands in the project folder, pre-labeled with the pin name and gridline.

fieldlog.local /plan/PIN-2c7a14
Tower 2 — L14 slab · 14 pins
A B C D 1 2 3 1 2 3 4 5 6 7 8 9 10 11 12 13 14
8 done 3 in field 3 pending
1 Form A1 alignment, gridline 1 ✓ alice@gc · 6:42 am
7 Embed plate location, C2 ✓ alice@gc · 6:51 am
9 Stop-end seal, A3 west edge capturing now…
12 Rebar density, column drop D3 queued
5

Signatures without the inbox scramble

Send the link once. Get the signed file back.

Today With FieldLog
Print, sign, scan, email back. Sign on a phone, in 60 seconds.
Three rounds before all signatures arrive. Each signer gets their own private link.
One person prints the whole thing again. Signed PDF delivered to your folder automatically.
Nobody can say for certain when it was signed. Tamper-evident record of who signed and when.
6

Files for review, without dead links

Share what you need, for as long as you say.

Today With FieldLog
Dropbox link expired Friday before review. The link lasts as long as you say it does.
Three versions in three folders — which is current? One link per request. One source of truth.
The contractor's IT blocks the share. Works on any phone or browser.
You can't tell if anyone actually opened it. See when it was opened, submitted, or revoked.
7

Reports that write themselves

Friday morning. Coffee, not formatting.

Today With FieldLog
Open seven message threads to find the photos. Every submission is already a report.
Drag images from a phone backup. PDF, Word doc, archive bundle — auto-generated.
Re-key field data into Word. Saved to the project folder you already use.
Repeat next Friday. And the Friday after. Same format, every time. No more "this one looks different."
8

Multi-party approvals that flow

Stop asking "who has it now?"

Today With FieldLog
Form gets emailed to the engineer for review. Each reviewer gets their own private link.
Engineer forwards to PM, who forwards to client. Watch the chain advance, hop by hop, in real time.
One person on vacation. Nobody can tell. Stuck somewhere? Recapture and send on a different path.
The whole thing comes back two weeks later. Maybe. Send to several reviewers in parallel when speed matters.
9

Records that hold up

Audit trail you'll never need. Until you do.

Today With FieldLog
"I'm pretty sure he approved it on the 12th." Who approved what, and when — exactly.
"There was an email — I'll find it." Who sent it, who opened it, who signed it.
The original signed copy left with someone who's gone. Sortable, searchable, exportable in standard formats.
Warranty claim three years later: hope you have receipts. Records cannot be edited or deleted — only added to.
10

Subcontractor compliance, on autopilot

The toolbox talks. The daily reports. Without the chasing.

Today With FieldLog
You text a reminder every Monday. Recurring forms — daily, weekly, on a custom schedule.
Most weeks, half the crews reply. Some weeks, none. One dashboard shows who responded and who didn't.
You don't notice the gap for a fortnight. Late submissions are obvious at a glance.
Audit time: who's actually been doing them? Three months from now, the record is still there.
11

From a thirty-second snap to a six-week chain

One tool. Used as lightly or as seriously as the work needs.

A field tech sketching a quick site note uses the same engine as the PM orchestrating monthly compliance returns from twelve subcontractors. Same project folder. Same audit ledger. No second tool to license.

⚡ 30 SECONDS
Capture & go

Snap a photo, drop a pin, leave a voice note, scribble a sketch on the screen — done before you're back at the truck.

  • Site sketch from the field
  • "What's that pipe?" photo
  • Spill / hazard snap
  • RFI on the spot
📋 5 MINUTES
Structured form

Fixed fields, photo slots, signature line. Same form every visit. Submit; the PDF lands in the project folder.

  • Daily site report
  • Incident report
  • Equipment check
  • Borehole / compaction log
🔗 1–3 DAYS
Multi-party chain

Capture, then route. Inspector → PM → EOR → owner. Each one gets a link; no app to install. You see the chain in real time.

  • Concrete pour sign-off
  • Hot-work permit
  • Change order approval
  • Work-stop notice
🔁 FOREVER
Scheduled + fan-out

Recurring send to a list — daily, weekly, monthly. Auto-tracks who replied, surfaces who's late, loops forever without a person remembering.

  • Weekly toolbox talks
  • Monthly compliance returns
  • Quarterly site audits
  • Daily subcontractor sign-ins

Start anywhere. Move up the ladder when you're ready. The data shape is the same all the way through.

12

A quick look

See it in action.

Six screens that show what the tool actually feels like — capture in the field, orchestration in the office, audit when it matters.

14
Capture in the field
15
Following an approval chain
16
All chains at a glance
17
Activity by project
18
The audit ledger
19
Who signs what
13

Capture in the field

Open the form. Capture. Submit. Done.

One screen, one form, one tap. Every field type your work needs — photo, voice memo, GPS pin, signature, structured text — all in the same flow. Works without internet; uploads when it can.

  •  Photos auto-tagged with project + GPS
  •  Voice memos transcribed in the background
  •  Pinned plans, weather snapshot, timestamp
  •  Queues offline; syncs when you're back in coverage
Daily Site Report
📍 25 Booth St · P-2024-118
🌤 8°C, partly cloudy
🎙 Voice memo · 0:34 transcribing…
A
B
+
Inspector signature
Submit
14

Following an approval chain

You always know where it is. And what to do next.

One request, three signers, two days of email — replaced by a single page that shows where it sits, who's late, and what to nudge.

fieldlog.local /admin/chains/CHN-7f3a92
Concrete pour — Tower 2, Level 14
Started 2 days ago · 4 hops · 2 done 1 pending
Inspector capture  complete
alice@field · submitted Apr 22, 9:14 am · 12 photos, signed
PM review  complete
dan@office · signed Apr 22, 4:52 pm · recaptured field 3
Engineer of Record sign-off  awaiting signer
eng@external · sent Apr 23, 10:00 am · reminder due tomorrow
Owner acknowledgement  queued
owner@client · will fire when EOR signs
15

All chains at a glance

Every multi-party approval, on one page.

Where every approval lives across every project. Late ones bubble up; completed ones slide off; nothing falls through.

fieldlog.local /admin/chains
14
Active chains
6
Awaiting reply
2
Overdue
38
Done this month
ChainProjectKindProgressStatusLast activity
Concrete pour — L14
CHN-7f3a92 · 4 hops
Tower 23-hop
awaiting EORApr 23, 10:00
Toolbox talk — west crew
CHN-2d40e1 · weekly
Booth Stfan-out · 5
2 of 5 leftApr 23, 7:32
RFI 0042 — slab edge
CHN-8b1cf4 · 2 hops
Tower 22-hop
completeApr 23, 6:14
Hazmat survey — bldg D
CHN-4a82bc · 3 hops
Lansdowne3-hop
overdue 1dApr 22, 14:51
Spill report — fuel tank
CHN-9d77a3 · first-wins
Booth Stfan-out · 3
winner: mayaApr 22, 10:08
16

Activity by project

One card per project. The pulse of the office, on one page.

fieldlog.local /admin/projects
all 14 active 9 closeout 3 archived 2
P-2024-118
25 Booth St · Tower 2
62
active4 today
P-2024-091
Lansdowne — bldg D
38
active1 today
P-2023-204
Carling overpass
19
closeoutquiet 6d
P-2024-120
Bayview borehole
11
specialistquiet 3d
P-2024-122
Pinecrest — intake
3
intake1 today
P-2024-101
Westboro retrofit
47
active2 today

Click a card → every submission, request, and chain for that project.

17

The audit ledger

Append-only. Searchable. Always there.

Every approval, sign-off, and access decision — recorded the moment it happens. You'll likely never need it. When you do, it's already there.

fieldlog.local /admin/access/approvals-log
last 90 days 19 action types
WhenActorActionSubjectDetail
Apr 23, 16:02dan@officeapproveregistration: priyank@sponsor endorsed; auto-approved
Apr 23, 14:51systemsms_challenge_sent+1 613 ••• 4490code 8c3a, ttl 10m
Apr 23, 10:14alice@fieldsignchain CHN-7f3a92 hop 1SHA-256 verified
Apr 23, 09:00systemrecurring_firedtoolbox talk · west crew5 recipients dispatched
Apr 22, 17:33dan@officerevokerequest DEMO-2c1ftypo in recipient
Apr 22, 16:52dan@officerecapturechain CHN-7f3a92 field 3amended quantity 3 → 4
Apr 22, 11:08sponsor:eor.examplesponsor_endorseregistration: legacy@verbal code matched
Apr 22, 09:14alice@fieldsubmitDaily Site ReportP-2024-118 · 12 photos
18

Who signs what

Set it once per form. The chain knows what to do.

Templates encode "who reviews what" so a new request goes to the right people without anyone remembering. Override per request when needed.

fieldlog.local /admin/forms/concrete-pour/signers
Concrete pour — Signer chain
Applies to every new request from this form · Apply template…
1. Inspector  field user
whoever submits the form · signs photos + structured fields
2. Project Manager  internal user
dan@office (default) · reviews + can recapture · SLA: same day
3. Engineer of Record  external · magic link
role: structural EOR · resolved per project · SLA: 2 business days
4. Owner acknowledgement  contact
role: project owner · signature optional · reminder after 3d
+ Add signer  ·  reorder by drag · per-request overrides allowed
19

After submit, the boring magic happens.

One tap in the field. The platform handles everything else.

The reason field documentation eats Friday mornings is the work after the inspection. That's the part FieldLog automates.

📁

Files in the right folder

Photos, voice clips, structured fields — sorted into the project folder, named consistently, exactly where humans already look.

📄

PDF + DOCX, branded

Every form auto-generates a polished PDF and an editable DOCX. Your letterhead. Your signatures. Searchable text inside.

🎙

Voice notes, transcribed

Background transcription. The narration is already text in the report by the time anyone goes to read it.

📷

Photos, fully tagged

GPS, weather, project number, timestamp — baked into the photo metadata at the moment of capture. No fixing in the office.

🧾

Audit ledger entry

Who did what, when — with a hash that proves the file hasn't been touched. Append-only. Never edited.

🔔

Notifications routed automatically

Email, Teams, SMS — notifications go where each recipient already lives. Reminders schedule themselves for late signers.

20

Plays nicely with the rest of your stack

Hands data to the tools you already paid for. Doesn't try to replace them.

💾

Lands in your file server

OneDrive, Dropbox, SMB share, S3 — submissions land in the path you already back up nightly. No new place to look.

📨

Email, Teams, SMS

Notifications routed where your team already lives. SMS for off-hours. No new inbox to monitor.

🔗

Webhooks → anything

"Submit" can fire into QuickBooks for billing. "Sign-off" into your PM tool. Wire it once, forget it.

📊

Power BI / Excel rollups

JSON exports per form, per project, per date range. Drive KPI dashboards from real submission data — no proprietary lock-in.

🏷

TagAndReport handoff

Inspection photos hand off for annotation; the polished tagged photo report comes back, signed and bound.

🔐

Microsoft / Google SSO

Same login your team already uses. Optional — it stays fully local-only if you'd rather not connect to the cloud at all.

On the roadmap: AI inspection summary · Procore / ClickUp / Asana hooks · auto-redaction for client bundles · one-click project closeout ZIP

21

Works on the phones your team already has.

No app store. No new device. No new training day.

📲

Installs from a link

Open a link, tap "install" — that's it. Looks and feels like an app, isn't one. iOS or Android, doesn't matter.

📡

Works without internet

No signal? Keep capturing. The submission queues on the phone and uploads itself when service comes back.

🎤

Voice notes, pin drops, QR scans

Voice notes that get cleaned up automatically. Pin drops on a plan. QR scans for equipment tags. Nothing to type.

Your inspector opens a form, captures what they see, hits submit. That's the whole interaction.

22

The boring stuff that matters

Standard. Simple. Your own data.

  • Files in a folder you own. Photos as JPEGs. Reports as PDFs. Records as standard files. Open them in anything.
  • Lives on your hardware — your office, or a server you rent. No vendor holding your data hostage.
  • No per-seat fee. No surprise pricing on year three. Add as many users as you want.
  • Walks away with you. If it ever stops being right for you, you keep everything in formats anyone can read.
  • Auditable, controllable. You decide what each role can do. Every action is recorded.
Your project folder ├── 2026-04-12_Fairview-A │ ├── 000_photo.jpg │ ├── 001_photo.jpg │ ├── 002_voice.m4a │ └── daily_report.pdf ├── 2026-04-13_Fairview-A │ ├── 000_photo.jpg │ ├── 001_photo.jpg │ └── daily_report.pdf └── 2026-04-14_Fairview-B ├── 000_photo.jpg ├── 001_voice.m4a └── incident_report.pdf
23

A day in the life

Three roles. One platform. No friction.

The Inspector

"I open the form, capture what I see, submit. Done."

Same form every day. Voice notes instead of typing. Plan-pin drops where I'm standing. Works without signal. Submit, and the office has it before I'm in the truck.

The Office

"I see what came in this morning, send what's needed, watch the chain."

Every submission lands in a list. Send a form to a contractor with one click. Watch the multi-party reviews advance without chasing. Audit trail is always one tab away.

The PM / Owner

"My weekly summary is already in the project folder when I sit down Monday."

Reports auto-generate. Photos are in folders by site. Signatures are on the contracts. When something disputes, the records are right there — dated, signed, hash-verified.

24

What a pilot looks like

Six weeks. One real project. Walk away with all your data.

Week 1

Setup

We install on your hardware. Configure your project folder. Tune the forms to your existing workflows. Nothing on the public internet that you don't want there.

Week 2

Training

One short session for inspectors (30 min on a phone). One for office staff (an hour). That's it. Add-to-home-screen install while we're together.

Weeks 3–5

Real project

One project, end-to-end. Photos, signatures, reviews, reports. We're available for tweaks; nothing is set in stone.

Week 6

Review

Look at what changed. Decide whether to keep it. Either way, every photo, signed PDF, and report you generated is yours, in standard formats. Nothing to migrate out of.

No multi-year contract. No per-seat license. No data lock-in.

25

Pick a project.
Try it for six weeks.

We'll set it up on your hardware, tune the forms to your workflow, and walk through one real project with you. If it doesn't fit, you keep everything you generated, in formats anyone can read.

Pilot lead
Elliott Smith
elliott@lrl.ca · LRL Associates
Want the technical detail?
See the engineering deck
docs/pitch.html

Press P to print this deck.

26