Features

Two audiences. One platform. No compromises.

SurveyOS is built for the field professional doing the work and for the partner firm that receives the output. Every feature serves both — but emphasized differently depending on who you are.

🧭
For surveyors & mechanics

Your tools, finally built for the way you actually work.

Every marine surveyor has done the same math: hours on the boat plus hours at the keyboard, writing the same findings three different ways for three different audiences. SurveyOS compresses that into a single field capture with multiple professional outputs. Your time on the water becomes the product.

Tablet-first field capture

Single-checkpoint focus, 48px minimum touch targets, works in direct sun. Built for the environments marine surveyors actually work in — engine rooms, yards, haul-out bays.

Offline-first sync

No connectivity at the marina? No problem. Checkpoints queue locally in IndexedDB with client-generated sync IDs. When you get signal, the batch uploads atomically — idempotent on retry.

Evidence anchored on capture

Every photo gets a SHA-256 hash the moment it hits the device. Uploads verify the hash matched. Once a report is issued, evidence is frozen — any attempt to modify it hits a database trigger.

Findings that defend themselves

Observation, inferred cause, and recommendation are three distinct fields. The UI enforces it. The database enforces it. The report renderer enforces it. You cannot accidentally conflate them.

Work orders without retyping

Select findings → convert to work-order lines in one click. Every line preserves the source finding ID. Mechanic completes the work; service history writes automatically. Findings aren't auto-closed — that's your call after reinspection.

Templates that match the vessel

The inboard-diesel sportfish template covers a 1984 Egg Harbor 35.5 with twin Cat 3208T — and it rejects items that don't apply. Different templates for sailing vessels, outboards, commercial platforms.

One inspection

Multiple outputs. Zero retyping.

The same findings compose differently for each audience. A CRITICAL raw-water hose weep appears on all three reports. Cosmetic gelcoat cracks appear only on pre-purchase. Maintenance items like depleted zincs appear on mechanic and pre-purchase but not insurance. Scope rules live in code — you never edit them manually.

Mechanic Assessment8 findings
Pre-Purchase Survey7 findings
Insurance Readiness3 findings
Owner Readiness Plan8 findings
🛡️
For partners & insurance firms

Reports you can trust. Data you can integrate. Audit trails that hold up.

Insurance partners, yacht brokerages, multi-site yards — SurveyOS was designed with the receiving side of the report in mind. Not just "the surveyor types it in and emails you a PDF." Integrated. Tamper-evident. Traceable back to the minute each observation was captured, by whom, on which device.

White-label report delivery

Your branding, your disclaimer language, your signature block. Every report exports as PDF, DOCX, or HTML bundle. Auditable at the browser level via the content hash on every frozen payload.

SSO / SAML for your team

Single sign-on via SAML 2.0 on Firm and Enterprise tiers. Role-based access control with blended-role support — your surveyor who also does mechanic work gets both capability sets under one login.

API + webhooks

Pull reports into your claims system. Push inspection requests from your CRM. Webhooks fire on engagement created, finding added, report issued — integrate with anything from AS/400 to Zapier.

Audit trail that holds up

Every state change, every edit, every export writes to an append-only audit log at the database level. Exports ship as tamper-evident CSV + JSON. Insurance partners who've been burned by paper trails understand why this matters.

Tenant isolation enforced at the data layer

Postgres row-level security means your data is isolated from every other tenant on the platform — even if our application code has a bug, the database will still refuse to cross streams.

Standards-aware without the copyright risk

Findings reference ABYC, NAMS, SAMS, and OEM topics by family + key + plain-English note. We never reproduce copyrighted standards text. Your reports stay clean; the referenced authority stays authoritative.

Defensibility deep-dive

Why a paragraph is not a finding.

1. Observed fact

"Port engine raw-water hose at heat exchanger inlet shows weeping at clamp; salt crystallization on hose barb. Hose appears to be original 1984 stock."

What you saw, heard, measured. No interpretation.
2. Inferred cause

"Hose clamp tension has relaxed with age; hose material likely hardened from four decades of service."

Professional inference — labeled as inference, separate from observation.
3. Recommendation

"Replace raw-water hose run from seacock to heat exchanger with ABYC-compliant reinforced hose; install double stainless T-bolt clamps; pressure-test cooling system after reassembly."

What to do. Converts directly to a work-order line.

Three fields. Three database columns. Three render blocks on every report. One reason surveyors who've been on the stand know exactly how much this matters.

See it on a real vessel, not a slide deck.

20-minute demo with the Egg Harbor reference profile and your questions.