Version control systems should be used by those who edit files. This is a broad generalization, but is largely true. There is some effort and learning on the part of the user necessary to utilize a version control system, however it is worth the effort. There are many tasks that do not require the use of a version control system, and even more that make it ridiculous.

However, those who require or find themselves maintaining multiple versions of files, or needing to track the revision of files should seek the rewards of using a version control system. This is especially the case for those with release-critical tasks including writing, publishing, engineering, and software development. Being able to record, track and report changes in your work is a powerful asset for any discipline.

Version control systems can aid group development projects. If one individual breaks or makes a poor modification to a file, an older version of that file can be retrieved. File locking (see section on file locking) can enforce multiple people editing a single file. Further, version control systems usually provide a way to merge two versions of a file, so that if two individuals edit the same version of file, there is still a chance the modifications can be combined.

Version control systems, including the Revision Control System (RCS, were developed for and created by software programmers. They have provided sometimes awkward and specific tools for version control. For instance, version control systems assume they are working with text, and assume that changes are made on a line-by-line basis. However, recent version control systems, including RCS, are able to operate on a range of file formats, including binary files.

The greatest rewards of using a version control tool like RCS do not come from the rudimentary task of using the tool to store revisions, but come from having used such a tool. The reward of having used RCS appears when you accidentally lost your work, made a change that would have otherwise required you to start completely over, wish you had documented the changes you made to a file, or recognized the consequences of a change made long ago. Of course RCS provides a means of providing short-term revisions of files, but the true benefits of RCS are seen by investing in regular use of RCS.

Stand-alone version control utilities like RCS have largely been disregarded by group development projects favoring other version repository systems. These other tools often provide network available repositories allowing individuals to submit versions of files over a network (like the Internet). Some version control systems (which actually utilize RCS for low-level operations) also are complicated with numerous features that make learning impossible and small common tasks difficult. RCS however provides a stable and well accepted system for versioning your computer work. Individuals who have smaller-scale independent tasks can benefit from using RCS.