Make “done”
easier to agree on.
Check the scope before the handoff.
Find unclear requirements, plan what to show, and record your review. Start with the work in front of you—no customer history needed.
What needs to be done?
Write one requirement per line. Include the result, how it will be checked, and any limits that matter.
Rules-based analysis, with no paid model calls. Text is processed server-side and is not saved there. A workspace draft is kept in this tab only when you explicitly prepare it. Do not include secrets or confidential personal information. Nothing is submitted to a model provider.
A clearer path to handoff.
Your review changed. Update the check to refresh the summary and guidance.
Questions to settle
Suggested proof plan
One package may cover related requirements. Each requirement still needs its own review.
Requirement by requirement
Keep evidence notes factual. Automatic text screening can flag supported inconsistencies or missing details; it does not inspect files or photos. An unflagged note is not certification. These records stay in this page until you clear it, leave it, or export them; no job is approved or updated.
Prepare these requirements for review in your JobClosure workspace.
Only when you choose this: requirement text is kept in this tab for up to one hour so you can review it in your workspace. Nothing is created or approved automatically. Evidence assessments stay here.