A record that stands up later.

In this industry, the check matters — and so does proof that the check happened. Every audit Nudgy runs is recorded permanently: what was checked, against which version, when, and what was found.

Record
Append-only
Captures
Doc rev · spec ver · time
Passes
Stored as proof
Retention
Permanent

The record

What every audit writes down

DOCUMENT
File name and revision of the drawing that was audited.
SPEC VERSION
Exactly which version of the specification it was checked against — addenda included.
TIMESTAMP
When the audit ran, to the second.
FINDINGS
Every finding, with severity, explanation, and citation, as issued.
PASSES
Every element that was checked and found compliant. Proof of coverage, not just failures.

Append-only by design

Audit records are never edited and never deleted. A re-run produces a new entry; a correction produces a new entry. The history of a project on Nudgy reads the way a site diary should: in order, complete, and unrevised.

Why this matters in AEC

Liability in this industry turns on what was known, when, and against which document. “We checked it” is only a defense if you can show what version you checked and what the check found. Nudgy makes that provable per revision — including the spec version in force at the time.

How teams use it

Dispute resolution, when a change order is contested months later. QA documentation, when a client or insurer asks how compliance was verified. Handoff records, when a project changes hands mid-stream and the new team needs to know what was checked and when.

Passes are part of the record

A record that only lists failures cannot demonstrate coverage. Nudgy records every element it verified as compliant alongside every finding — so the trail shows the breadth of the check, not just its exceptions.

Revision comparison

Diff two revisions in findings, not gut feel

The trail records every run — and revision comparison reads two records side by side: what the new revision resolved, what it carried forward, what it introduced, and anything that grew more severe. 'Did Rev 4 actually fix it?' has a documented answer.

Get started

See Nudgy run against one of your own specs.