These two recordings are publisher-hosted workshops, not verified YouTube listings.

They are included separately because their accessible transcripts address documentation and scoping directly.

12. How should teams distinguish the scope from the estimate?

Title: Rethinking Scoping & Estimating: A Better Way to Understand Loss
Watch/read: Recording and transcript
Who: David Herring, founder of WriteLoss, with Jeff McDowell, identified as Encircle’s chief product officer.
Date: Recording date not established on the reviewed page.
Evidence basis: Publisher transcript and learning objectives.

Key takeaways: the workshop argues for describing the actual loss before reducing it to estimate line items. Its published objectives address supporting evidence, repeatable staff habits and technology that assists documentation rather than substitutes for understanding. (getencircle.com)

Desk application: add a scope-quality check before estimating begins. Require a reviewer to explain the affected areas and proposed work from the evidence, without relying on the priced estimate to supply the story.

Buying question: “Are we buying accurate translation of an established scope, or asking the production supplier to infer the scope from incomplete material?”

Caution: this is a vendor-hosted, restoration-oriented session. Its workflow advice is not a universal carrier standard or proof that a particular software product improves acceptance.

13. How can a file make sense to someone who never visited the loss?

Title: Beyond Text: Building a Bulletproof File
Watch/read: Recording and transcript
Who: David Herring, identified as founder of RiseDocs and WriteLoss; hosted by Encircle.
Timing: June 2026; Herring’s 19 June recap refers to the preceding week’s workshop. The exact event date was not established.
Evidence basis: Publisher transcript, learning objectives and speaker recap.

Key takeaways: the session covers organised photographs, narrated walkthroughs, floor-plan tools and questions for AI suppliers. Its transcript discusses turning recorded observations into narratives and testing AI outputs for consistency. (getencircle.com)

Desk application: ask a reviewer unfamiliar with the property to reconstruct the loss using only the submitted package. Require generated narrative statements to be traceable to supplied evidence, and test repeated outputs for material factual differences.

Buying question: “Can we distinguish what was observed, what was inferred and what remains unknown?”

Caution: “bulletproof” is the publisher’s title, not a guarantee. Output consistency is also not sufficient proof of accuracy; your pilot should test both separately.