Capture the field.
Prove the work.
Offline-first observation capture. GPS-and-compass-stamped photos. The compliance record built from the work itself. Used by crews in the field, and the office that has to make the record stand up.
Operational layers baked into the map: wells, pipelines, roads, watersheds. No exporting shapefiles, no swapping apps.
The boring stuff, done right.
Field crews capture. Reports assemble. The same record holds up wherever it lands: a regulator, a nation, an operator, your own audit.
Offline-first
Zero cell signal? Full app. Capture photos, log observations, mark map locations. Auto-syncs the moment you're back in range.
GPS and compass-stamped photos
Every photo is watermarked at capture with UTM coordinates, bearing, and accuracy. Evidence that holds up, without anyone touching metadata.
Operational map layers
Wells, pipelines, roads, watercourses, watersheds, and reference grids baked in. NTS, BCGS, DLS. No swapping apps.
Configured to your operation
Captures shaped to the work you do. Environmental compliance ships with risk ranks (Positive, Low, Medium, High) and categories like soil handling, waste, watercourse, wildlife. A different operation gets a different setup.
Reports that tell the story
Daily logs, compliance rollups, evidence packages. Assembled from the observations the field captured, branded with your company. The same record serves a regulator, a nation, an operator, an internal review.
Track work over time
An observation isn't a snapshot. When crews return to the same site, updates layer on. The original record carries the full history: who came back, what changed, what's resolved, what's still open.
Audit-grade evidence
Pin observations to specific commitments and requirements. When the auditor asks how a requirement was met, the evidence is the observations themselves: GPS-stamped, photo-attached, time-coded.
Dedicated deployment
Your data lives on your instance. Not shared multi-tenant. MIT-licensed framework underneath. No vendor lock-in.
From a site visit to a finished record, without a spreadsheet in sight.
Capture in the field
Foreman opens the project, taps an observation, takes a photo. GPS, bearing, and accuracy stamp on automatically. Risk-rank it, categorize it, move on. Works without a bar of signal.
Sync when you have signal
Back at the truck, in town, at camp: the moment a connection is there, photos and observations sync. No manual upload, no losing the day if the phone dies.
Assemble the record
The same observations roll up into whatever record the work demands. Daily logs. Compliance rollups. Stakeholder updates. Built on a laptop or in a truck, sent wherever the audience sits: email, text, print, save. One source, many audiences.
A clean view of the work. And the gaps.
Open items, risk-ranked. Categories rolled up. Compliance trends per project. Drill into a single observation, or pull a stakeholder-ready PDF in one click.
Submissions roll up
Total submissions, form types, recent activity. What came in today, this week, this month, at a glance.
Reports look the part
Branded headers, company-name footers. Generated from observations, not retyped from a notebook. The kind of document that proves the work was done, for whoever's asking.
Same on every device
Foreman wants to see the daily report from his truck? It's there. Same data, same format, same signature line.
Your data, your instance.
We can spin up a dedicated deployment for your organization: separate database, separate file storage, separate everything. Or run on the shared platform with org-and-project isolation. Both are real options. The right one depends on what you're doing and who you have to answer to.
The framework underneath is open source (MIT). No vendor lock-in. If we ever stopped existing, you could keep running.
Shared platform
Org-level isolation on a managed instance. Fast to onboard, ideal for smaller operations.
Dedicated deployment
Your own database, your own storage, your own URL. Available as an in-house add-on for organizations that need it.
Custom plugins
Workflows we don't ship out of the box, built and integrated into your deployment on a per-engagement basis.
Configured to the work.
BirdDog is set up to match how your operation actually runs. Same code underneath, very different shapes on top. A few of the ways customers run it:
Compliance and reporting on real ground
Crews capture observations across sites: wellsites, pipelines, reclamation areas, watercourses. Photos GPS-and-compass-stamped. Daily logs, compliance summaries, and incident reports assembled on company letterhead. This is what most BirdDog customers are doing today.
Who's accountable. Who signed off.
Multi-stakeholder requirement tracking for owner and producer-class customers. The accountable party named per requirement, the consulted parties on record, the evidence trail attached. Built for projects where commitments outnumber the people tracking them.
Many clients, one workspace
One field worker, multiple organizations, multiple active projects. Switch context in one tap, see only what that engagement covers, keep client data isolated. Built into the platform, not bolted on.
If your operation looks different from any of these, that is not a problem. The platform is configured per customer at onboarding. You walk us through the work, we set BirdDog up to match.
See it on your work.
Thirty-minute call. Tell us about your operation: a project, a site, a compliance commitment. We'll show you BirdDog working against it. You'll know if it fits before you commit anything.