Support

Nudgy cross-references your construction drawing revisions against the project specification and returns findings — each with a severity and a citation to the exact spec section it rests on. It is built for the schedule-based compliance checking that is slow and error-prone to do by hand.

A Microsoft 365 account with your project specification and drawing set in OneDrive or SharePoint, or the files to upload directly. That's it — there is no software to install and no server to run.

Minutes. You create a project and add the specification — uploaded directly, or picked from OneDrive or SharePoint. The spec is indexed once; each drawing revision you add is checked against it from then on.

No. Nudgy precedes the review — it hands the reviewer a cited punch list instead of a blank spec — but the professional judgment and sign-off stay with your licensed architect or engineer. See Accuracy & limits below.

A single read-only Microsoft Graph scope, used to browse and retrieve the specific files you pick. Nudgy never writes, moves, renames, re-permissions, or deletes your files, and it does not retrieve files you have not selected.

No. Authentication happens entirely on Microsoft's side. The read-only access token stays in your own browser session — it is not stored on Nudgy's servers and expires automatically.

Yes. You can connect more than one OneDrive or SharePoint account and switch between them when choosing files — useful if you work across several clients' tenants. If a session expires mid-task, Nudgy re-authenticates in place and resumes what you were doing.

Both. When adding a spec or a drawing, pick the file from the SharePoint document library or OneDrive folder where it lives.

Revoke Nudgy's read-only access at any time from your Microsoft admin center or account settings. Revoking prevents adding further files from Microsoft 365; it does not delete documents already added or audit records already generated (see the Privacy Policy on retention).

A wide range of schedule types across the CSI MasterFormat divisions — doors, windows, and finishes, plus structural, envelope, mechanical, electrical, plumbing, and fire and life-safety schedules. Nudgy selects the right rule set automatically from the schedule type on the sheet.

Yes. When the conflict lives in the spec — a contradiction between Part 1 and Part 2, or a reference to a superseded standard — the finding names the spec as the document in error, not the drawing.

Today Nudgy focuses on schedule-based audits, where most spec-compliance errors live and where the data is structured. Floor-plan element detection and detail auditing are on the roadmap, not in the current scope.

Nudgy works best on vector PDFs exported from Revit or AutoCAD, where the text is directly extractable. Scanned or raster pages can't be read at that fidelity, so Nudgy skips them rather than guessing — and lists every skipped page right on the audit report, so your coverage is never silently degraded. Re-export those sheets as vector PDFs to have them audited.

The specific element (named the way the schedule names it), a defined severity, a plain-English explanation, and a citation to the exact spec section and clause. No black-box verdicts — every finding shows its work.

Every element gets a status: conflict (a requirement is violated), warning (a condition the documents can't confirm either way — needs human verification), or compliant (checked and passing, recorded rather than discarded). Conflicts and warnings then carry a severity: critical (life-safety or accessibility — fire ratings, egress, ADA), major (a code or spec violation requiring correction), or minor (non-compliant, limited impact). Each finding also names its error source — drawing error, spec error, or field verification when resolution depends on something the documents can't show.

Yes. Opening a finding shows the cited section beside it with the relevant clause highlighted, so you can confirm it — or overrule it — against the requirement itself.

Yes. You can dismiss a finding you've reviewed or accepted; it is set aside, not deleted, and your decision persists. The full set of findings stays in the immutable audit record.

Yes. Revision comparison diffs two audits of the same project into new, resolved, and still-open findings, and flags any issue that grew more severe between revisions.

No. Nudgy is an automated aid. Its findings do not constitute architectural, engineering, legal, or code-compliance advice, and they do not replace the independent judgment, review, and sign-off of a licensed professional. You remain responsible for the compliance and certification of your drawings. See the Terms of Service.

Yes. Findings are generated by software and AI models and may contain errors, omissions, or false positives, and may fail to identify a non-compliant condition. The absence of a finding is not a certification of compliance — do not rely on a finding, or its absence, as the sole basis for a decision.

Documents you add to a project are stored in private, access-controlled storage, isolated per organization. An isolated worker reads the stored document, extracts the schedule tables, and runs the audit. Your source files in Microsoft 365 are never modified — Nudgy works from its own stored copy.

The documents you add, the spec index, the embeddings, the findings, and the audit records for your project — the trail your industry requires, traceable to the exact document version behind each finding. Everything is separated per organization and per project, enforced server-side on every query.

No. Audit analysis and embeddings run under commercial API agreements — the enterprise terms, not consumer AI products. Documents are sent for processing only; they are not contributed to anyone's training data.

Yes. All traffic is encrypted in transit with TLS, and the spec index, findings, audit records, and stored tokens are encrypted at rest by the managed services that hold them. The full security model — and the named subprocessor list — is documented for vendor review.

Nudgy is organized by organization, project, and team membership, so your team shares projects while access stays scoped. A team sees its projects and nothing else.

Pricing is tailored to your firm and is discussed in the demo against your own numbers. Small firms carry the same per-drawing liability as large ones, so the audit engine is the same at every size — only the price scales.

Onboarding is a working session run against one of your own specs, not a slide deck. Reach out and we'll set it up.

On request, and subject to our agreement, we delete or return Customer Content and delete the personal information we control, except where law requires retention. Details are in the Privacy Policy.

Try running it again. If it fails a second time, email us with the project, the approximate time, and the document involved, and we'll look into it directly.

Open the finding and read the cited clause beside it — that's the requirement the verdict rests on. If you disagree, you're disagreeing with the spec, not a black box; overrule it and, if you think it's a genuine miss, tell us so we can improve.

Specification manuals and drawing sets up to 200 MB upload directly, including large multi-hundred-page documents.