Stop rebuilding client reports after every site visit

The Product Behind The Promise

One record, from field capture to client reporting

The item a crew opens on site is the item the office reviews, complete with its photos, location, status, and follow-up.

Field list Evidence record Client report

Oculi item record with status, location, repair action, and supporting field photos — Evidence record

Oculi open-items list showing the same NUPL field record — Field list

The item number, status, description, and field evidence remain connected instead of being rebuilt after the visit.

Two Sides Of The Same Record

For field-service providers and the organizations accountable for the outcome

Service providers move from site visit to client report without rebuilding the visit. Asset and program owners review the evidence, location, status, and follow-up behind reported work.

We deliver the field work Give crews a reporting-ready capture flow and give the office one record to review, correct, and report from. Request a client-reporting review We own or oversee the program Keep reported work tied to its evidence, location, status, and follow-up so exceptions are easier to verify. Request a program-reporting review

The Reporting Problem

The site visit is over. The report should not start from scratch

Photos on phones, notes in messages, and statuses in spreadsheets force the office to reconstruct each visit before a report can go out. Oculi keeps those details attached to the job from the start.

Use the same record to capture the visit, resolve gaps, track open work, and prepare the client deliverable.

Standardize what crews capture before they leave the site.
Keep each photo, deficiency, action item, location, date, and status attached to the work it documents.
Give reviewers enough context to approve or follow up without chasing the crew.

How It Works

Capture once, review once, report from the same record

Crews capture the site visit, office teams review exceptions and open items, and reports use the same photos, notes, statuses, and sign-offs.

Collect

Capture structured field records

Crews record site visits, inspection items, photos, locations, notes, checklist details, and status updates while the work is happening.

Validate

Reduce missing and inconsistent data

Standardized forms and required fields help teams submit information that will still be usable at review, closeout, and reporting time.

Track

See what is open, aging, or complete

Office teams monitor progress, exceptions, and action items without waiting for manual status chasing.

Report

Build reports from approved site details

Prepare client reports, closeout records, and exports from reviewed photos, notes, statuses, and sign-offs.

Site photos, notes, statuses, and reports stay connected from the first submission.

Gloved field user using Oculi to photograph site equipment

What Oculi Creates

A visual site record, not another folder of photos

Every item, photo, note, status, location, sign-off, and follow-up stays tied to the work it documents. The office can see what happened, what remains open, and what belongs in the report without reconstructing the visit.

Evidence in context Keep each photo with the item, site, work package, and location it supports.
Review before delivery Check photos, notes, status, checklist details, and evidence gaps before the record becomes a report.
Follow-up after closeout Keep unresolved items visible as Site Follow-Up Items instead of burying them in a completed PDF.

See How the Record Stays Connected

Case Study

Zon Generation saves close to two hours per job with structured maintenance reporting

Zon's maintenance teams now capture site photos, visit details, equipment data, and closeout notes in Oculi so office teams can review client reporting without rebuilding each report by hand.

Customer-reported result Close to two hours saved per job

Capture starts on site photos, equipment details, notes, and status stay with the visit

Review before delivery office teams use the same field record for client reporting

Operandi tailored the Oculi implementation around Zon Generation's existing reporting, so technicians could capture site photos, field notes, equipment details, status, and closeout information once in the field and transition that work directly into office review and client reporting.

"It's saving us close to two hours per job just in being able to quickly report on stuff and be able to capture the information."

Zon Generation, on maintenance reporting improvements

This is Zon Generation's reported outcome from its maintenance workflow, not a general performance guarantee.

Discuss Your Reporting Workflow Read The Full Customer Story

Product Walkthrough

See the field-to-report workflow

Watch a site visit move from mobile capture to office review and reporting, with photos, notes, statuses, and open work staying attached to the same record.

Request a Workflow Demo Review the Platform

Built around the field, not just the office. Site records stay connected to the photos, issues, equipment notes, statuses, and closeout history your team needs later.

Platform Capabilities

The field-to-office tools for photos, open items, statuses, and reports

Oculi keeps site photos, open items, statuses, review, and reports connected in one field-to-office record.

Mobile field capture

Crews capture site visits, checklists, observations, photos, and status updates while the work is happening.

Offline-aware field work

Cached work, local item progress, queued photos, and sync recovery help crews continue when connectivity is unreliable.

Open-item tracking

Track open items, aging work, exceptions, work-package status, and follow-up from the portal.

Custom reporting

Build client reports around the fields, photos, statuses, and deliverables each program needs to review.

Photo and asset context

Keep site records connected to the photos, issues, equipment notes, statuses, and closeout history your team needs later.

Exports and integration planning

Review the reports, exports, and system handoffs your program needs, then plan the right delivery path for each approved record.

