All guides
Getting started
What is Submittal Kit Create Your Workspace Your First Project Search Everything The Dashboard Help and What's New Abbreviations We UnderstandProjects & Schedule
Project Settings Schedule and MilestonesEquipment Register
Equipment Register Basics Import a BOM Equipment DocumentsParts & Library
The Parts Library Part Documents Find Datasheets The Document Library Search Inside DocumentsSubmittals
Create a Submittal Configure Sections Choose Equipment Scope Compile a Submittal O&M Manuals Submittal Numbering Cover PagesRevisions & Review
Issue a Revision Submittal Log Returned Reviews Record an External SubmittalRFIs
RFI Basics RFI Log RFI LayoutsField & QA
Punch Lists As-Built RedlinesSpecifications & Scope
Upload Specifications Spec CheckProcurement & Change Orders
Quotes and Purchase Orders Coverage and Lead Times Change Orders Budget and SOVDirectory & Team
Firms & Contacts Team & Access Personnel & CertificationsSettings & Billing
Company Identity Library Vocabulary Billing and PlansIntegrations
Connect an AgentHelp Specifications & Scope
View as MarkdownSpec Check
Read every datasheet on a submittal against its spec section, and get one answer per requirement.
A submittal tied to a spec section can be read against it. The check takes every datasheet on the submittal, the section's text, and the parts the submittal covers, and answers one row per requirement per part.
Run it
Run spec check sits on the submittal page. It runs only when you press it, and it needs a primary spec section on the submittal, at least one part with a datasheet, and a paid plan. When one is missing the button is there but dark, with the reason beside it.
A run reads each datasheet once, even when several parts share it, and judges it for each part. A very long datasheet is read in part: the pages that name the part or its ratings go first, and the panel says "not all pages read" for that document.
What comes back
Each requirement is one row with a glyph and a word.
- Meets. The datasheet states a value that satisfies the requirement. The row carries the value, the line it was found on, and the page.
- Does not meet. The datasheet states a value that fails it, or the manufacturer is not on the section's list. The next action says whether to swap the product or ask the engineer.
- Look at this. The datasheet does not state it, it depends on the ordered configuration, or the cited line could not be found on the page. The row says which.
Rows never do arithmetic. A value in the wrong unit is Look at this, not a verdict.
Section fit
Before checking, the run asks which section in the project's book the parts read like. When that differs from the linked section, the panel says so with Change section and re-run. When the submittal has no section, the picker proposes one, and linking it starts the check.
Mark a row yourself
Mark any row Meets, Does not meet, or Look at this, with a note. The mark shows as "Marked by you" beside the machine's verdict, and it survives re-runs and revisions of the same part.
When it goes stale
Changing a part, a datasheet, or the primary section marks the last run out of date. The findings band says so with a Re-run button. Nothing re-runs on its own.
Updated Sep 2, 2026
Can't find it? [email protected]