*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
Procedure Number: | Related Processes and Procedures: |
All text in "blue" should be removed from this document prior to release as final draft.
Revision History
Date | Author | Version | Description | ||
5/6/11 | Jon Atherton | 0.0 | New Document | ||
|
|
|
| ||
5/6/11 | Jon Atherton |
| | 0.9 | Final Draft |
|
| 1.0 | Approved Document | ||
|
|
|
|
...
(What is in scope and what is not in scope for this procedure?)
Describe the situation or problem or specific deliverables applicable to this standard operating procedure.
(This is a required section for this document.)Each hosting customer must update contact information and account number at the fiscal year boundary.
CARD (Contingencies, Assumptions, Requirements, Dependencies)
(Indicate contingencies, assumptions, requirements and dependencies not indicated elsewhere which are required for execution of this procedure.)
Any relevant Contingencies, Assumptions, Requirements or Dependencies should be included.
- Contingencies describe "what if" scenarios and how to accommodate them.
- Assumptions are things which are presumed to be valid or true. Many assumptions will have a risk related to them.
- Requirements are items which are necessary in order to successfully execute this procedure.
- Dependencies are related items which depend on this procedure. Alternatively, the converse may also be relevant.
(If this section is not required, indicate "Not Applicable" rather than removing this section from the document)Assumption: We will continue to bill for custom support and CommonSpot, otherwise an account number would not be necessary.
TASK DESCRIPTION
Provide a description of the individual tasks which constitute the SOP. Flow chart diagrams may be included for clarity.)
...