/ Free Working Demo · No Login

Build a project-basis readiness record before technical review starts.

Use this screen to separate confirmed project inputs from assumptions, identify missing evidence, assign the next verification, and create a concise record for a review note, meeting agenda, or information request.

Privacy and purpose: your entries stay in this browser tab and are not sent to MasterBuild. Do not enter confidential, personally identifying, export-controlled, or privileged project information. This is a documentation-readiness screen—not a code-compliance, permit-approval, design-sufficiency, or professional-responsibility determination.

Field evidence quality: what should be captured?

Governing basis

Identify the jurisdiction, enforcement authority, adopted edition, local amendments, project phase, and exact review boundary. A familiar code is not automatically the adopted project basis.

Source currency

Record document title, issue status, date, and revision. For equipment, identify the exact model, listing data, and applicable installation instructions—not a similar product.

Field observation

Record location, date, observer role, visible condition, access limits, and cross-referenced photos or measurements. Keep observation separate from inference and required verification.

Responsibility and closure

Assign each open item to a responsible role with a timing or dependency. An unresolved assumption must remain visible until evidence supports closing it.

Project Basis + Evidence Readiness

Create the record

Required fields protect the minimum basis needed to start a bounded review. Use an anonymous project reference if you want to distinguish this record.

1 · Define the review basis

Project reference Optional

Project type, use, and phase Optional

Jurisdiction / authority having jurisdiction (AHJ) status Required

Adopted code, edition, and amendment basis Required

Defined review scope Required Decision or question the review must support Required

2 · Identify evidence and responsibility

Source-document status Required

Existing-condition status Required

Responsible reviewer status Required

Responsible role Optional

Evidence or source notes Optional Open assumptions and unknowns Optional Next required verification action Required

Responsible party or role Required

Due date, trigger, or dependency Required

3 · Evidence-control check

Check only what is supported by a current record. An unchecked item becomes a documented gap in the output.

Jurisdiction and authority having jurisdiction are identified. Adopted code edition and local amendments were checked. The current drawing, document, issue status, date, and revision basis are identified. Existing-condition evidence, access limits, or non-applicability are documented. Manufacturer, listing, or source documents are identified, or non-applicability is documented. Owner, client, and authority criteria are identified, or non-applicability is documented. A responsible reviewer is assigned for the stated boundary. The next verification owner and timing or dependency are stated.

Documentation-Readiness Result

This status is generated only from your self-attested entries. Copy or print the record before closing or reloading this tab.

Copy-ready record

Request founding access — no charge

TXT downloads stay on your device. The demo does not upload the record.

Need an actual project decision?

When the answer depends on drawings, field conditions, adopted requirements, calculations, or professional responsibility, request a separately scoped PE-led review.

Discuss the project review

See the planned Field Tools membership Browse current guides