Being an SCM manager, the best answer that I can give you on this question is "it depends". Your list and order of importance of items on the list will depend on your project requirements, language you are using, and developer level.
One thing that you may want to consider to me important (or #1) on ANY list you put together is that the trunk or primary branch of your tool be VERY heavily controlled and only a very select few have access to import or commit changes to it. This will save a ton of headaches at release time.
Items that can be on any list you put together is:
- List itemWhen to check-in (daily, weekly, more often, less often)
- List itemWhen builds are done (daily, weekly, etc.)
- List itemUse of dual repositories (engineering vs production)
- List itemAllow binaries in repository
- List itemAllow third party software in repository
- List itemAll items necessary for build in repository
- List itemWhen imports or commits to trunk are done
- List itemUse one file to export and build
- List itemAllow check-in with/without bug report information
- List itemEnforce check-in comment standards
The list can go on and on depending on your specific requirements, but I think you get the general idea with what's here.