Navigating Service Procurements at UCSF

group_of_employees_in_meeting

Navigating Service Procurements at UCSF

Service procurement breakdown brought to you by Tina Stugart, SCM Procurement Supervisor and Laura Morsony-Wilson, SCM Response Team Analyst. 

Service procurement is the process of acquiring services—such as consulting, technical support, or professional expertise. Services are intangible and require careful documentation to ensure both parties understand and meet the agreed-upon outcomes, minimizing risks and ensuring compliance. 

Navigating the Process at UCSF

At UCSF, procuring services is a fundamental part of operations, but it differs significantly from purchasing tangible goods. The service procurement process typically requires more detailed communication and negotiation.  

This series of articles will introduce key concepts in service procurement, focusing on its unique aspects, the various types of services you may encounter, and the importance of careful documentation to avoid pitfalls and reduce risk to UCSF. 

Article topics will feature:

Types of Services 

We will introduce three common categories of services at UCSF—Personal, Consulting, and Professional Services—each with distinct procurement requirements. Understanding the nuances of these service categories will help guide your decisions throughout the procurement process. 

Producing a Statement of Work 

Services require a Statement of Work (SOW), a critical document outlining the scope, expectations, deliverables, and completion timeline. The SOW helps reduce risk by ensuring both parties are aligned, preventing misunderstandings and potential legal or financial issues. A well-crafted SOW is vital to ensure mutual understanding between UCSF and the supplier. We’ll share some fundamentals and look at key aspects of a well-crafted SOW. 

Common Stumbling Blocks, Supplier Guidance, and Support 

This will include tips on finding service suppliers and ensuring compliance.

 

Stay tuned for more insights in upcoming articles.

 

Questions about this article? Contact SCM Response Team