SFSPL Global · Legal
Service & Project Terms
A structured framework for scope, delivery, client dependencies, change, review, acceptance, handover and post-delivery support.
Reviewed 9 August 20261. Scope baseline
The accepted statement of work defines deliverables, formats, quantity, functionality, milestones, exclusions and intended use. References or examples describe direction unless expressly adopted as acceptance criteria.
Project assumptions should be recorded. If a material assumption proves incorrect, the parties will review the impact through change control.
2. Timeline and dependencies
Dates are planned from agreed commencement and remain dependent on content, access, feedback, approvals, third-party availability and payment. A dependency delay can move subsequent dates.
Where a fixed external deadline exists, it must be identified before acceptance and confirmed in the scope. SFSPL Global will not represent an unconfirmed timeline as guaranteed.
3. Content and instructions
The client is responsible for the accuracy, completeness, rights and legality of supplied content and instructions. SFSPL Global may identify visible issues but does not independently audit every factual or legal claim unless that review is included.
4. Revisions and changes
Included revisions apply to refinement within the approved direction and scope. A new concept, changed objective, additional page, feature, integration, format, language or volume may be additional scope.
Feedback should be clear, consolidated and provided by the authorised reviewer. Conflicting instructions may pause the affected work until resolved.
5. Testing and acceptance
Where testing applies, the parties will review the deliverable against documented requirements. A defect is a reproducible failure to meet an agreed requirement; a new preference, capability or altered requirement is a change request.
Acceptance does not remove any specific written warranty or mandatory right. It confirms that the reviewed stage is approved for the next agreed action subject to recorded issues.
6. Handover, support and maintenance
Handover content depends on scope and may include final files, access, documentation or deployment. Third-party accounts and licences remain subject to provider terms.
Support after handover is limited to the included period and scope. Ongoing maintenance, updates, hosting administration, content changes or enhancements require a separate arrangement unless included.