1. SOW - Key Points
FS-020 Ver 2.1 (Aug 23)
Reference Templates:
Food Services Sample SOW for Coffee Kiosk
Food Services Sample SOW for Food Services
Food Services Scope and Population Matrix
Food Services SOW and Scope Matrix
Food Services Standard CBRE Office Coffee Vending SOW for RFP
Food Services Standard CBRE MSA SOW for RFP
2. Useful Links
A well-engineered SOW defines the Food service delivery program elements that are within scope as well as those out-of-scope.
What should be covered by the SOW?
The SOW should cover all Categories defined for each service and all LOB
The SOW summarises:
- The services to be performed
- The Service Level Agreement parameters
- Relevant KPIs to be performed to
- Capex requirements
- Legal Liabilities
- Level of reporting requirements
- Key personnel required and their engagement
When do I need to issue the SOW ?
This can vary from project to project. SOW should be issues as part of the RFP process
6-12 months in advance of Go-Live
REFER TO THE BID PROCESS GUIDELINE TO PROVIDE DETAILS ON THE SEQUENCING OF EVENTS
CLICK HERE to access BID process Guideline
Should cover all sub-service line categories defined for each service / sub-service line within the scope of the client contract
The SOW summarises the service definition and includes relevant aspects to capture the essence of the service requirement, further detailed through the Service Level Agreements (SLA’s)
The SOW must be finalised and documented in advance of contract Go-live or renewal and should be aligned to the SOW detail within the client contract
Transition or supplier contract renewal should be treated as an opportunity to redefine the SOW, addressing scope-creep or service evolution issues at the time through the documenting of revised and a representative SOW