Exhibit A Sacramento County Sample Contract
What the Exhibit A Sacramento County Sample Contract Is
Why Include an Exhibit A in a Sacramento County Contract
Use the Exhibit A Sacramento County Sample Contract to ensure clear, consistent scope and payment terms, reduce negotiation cycles, and document compliance with county procurement and insurance rules. It helps align expectations between the county and vendors and supports audit-ready recordkeeping.
Who Typically Prepares and Signs Exhibit A
Primary users include county procurement officers, project managers, and external contractors preparing exhibits for county agreements.
- County procurement and contracting officers managing vendor agreements and attachments.
- Project managers specifying deliverables, milestones, and acceptance criteria for services.
- Vendors and subcontractors completing scope, pricing, and schedule details for contract execution.
Stepwise Process to Prepare and Attach Exhibit A
-
01Draft: Populate scope, schedule, compensation, and attachments.
-
02Review: Legal and procurement review for compliance and clarity.
-
03Approve: Obtain signatures from authorized county and vendor signatories.
-
04Attach: File Exhibit A as an attachment to the main agreement record.
How Exhibit A Moves Through County Review and Approval
-
Upload: Attach signed Exhibit A to procurement portal or contract repository.
-
Route: Send to contracting officer and department approver via email.
-
Sign: Authorized parties sign; e-sign compliance should be documented.
-
Archive: Store final PDF and retention metadata in county records.
Recommended Digital Workflow Settings for Exhibit A
| Field | Configuration |
|---|---|
| Signing authentication and identity verification | Email link with optional SMS code; consider KBA for high-risk |
| Document retention and archival settings | Retention metadata tags, PDF/A archival, and access controls |
| Signing order, roles, and delegation | Role-based signer sequence with delegation rules and reminders |
| Notification, reminders, and tracking settings | Automatic emails on status change and completion certificates |
Technical and Integration Requirements for eSubmission
Confirm technical requirements for eSubmission, file formats, and signer authentication to ensure compatibility with county systems.
- File formats: PDF/A preferred; DOCX accepted for draft.
- Authentication: Email link, SMS, or multi-factor authentication
- Integrations: Works with procurement systems and document repositories
Key Submission Deadlines and Processing Timeframes
Submission Deadline:
Follow the contract-specified submission date to avoid late acceptance.
County Review Period:
Allow typical county review time of 14–30 business days.
Invoice Processing Time:
County payment cycles often pay within 30–60 days post-approval.
Insurance Proof Deadline:
Provide current insurance before work commencement or per contract.
Amendment Processing:
Allow 10–20 business days for formal amendments to be approved.
Milestone Timeline for Exhibit A Preparation and Archival
Draft Completed
Finalize scope, pricing, and attachments before submittal.
Internal Review
Legal and procurement validate terms and compliance.
Signatures Obtained
Authorized county and vendor signatures executed and dated.
Record and Archive
Store executed exhibit in contract repository with metadata.
Comparing Exhibit A with a Statement of Work
| Document Type | Exhibit A | Statement of Work |
|---|---|---|
| Purpose | scope & terms | detailed tasks |
| Binding Status | attachment to contract | attachment to contract |
| Detail Level | high-level | task-level detail |
| Modification | amendment required | amendment preferred |
eSignature Vendor Pricing and Feature Snapshot for Exhibit A Execution
| 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 vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| 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 | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Illustrative Examples of Exhibit A in Practice
Public Works Project
A county public works department used Exhibit A to specify scope, milestone dates, and retainage terms for a bridge repair contract.
- Clear milestones avoided payment disputes and inspection delays.
- By attaching detailed acceptance criteria and insurance requirements, the county reduced change orders, sped up inspections, and ensured contractor compliance with prevailing wage and bonding requirements, making audits straightforward and reducing fiscal risk across the project lifecycle.
Health Services Agreement
A county health clinic included Exhibit A to list deliverables, patient consent language, and data handling standards for a contracted vaccination outreach program.
- Explicit PHI handling reduced compliance risk.
- Including HIPAA-required clauses and specifying encryption, audit logs, and BAA terms allowed rapid approval, ensured proper storage of signed records, and met county reporting requirements while providing clear obligations for vendors handling protected health information.
Best Practices to Speed Approval and Reduce Risk
Common Preparation Pitfalls to Avoid
- Ambiguous deliverables or acceptance criteria that leave interpretation to reviewers and cause disputes, rework, and invoice rejections.
- Using inconsistent party names or abbreviations across sections leads to mismatched signatures and tax reporting problems with county finance.
- Failing to attach required insurance, licenses, or prior approvals causes administrative holds and may delay contract execution for weeks.
- Incorrect dates, missing signatures, and failure to specify payment milestones are frequent causes of vendor payment disputes.
Penalties and Risks of Inaccurate or Incomplete Exhibit A
Frequently Asked Questions About Exhibit A
-
Can Exhibit A be signed electronically under ESIGN?
Yes. Electronic signatures are legally recognized under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and record retention requirements are met. Exceptions such as wills and certain court filings may still require wet ink or notarization.
-
Who must sign Exhibit A and how is authority verified?
Signatories must be authorized representatives: a county contracting officer or authorized designee and a vendor signatory with corporate authority. Verify delegated authority, purchasing thresholds, and any board or department approval that may be required before execution to ensure enforceability and timely payment.
-
Is notarization required for Exhibit A execution?
Notarization is not routinely required for Exhibit A unless the primary agreement or state law specifically demands it, or the exhibit contains acknowledgments or powers requiring notarization. If a notary is required, confirm Sacramento County guidance and whether Remote Online Notarization is acceptable.
-
How should completed Exhibit A be submitted to the county?
Submit Exhibit A per the contract's routing instructions: usually to the county contract administrator, procurement portal, or assigned email. For electronic submission, include the signed PDF/A, attachments, and certificate of completion. Follow any county file-naming and metadata requirements to ensure proper tracking.
-
What common errors cause processing delays?
Mistakes include mismatched legal names or tax IDs, missing insurance certificates, ambiguous or incomplete scope of work, omitted signatures or dates, incorrect billing instructions, and failure to attach required supporting documents. Each can trigger review cycles and payment or compliance delays.
-
How can errors be corrected after submission?
If you discover errors after submission, notify the county contract administrator immediately, submit a corrected Exhibit A with a dated amendment or replacement signature page, and document the change. Significant modifications may require formal amendment, approval, and updated insurance or compliance evidence.