SiteQura · A FidelonX vertical solution

Structure, verification and intelligence for physical operations.

SiteQura is the system of record for work done at sites, by crews, on assets — built to capture what actually happened in the field, prove it, and make it visible to everyone who depends on it.

01 · The problem

Physical work is done far from where it is accounted for.

On a site, the truth is what a crew did, when, where, and to what standard. By the time it reaches an office, an inspector or a client, it has passed through informal messaging threads and fragile spreadsheets — and lost most of its credibility on the way.

  • 01“Sent the photos on the group.” No location, no timestamp you can rely on, no owner.
  • 02“It's in the spreadsheet.” Edited by anyone, reconciled by no one.
  • 03“He was certified last year.” Nobody checked before he was dispatched.
02 · Field reality

Software that only works with signal isn't field software.

Crews finish substation commissioning in extreme heat with no cellular bars. SiteQura is designed on the assumption that networks are broken and devices are transient — and that the record still has to be trustworthy.

CaptureRecorded on the device

Readings, torque tests and punch-lists persist locally the instant they're entered.

Offline · 1,840 s in this exampleNo signal. No problem.

Work continues. Entries queue in a local write-ahead store and IndexedDB buffer — nothing is lost, nothing waits on a spinner.

ReconnectSynced atomically

Queued records sync as one unit, without merge collisions.

Illustrative sequence

03 · The SiteQura system

Every entry becomes a signed record.

A record in SiteQura isn't a row someone typed. It carries where it was captured, what was measured, how long the device was offline, who signed it off, and a checksum that proves it hasn't changed since.

That is what turns a field log into a system of record — something an inspector, a client or an auditor can rely on without taking anyone's word for it.

CRYPTOGRAPHIC RECORD MANIFEST #08942CONNECTED
target_arrayString 4B · 148 kW installed
coordinates33.4484° N, 112.0740° W
event_id99f4d382-7d0e-47aa-…

torque_spec_verifiedtrue
inverter_reading_kw148.12
offline_duration_seconds1840
supervisor_hmacPASS
sha256_checksum9b12a8…31cc

tenant_isolationrow-level security · verified
Illustrative product view
04 · Verification

Trust is checked, before and after the work.

A

Deployment gates

Crew leads whose safety certifications or insurance coverage have lapsed are locked out of dispatch automatically — before they reach a site, not after an incident.

B

Worker & safety verification

Background verification and safety status sit in the same system that assigns the work, so compliance isn't a separate spreadsheet.

C

Supervised daily briefings

Sixty-second in-situ safety modules, confirmed by supervisor sign-off on the device itself — captured as part of the day's record.

DISPATCH GATEILLUSTRATIVE
Crew leadSafety cert.InsuranceDispatch
Lead AvalidvalidCLEARED
Lead Bexpires soonvalidCLEARED
Lead ClapsedvalidLOCKED
Illustrative product view
05 · Intelligence

A record structured enough to reason over.

Because every entry is verified, located and timestamped, SiteQura holds the kind of data an intelligence layer can actually use — a field reality that is complete, consistent and attributable, rather than a pile of photos.

SiteQura understands physical execution. Fidel Labs is the AI platform designed to reason across the systems surrounding it — the CRM, the schedule, the support queue — under the same controls: scoped tools, deterministic routing where it matters, and no invented answers.

Architecture direction

06 · Operational visibility

Everyone downstream sees the same truth.

Scheduled jobs collate each day's verified records into deterministic inspection reports and dispatch them to the people who need them — including municipal inspectors — without a coordinator assembling them by hand.

Each organisation's data is isolated at the database level, so contractors, utilities and clients can share a system without sharing each other's records.

Automated report dispatch

Compiled and delivered on a schedule.

Per-organisation isolation

Row-level security, not convention.

07 · Outcomes

What changes when the field is accountable.

Evidence

Records you can stand behind

Signed, located and checksummed — usable in front of an inspector or a client.

Continuity

Work that doesn't wait for signal

Capture and progress continue offline, and reconcile cleanly afterwards.

Compliance

Gates instead of good intentions

Lapsed certification or cover stops dispatch, automatically.

Reporting

Audit-ready by default

Daily verified records roll up into reports without manual assembly.

Isolation

Shared platform, separate data

Each organisation's records stay its own.

Foundation

Ready for an intelligence layer

Structured, verified data that Fidel Labs can reason across.

Where it applies

Solar EPC is where it began. It isn't where it ends.

SiteQura is engineered for solar utility construction, industrial civil engineering and high-voltage grid teams. But the underlying problem is not specific to solar. It appears in any business that executes work at physical sites and has to prove it afterwards.

If your work is delivered through any of these, the same system applies:

Physical sitesDistributed infrastructureProjectsField teamsInspectionsInstallationsMaintenanceComplianceExecution workflows