Start With A Real Reporting Problem

Choose the workflow your team needs to fix first

Oculi is configured around a field workflow your team already runs, including operations and maintenance (O&M), inspections, closeout, and client reporting.

Solar O&M field reporting

Keep site photos, equipment details, preventive maintenance records, closeout notes, and open work connected from each visit through the client report.

Explore solar maintenance reporting

Inspection and closeout reporting

Find missing evidence, unresolved deficiencies, and incomplete sign-offs before the package goes out.

Explore inspection and closeout reporting

Field-service client reporting

Give crews a structured capture flow and office teams a reviewable record for every service visit.

Request a field-service workflow review

Visual site records for program oversight

Keep each reported item tied to the evidence, location, status, and follow-up behind it.

Talk through your program reporting

Outcome-Based Pricing

Price the work being delivered, not the people logging in

Oculi pricing is aligned to the field work your team delivers: work packages, inspections, service visits, closeout packages, or recurring reports. Your team can collaborate without every login becoming the pricing driver.

Oculi does not make every login the main pricing driver. Pricing is aligned to completed work so field crews, coordinators, reviewers, and managers can stay connected without managing seat math. Read the pricing guide.

Focused rollout

Prove one work-package flow

Best for teams starting with one inspection, maintenance, closeout, service order, or reporting process where value is measured by completed work.

Configured forms and fields for your unit of work
Mobile capture and portal access
Guided setup through the first report

Request a Workflow Review

Growing program

Scale by work packages, sites, and reports

For teams expanding Oculi across recurring inspections, service orders, maintenance visits, and closeout packages where usage follows the work being completed.

Work-package and reporting configuration
Sites, roles, and project structure
Pricing aligned to work, order, or visit volume

Plan a Growing Program

Complex deployment

Match larger programs to reporting and rollout requirements

For larger deployments that need custom reporting, integrations, governance, and a commercial model tied to program scale.

Custom work-package reporting flows
Integration and export planning
Commercial model matched to program scale

Discuss Program Requirements

Implementation Support

Guided onboarding is part of the product

We help turn your current forms, reports, sites, assets, and rollout needs into a working Oculi setup.

Map the current workflow and reporting needs.
Configure Oculi around your sites, assets, forms, and statuses.
Support the first workflow through field capture, office review, and report delivery.

FAQ

Questions about Oculi field reporting and rollout

Start with your current forms, report, and field-to-office handoff. These answers cover fit, connectivity, integration, rollout, users, and pricing before a workflow demo.

What does Oculi replace?

Oculi replaces the disconnected handoff between paper forms, spreadsheets, shared folders, photo dumps, manual PDFs, and message threads with one structured record for field capture, office review, reporting, and follow-up.

Can Oculi reports match the templates we already use?

Yes. Oculi can be configured around your existing reporting process, including the fields, photos, notes, statuses, and deliverables your team or clients already expect.

Does Oculi work when crews have poor connectivity?

Oculi supports offline-aware field work with cached site data, local item progress, queued photos, and sync recovery when connectivity is unreliable.

Can Oculi connect with the tools we already use?

Oculi supports exports, reporting workflows, and integration planning depending on the systems your team uses. In a workflow demo, we review where data needs to go after field capture.

How long does it take to get the first workflow live?

The timeline depends on your forms, reports, sites, and rollout scope, but guided onboarding is built around getting one practical workflow live first instead of trying to rebuild every process at once.

Who configures the forms, workflows, and reports?

Guided onboarding is part of the product. Operandi helps map your current workflow, configure Oculi around your sites and forms, and support the first rollout.

Who on our team uses Oculi?

Field crews capture records in Oculi, while office teams review the data, track open items, and run reports. On smaller teams, field crews may also review or produce reports depending on the company structure.

Is Oculi only for solar teams?

No. Solar operations and maintenance (O&M) field reporting is one focused use case. Oculi can also be configured around engineering reviews, equipment installations, EV charging, battery storage, inspections, commissioning, preventive maintenance, and closeout workflows.

How does pricing work?

Oculi pricing is aligned to the field work your team delivers: work packages, inspections, service visits, closeout packages, or recurring reports. Your team can collaborate without every login becoming the pricing driver.

Trust And Procurement

Bring the hard questions before rollout

Review Oculi's access, field data, offline, reporting, privacy, and support model with the Operandi team before implementation.

Discuss Security, Privacy, And Rollout

Request A Workflow Review

Bring one report you build today

Bring an anonymized report or closeout package and the field form behind it. We will map the capture, review, reporting, and follow-up steps and show where Oculi can remove rework.

Start with one real report, program, or recurring site visit.
Agree on the evidence, status, review, and follow-up the workflow needs.
Use a focused rollout before expanding into other processes.