master-agreement-generator

Topics in the source

• Master Agreement Generator
• When to Use
• How It Works
• Template
• Spec
• Role table
• Build
• Signature page geometry

One master template, one small spec per counterparty, one draft build step. The generator always labels output DRAFT, including documents generated from a completed template. A successful conversion proves artifact generation, not legal completeness, authority to contract, or readiness to send or sign. An executed agreement may permit designated opportunities to be added by notice; that authority must be established before using the Schedule A workflow. You issue a framework agreement (NDA, referral or sourcing fee, non-circumvention, master services) to many counterparties with the same terms and a few party-specific fields. Deals are added over time and re-papering each one is the bottleneck. Documents must be reproducible from tracked source, diffable, and free of hand edits. Signature fields are placed by automation and need a stable page layout. A single markdown template with {{PLACEHOLDER}} fields. Every party-specific value is a placeholder; everything else is fixed text. A skeleton lives at references/master-template.example.md. Replace its generic sentences with your counsel-approved clauses. Placeholders the reference script fills: | Placeholder | Source | | --- | --- |

This is an excerpt. Refer to the complete source and its current requirements.