demand-intake

A demand letter intake structures parties, triggering events, legal basis, deadlines, and desired outcomes to ensure the final notice is precise and strategically sound.

Drafting a cease-and-desist or breach-and-cure notice requires core posture inputs including parties, the triggering event, legal basis, deadlines, and desired outcomes. Strategic blocks like leverage and settlement posture are collected when full coverage is requested.

You can skip the strategic leverage block during legal intake and still generate an output file. The skip-aware guidance produces an intake document that downstream drafting steps can flag for missing verification gaps and risk calibration details.

Demand letter intake supports preservation demands and employment separation communications. It applies to payment demands, breach-and-cure notices, and related correspondence whenever pre-writing context and structured posture inputs are required.

Organize settlement posture and privilege filters by running a structured intake with full coverage. This captures leverage, BATNA, downside tolerance, and privilege filters, writing a complete intake document to the demand-letters workspace for later drafting.

A demand letter intake needs a deterministic slug and workspace directory for matter-ready output management. This generates a consistent file name and saves the complete intake.md document to the configured demand-letters directory for downstream drafting.