What does the Spec Reviewer flag, and why are some fields left blank?

Overview

Alongside the requirements it extracts, the Spec Reviewer highlights issues that could affect your bid, and it fills in only what the specification actually states. It flags problems for your review. It doesn't resolve them or decide for you.

What it highlights

Flag	What it means	Why it matters
Missing referenced documents	The specification refers to documents that weren't included in your upload.	Requirements in those documents can't be extracted, so a value you expect may be missing or incomplete.
Unreadable pages	Pages the Spec Reviewer couldn't read.	Requirements on those pages may not have been captured.
Conditional project requirements	Requirements that apply only under certain conditions.	You'll need to check whether the conditions apply to the application you're working on.
Conflicts	Places where requirements disagree.	You need to decide which requirement to design to.

Who decides which requirement governs?

You do. When documents conflict, the Spec Reviewer highlights the conflict but doesn't decide which requirement governs. Use the file, page and section shown for each value to compare the conflicting statements, and confirm with the specifier if it's unclear which one applies.

Why are some fields blank?

The specification doesn't state the value. The Spec Reviewer doesn't invent a value the specification doesn't state.
The field is yours to set. Some fields are controlled by the producer, and the Spec Reviewer doesn't fill all of them.
The value is in a document that wasn't uploaded. Check whether the Spec Reviewer flagged a missing referenced document.
The page couldn't be read. Check for unreadable-page flags.
Invent a value the specification doesn't state.
Decide which requirement governs when documents conflict.
Replace your review, or fill every producer-controlled field.
[Link: How do I use the Spec Reviewer to turn a job specification into a Mix Designer project?]
[Link: Do Climate Earth's tools replace lab testing, engineering review or compliance decisions?]

The form is editable, so you can complete blank fields and adjust anything that needs your judgment.

What the Spec Reviewer doesn't do A practical review routine

1. Look at the flags first: missing documents, unreadable pages, conditional requirements and conflicts.

2. Resolve what you can. Add missing referenced documents, and confirm conflicts or conditions with the specifier.

3. Open the source references for the values that drive your bid.

4. Complete any blank, producer-controlled fields, then accept the application.

Related articles