Field note / Evaluation method
What to test during a final-beta contractor software evaluation
A bounded evaluation built around real records, failure paths and the people who own each handoff.
Published 2026-08-15 · public evaluation material
Section 01
Choose a representative record
Use a job your team already understands. Include at least one exception: changed scope, weather delay, missing document, duplicate lead or disputed measurement. A flawless sample cannot test refusal and recovery.
Section 02
Write acceptance criteria first
Name the handoffs that must work, the evidence that must stay attached, the person who owns each gate and the current cost or time baseline. At the end of the trial, compare the record—not the quality of the demo.
Final beta · applications open
Use the note on one real job.
We are accepting roofing operators who will test one real workflow, tell us where it breaks, and help shape the production release.