FDE scope, deliverables and responsibilities
Define discovery, implementation, handover, customer inputs and change control.
Agree a statement of work
Each statement of work defines workflows, systems, environments, data scope, deliverables, samples, owners, milestones, budget and dependencies. List read, write, send, deploy and migration permissions separately. The modules below are available to scope; the project agreement defines what is included.
Delivery modules
FDE work centers on an independently reviewable business cycle. New data sources, environments or systems require added effort and acceptance scope.
| Module | Work | Deliverable |
|---|---|---|
| Discovery and design | Interviews, process map, data/access inventory and feasibility | Scope, design, risks and estimate |
| Team and knowledge setup | Roles, skills, briefs, knowledge cleaning and sampling | Configuration, samples and maintenance rules |
| Integration and adaptation | API/MCP/authorized-tool adaptation, mapping and errors | Agreed adapter code, interface guide and integration records |
| Deployment and verification | Environment setup, access tests, evaluation and recovery drill | Deployment inventory, test report and rollback steps |
| Training and handover | User training, admin drill and issue review | User/run manuals and issue/asset registers |
Bound data preparation
Agree formats, volume, quality assumptions, transformations and sampling. Routine formatting may be included. Large-scale OCR, historical data repair, master-data rebuilding and cross-system reconciliation need separate work packages. The customer resolves business definitions and conflicts; engineers retain transformation and exception records.
Work requiring explicit scope
Round-the-clock support, unlimited changes, hardware, third-party licenses, full-company migration, transfer of general product source code and external platform approvals require explicit scope. Customer approvers own payment, contracting and publication decisions. Validate model outputs against samples; unconditional accuracy and fixed business returns are not promised.
Customer inputs and dependencies
The customer supplies test environments, authorized accounts, samples, system contacts and timely decisions. Missing APIs, network access or internal approvals can change the schedule. The delivery team documents blockers, alternatives and cost effects; both parties agree milestone changes and how waiting time is charged.
Changes, assets and exit
Use a change order for additional workflows, write access, concurrency, environments or acceptance goals, documenting deliverables, effort, price and timing before execution. Contracts distinguish customer data, configuration, custom code, general components and third-party licenses. Agreed source-code handover includes build instructions and dependencies.