Introduction

Scoping is the process of defining the specific requirements of a given task or project. This should include a clear list of responsibilities for the the consultant and the customer. Any standard contract wording should include a section that specifically states that anything not explicitly covered in the "in-scope" section is expressly out of scope. Never double-cover terms of service, as it can lead to loopholes.

Example 1

Overview of Engagement

Describe the main purpose of the engagement and items or tasks which are directly related.

Scope of Engagement

List of specific, distinct tasks. Do not be vague or assume anything. State everything clearly.

• Install and configure ____
• Configure ____ to enable ____
• Configure ____ to allow for ____
• Provide concurrent training of select staff members (identify who)

Success Criteria

List of desired results which customer says will confirm success.

• ____ will enable use of ___
• ____ will allow for control of ___
• Requirements of ____ will be in full compliance

Responsibilities

List of preliminary, ongoing and completion tasks which are the responsibility of the consultant (you) and the customer, as well as any third-party interests (vendors, service providers, contractors, etc.)

• Software and licensing
• Accounts and Access grants
• Equipment
• Network access
• Building / facility access
• Workspace (if working on site) or VPN (if remote)
• Background security checks, badging, etc.

Terms of Acceptance

"Any tasks or activities not explicitly stated in the 'Scope of Engagement' section are out-of-scope for this engagement. Any tasks or activities which are identified as having an impact on this engagement, which are not included in the 'Scope of Engagement' section, which affect schedules, resources or staffing, will be addressed with a separate Change Order."