BA-000 Build Arbiter Project Record Health Check
Find the weak points in your construction project record before they become expensive.
Build Arbiter Project Record Health Check is a free 25-question self-assessment designed to help contractors, project managers, subcontractors, owner representatives and construction administrators quickly identify weaknesses in the records they already keep.
Answer based on what your team actually does consistently — not what the procedure says should happen.
The Health Check reviews
• Daily field records
• Evidence and photo control
• RFIs, instructions and drawings
• Changes and delays
• Defects and punch items
• Commercial records and payment control
• Milestones and risk visibility
• Closeout and handover records
How it works
Work through 25 practical YES/NO questions.
Score one point for every YES.
Your score gives you a quick indication of the strength of your current record discipline and highlights where important information may be fragmented, missing or difficult to retrieve.
The guide then points you toward the Build Arbiter control pack that matches the area needing the most attention.
What your score tells you
22–25 YES — Strong record discipline. The opportunity is usually consistency, automation and connected reporting.
17–21 YES — Good foundation with identifiable gaps.
11–16 YES — Material exposure. Important project information is probably fragmented across people, email, photos and spreadsheets.
0–10 YES — High exposure. Reconstructing a change, delay, dispute or closeout position may depend heavily on memory and manual searching.
What to fix first
Weak field records or evidence → Field Record Pack
Weak RFIs, instructions or drawing control → RFI & Submittal Control
Weak change or delay records → Change & Delay Control
Commercial and payment gaps → Commercial Control
Risk, defect or handover gaps → Risk & Closeout Control
Several weak areas → Project Record Pro
The core principle
Record the event. Preserve the evidence. Link the decision. Track the cost and time effect. Close the loop.
Build Arbiter
Record it. Link it. Prove it.