Scope
Define grapes, parcels, vintage years, production volumes, and specific processes covered. State whether the agreement covers a single vintage or ongoing production to prevent scope creep.
A written Wine Project Agreement reduces ambiguity by recording expectations, financial contributions, quality criteria, and distribution of proceeds. Clear terms protect contributors, help manage operational risk, and provide an evidentiary record should disputes or regulatory reviews arise.
Typical parties include vineyard owners, winemakers, investors, and distributors collaborating on a defined wine project.
Confirm each party's role, capacity to contract, and attach exhibits that document contributions, schedules, and payment mechanics for clarity.
The winery or vineyard owner provides land, grapes, or facility access and warrants title and capacity. They must disclose encumbrances, comply with agreed cultivation and delivery schedules, and often accept specific quality and testing obligations tied to acceptance and payment.
The project manager coordinates harvest, production, and logistics, enforces quality checkpoints, keeps project records, and communicates with stakeholders. They typically have authority to approve samples, trigger production stages, and notify parties of schedule changes.
Define grapes, parcels, vintage years, production volumes, and specific processes covered. State whether the agreement covers a single vintage or ongoing production to prevent scope creep.
Clarify title to bulk wine, finished bottles, and intellectual property, including label and recipe ownership. Specify transfer triggers, custody during storage, and inventory accounting methods.
Detail capital contributions, per-case fees, revenue splits, cost reimbursement, payment timing, and penalties for late payments or shortfalls to avoid misunderstandings.
List sensory criteria, lab tests, sampling methods, and acceptance thresholds. Include procedures for failed lots and remedies such as rework, blending, or price adjustments.
Set the effective date, project duration, renewal terms, termination events, cure periods, and handling of inventory and unsold wine after termination.
Specify governing law, forum, and whether mediation or arbitration is required. Include allocation of fees and the process for provisional remedies when necessary.
| Field | Configuration |
|---|---|
| Authentication | Email with optional SMS code; KBA for high-risk transactions |
| Signing Fields | Signature, initials, dates, conditional exhibits when milestones complete |
| Routing | Sequential routing with reminder emails every three days |
| Storage | Secure PDF with audit trail and tagged folder |
Digital signing and storage choices affect enforceability, chain-of-custody, and long-term recordkeeping for Wine Project Agreements.
The date parties agree; starts obligations and deadlines
Specify harvest start and completion dates per vintage
List due dates, milestones, and late payment consequences
State required days for breach notices and cure periods
Specify where executed copies, invoices, and logs are stored
| Criteria | Wine Project Agreement | Standard Purchase Agreement |
|---|---|---|
| Typical Purpose | joint production | sale of goods |
| Notarization | optional | rarely required |
| IP Assignment | often included | usually not included |
| Revenue Sharing | one-time payment |
A landowner supplies grapes and a winemaker provides production services for a single vintage
An investor funds equipment upgrades in exchange for a share of finished bottles
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | Yes |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |