Scope of Work
Precise description of the models to be delivered, software used, polygon counts, texture specifications, revision limits, and how the assets integrate into client systems, including naming and layering conventions.
Use a 3D Modeling Agreement to assign responsibilities, set delivery and acceptance standards, protect intellectual property, and define payment and revision terms. Clear contract terms reduce scope creep, speed approvals, and limit exposure to unpaid work or post-delivery disputes.
Typical parties include freelance 3D artists, boutique modeling studios, architecture and product development teams, and in-house creative departments.
Use this agreement when scope, IP rights, or payment terms must be explicitly defined to avoid later disputes.
Precise description of the models to be delivered, software used, polygon counts, texture specifications, revision limits, and how the assets integrate into client systems, including naming and layering conventions.
Define milestone deliverables, delivery formats (OBJ, FBX, GLTF), sample files, acceptance tests, revision windows, due dates, payment triggers tied to formal client signoffs, and handover documentation.
State whether the creator assigns copyright or grants a license, define permitted uses, sublicensing rights, territorial limits, exclusivity, and the duration or termination of rights.
Specify total fee, milestone amounts, invoicing schedule, deposits, late fees, reimbursement for expenses, tax treatment, and accepted payment methods.
Mutual or one-way non-disclosure obligations covering project files, client materials, proprietary workflows, and any reference assets provided during the engagement.
Limitations of liability, warranty period for deliverable defects, indemnities, caps on damages, and insurance requirements for larger or high-risk projects.
| Workflow Field Name and Purpose | Configuration |
|---|---|
| Automatic file naming convention for versions | Use project codes and dates for file versioning. |
| Conditional field display for revisions | Show revision fields only after failed acceptance. |
| Signer authentication options and strength | Email link by default; SMS code optional. |
| Storage location and retention policy | Save signed PDFs with audit trails in encrypted storage. |
Choose a platform supporting PDF/DOCX input, secure storage, and audit trails for reliable signing and recordkeeping.
| 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, no credit card | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes (Business Premium) | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA available) | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Specifies cutoff for accepting quoted price and terms.
Date contract obligations and milestones commence.
Each deliverable tied to specific payment triggers.
Client has set days to review and approve.
Defines timeframe for defect corrections post-delivery.
Send scope, quote, and proposal acceptance.
Gather assets and confirm technical requirements.
Intermediate deliveries, feedback, and revisions occur.
Client signs acceptance and final files are transferred.