THE SPECSPRINT FIELD GUIDE
Make a specification catalog someone else can check
A useful specification catalog lets a colleague check a value without reconstructing how you found it. Treat the source reference as part of the record, not an optional note at the end.
Start with the intended comparison
Choose a concrete task, such as finding prior pump packages with an electric drive and vertical orientation. Agree which attributes support that task and which decisions remain outside the catalog. Limit the first batch to a coherent equipment family.
Separate the value from its evidence
For a stated field, capture the value and unit separately, plus the source page and supporting excerpt. Preserve the original wording rather than silently converting ambiguous text into a more precise claim. Keep the source filename and revision on the record.
For example, a fictional schedule might state “rated flow 80 L/min” on page 1 while a revision note states “rated flow 100 L/min” on page 2. Store two conflicting claims. A single unqualified 100 in the spreadsheet would hide the unresolved decision.
Use three explicit observation states
- Stated: the source supplies the value, and the page and excerpt are retained.
- Missing: no value is recorded. Do not convert this into zero or a guessed default.
- Conflicting: source passages disagree; each claim keeps its own page and excerpt.
These states help a reviewer distinguish available information from work still needed. They do not express statistical confidence or engineering certification.
Review against the original
Assign a reviewer who understands the documents and intended use. Check each stated field against its source and resolve conflicts before recording the local review. In SpecSprint, changing a record clears its prior review so the earlier check cannot silently cover new content.
A review note documents a local check. It does not replace your organization's approval process. The same applies to imported project files: review metadata is a local record, not a signed certificate.
Deliver the working copy and the evidence
Export a catalog CSV and a separate evidence CSV. Keep the project JSON for editable continuity and preserve originals separately. Before sharing, inspect filenames, excerpts and other metadata for information that should stay private.
For a larger batch, agree the attribute dictionary, file and page limits, reviewer, acceptance examples, correction process, price and delivery window before starting a recovery pilot.
Put the workflow to work.
Use the free local catalog to create and review your own manually entered records. No account, upload or automatic extraction. Start with the synthetic example, then choose your own attributes.