dovetail.
Let’s talk

THE SPECIFICATION FIELDNOTES

Useful thinking.
For work that gets built.

Practical guides for turning selections into clear instructions, reviewing changes and keeping AI-assisted work accountable.

Review your handoff

FIELDNOTE / SPECIFICATION PRACTICE

What makes a specification
actually complete?

Completeness is not the number of filled-in fields. It is whether the next person has enough verified information to perform their part of the work.

Start with the recipient’s question.

A designer needs to protect the intended composition. A buyer needs the exact orderable item. An installer needs the relevant dimensions and requirements. Structure the record around those different needs, rather than assuming one product image serves them all.

Separate identity from application.

The manufacturer’s product facts describe the item. The project describes where it will be used and how it relates to other decisions. Keep both visible. An item suitable for one room is not automatically approved for another application.

Make missing information explicit.

“To be confirmed” is more useful than a plausible guess when the answer controls procurement or installation. Add an owner and a next question so the missing detail is a manageable task, not a hidden risk.

Close the handoff deliberately.

Check revision, approval status, outstanding items and recipients before issuing. An attractive schedule should not conceal the fact that a finish sample or installation detail is still awaiting review.

FIELDNOTE / COORDINATION

One change rarely
stays in one field.

A useful change review asks what else depends on the selected item, which records need updating and who must approve the result.

Define exactly what changed.

Record the old value, proposed value, reason and source. Avoid vague instructions such as “use the new one” when several documents or variants exist.

Trace the adjacent decisions.

Review linked selections, quantities, installation details, supplier questions and budget assumptions. This is a coordination exercise; qualified professionals still determine technical suitability.

Separate a request from an approval.

A client request, supplier suggestion and approved instruction are different records. Keep those states distinct so an unresolved proposal does not become an accidental purchase.

Issue the difference, not just the file.

A concise change summary tells each recipient which items changed and which previous information is superseded. Keep a record of the revision included in that handoff.

FIELDNOTE / RESPONSIBLE INTELLIGENCE

How to review
an AI-assisted finding.

A well-written explanation can still rest on an outdated document or an untested assumption. Review the basis as carefully as the answer.

Open the source.

Check that the cited information exists and belongs to the selected product variant. Verify the units, page context and revision. Missing source context is a reason to ask another question.

Check the type of claim.

An observation, an inference and a recommendation should not be interchangeable. “The dimensions differ” is an observation. “This will fit” requires more evidence.

Recalculate numerical comparisons.

Check the quantity, unit price, included costs and calculation. Keep deterministic arithmetic separate from language-model explanations, especially when a comparison affects purchasing.

Keep a human release point.

Use AI to prepare a brief, proposed update or supplier question. The authorized project team should decide whether the change is approved and ready to issue.

BEFORE THE NEXT ISSUE

Would your next handoff
pass a clarity check?

Use this practical checklist to review an example specification process. It is a preparation aid, not a compliance or project-approval tool.

YOUR PROCESS REVIEW0 / 8

Select the practices your process currently includes.

No project information is uploaded.

DESIGN FORWARD. BUILD WITH CLARITY.

Leave nothing
to interpretation.

Bring us a room, a spec sheet, or a process you want to improve.
Let’s talk about what better coordination could look like.

Start a conversation