FDE acceptance, assurance and support
Accept identified revisions, verification evidence and handover; agree service targets in writing.
How delivery assurance works
FDE projects document scope, milestones, verifiable acceptance and issue handling in the SOW. Evidence includes actual execution, access validation and handover materials. Customers review work at checkpoints, raise in-scope issues and verify fixes before acceptance. Support periods and response targets require agreement.
Recommended acceptance checks
Agree samples and pass conditions before implementation. Record revision, tester, date, evidence and decision at acceptance. Measure performance, capacity and quality thresholds for the actual workflow.
| Dimension | Check | Evidence |
|---|---|---|
| Business flow | Normal/exception cases, approval and final output | Task/output revisions and owner approval |
| Access and data | Allow, deny, revoke and data scope | Test identities and redacted records |
| Cost and performance | Agreed volume, time, cost and concurrency | Measurements and conditions |
| Failure and recovery | Disconnection, retries, deduplication, backup and rollback | Drill records and remaining limits |
| Documentation and handover | Configuration, manuals, code and training | Asset list and admin drill confirmation |
Handling failed acceptance
Classify in-scope defects, missing inputs/environments, provider failures and new requirements. Fix defects against the original criteria and rerun checks. Agree whether unresolved critical issues block acceptance; estimate new requirements separately. The customer signs acceptance and exceptions. Contracts define review periods and disputes, with no website-imposed automatic acceptance.
Defect cover and maintenance
A discussion starting point is 30 calendar days after acceptance for reproducible in-scope defects in the agreed environment and revision. The contract defines duration, remediation and allowance. New features, data rework, provider API upgrades, customer modifications and new environments require maintenance or change assessment. Confirm renewal or ownership before cover ends.
Response targets and support hours
The following are negotiation references, not an active SLA. Response means acknowledgment and next steps, not completed repair. Agree timezone, business days, channels, escalation contacts and excess charges. Assess 24/7 coverage separately.
| Severity | Example | Illustrative first response |
|---|---|---|
| Critical | Critical flow unavailable or ongoing incorrect writes | Within 4 hours during agreed support hours |
| Standard | Partial disruption with a workaround | 1 business day |
| Advice and improvement | Configuration questions or nonblocking improvements | Acknowledge and schedule within 2 business days |
Purchasing ongoing support
Options include monthly person-day allowances, work-hour bundles or per-incident support. Specify checks, upgrades, integration repairs, training and workflow optimization. Report usage, issues and residual risks; agree an estimate before exceeding allowance or adding scope. Support does not automatically guarantee provider uptime, model accuracy or business results.