One of the most important practices we have at SmallBizTracks is starting things out with a Scope Document.
Whatever level (size of project) or track (type of project), “The Scope” starts the project off on the right foot, keeps the project on “track”, and serves as a check list to know when to modify and when the task is complete.
The outline below is written in a format similar to our scope document, just to give an idea of what our scope document format looks like (not a specific track or model):
- Initial Consult
- Phone, Skype, or In-Person conversation
- Inquiries re: Short-Term and Long-Term goals
- Data Points, i.e., Timeframe, Resources, Conviction level
- Scope Document
- Draft and Delivery of Scope Document and Specifications
- Questions or Modifications
- Acceptance of Scope Starts the Project
- Project Invoiced, Payment Held in Escrow Until Project Complete
- Project Work
- Scope becomes Checklist
- Modifications Become Subject to Possible Additional Charges
- At End of Work, Customer uses Scope as “punch list” to completion
- Next Track
- At completion of project, a “Next Track” document is delivered
- Suggestions are made as to potential Improvements
- Some will be suggestions with current track
- Some will be suggestions on other tracks within business model
- Referrals and Reviews
While it would seem that only the Master Level projects would require a document like this, the “scope” serving as a checklist protects all parties, including potential outsourced contractors.
A scope document also acts as a box, of sorts. We can still think outside the box – it’s encourage all parties involved do so, but at least we always know where the box is and what it contained should we get lost in practice or purpose.
We look forward to creating a scope for your project soon.