What Proofstead can review vs. what must be documented in workspace

What Proofstead can directly review or unblock

The repo already shows a few classes of issues that genuinely depend on Proofstead review or intervention: homeowner claims, contractor disputes, blocked contractor verification, restricted or failed payout handling, checkout failures, and account-access or security issues.

Those are workflow-level problems. They are about review, status, or unblockers that the app itself cannot finish without the right team stepping in.

What still has to live in the workspace first

Support cannot replace the job record. If the question is about what work was approved, what changed, what the closeout record shows, what the invoice line means, or what condition the photos document, those facts still belong in the workspace first.

That is true even when the next step becomes a claim, a dispute, or a support escalation. The workspace is where the evidence stays legible for everyone reading the case later.

• +The exact scope item, change order, or charge being questioned
• +Before and after photos or current condition photos when they matter
• +Timestamps, notes, and the specific outcome you want reviewed
• +Any closeout or invoice context already shown in the job record

How to escalate without losing the thread

Use the built-in claim or dispute path when the job is already at the right stage for formal review. Use direct support when the blocker is about access, verification, payouts, checkout, or a review path that still needs manual follow-up after the documented record is already in place.

That sequence keeps the facts, the workflow, and the support request aligned instead of forcing the team to reconstruct the job from separate channels.