Draft template
Onboarding Statement of Work
A reusable implementation scope for configuration, migration, training, and go-live.
DRAFT TEMPLATE — NOT LEGAL ADVICE. This document has not been approved by an attorney. It must be reviewed, completed, and approved by qualified counsel before CatOps or any Client signs it or relies on it.
Bracketed fields require a business decision or verified fact. Do not remove this notice or present this document as final until counsel has approved it and CatOps has verified every operational and security statement.
Project Overview
CatOps will configure the subscribed service for [Client] at [facility] and assist with the agreed initial workflow. Project dates are estimates dependent on Client cooperation and data quality. Project kickoff: [date]. Target go-live: [date].
CatOps Deliverables
- Workspace and subscribed feature configuration.
- Configuration workbook covering Clients, users, roles, locations, units, items, products, and agreed workflows.
- Import of [one] approved source file after validation and Client signoff.
- Administrator training and [number] operator-training sessions.
- Workflow validation for [receiving-to-production-to-shipping / defined workflow].
- Go-live checklist and [number]-day stabilization review.
Client Responsibilities
- Provide a project owner with decision authority and appropriate subject-matter experts.
- Complete templates, clean source data, make users available, and respond within [two] business days.
- Validate imported totals, mappings, opening balances, permissions, feature access, and representative workflows before go-live.
- Maintain source records and backups until written acceptance of the migration.
- Provide secure access to data; do not transmit credentials or confidential files through unapproved channels.
Assumptions and Exclusions
The SOW assumes one facility, standard CatOps configuration, one source dataset in the supplied format, and remote delivery unless stated otherwise. Data cleansing, integrations, custom development, regulatory advice, hardware installation, label design, network work, and additional migration cycles are excluded unless added through written change control.
Acceptance
A deliverable is accepted when Client confirms acceptance or does not identify a material failure against the written acceptance criteria within [five] business days. CatOps will correct reproducible material failures within scope. Preferences, new requirements, and source-data errors are handled through change control.
Change Control and Fees
Either party may request a change. CatOps will document the scope, schedule, fees, dependencies, and effect on existing commitments. No change is authorized until both parties approve it in writing. Fees: [fixed implementation fee / rates].
Signatures
This SOW is governed by the parties’ SaaS Subscription Agreement and applicable Order Form. CATOPS: [signatory, title, signature, date]. CLIENT: [signatory, title, signature, date].