I am creating a template for creating a job description and I was wondering if a template should have a revision history? If so what happens to that history once the template is used for creating a job description?

Do you think it is necessary to track changes to a job description? Does the job description need a revision history?

My reasoning...I think that once a template is used to create a job description it is a record and if that record needs to be replaced then the old record is archived or deleted. I do not really see a need to have history of how a job description changes over time. Does anyone else agree? I want to make sure I am following the ISO standard in setting this up correctly.

I want to make sure I am following the ISO standard in setting this up correctly.

That seems to be the source of your confusion. :D You should determine the mode and extent of document control according to the needs of your company.

Whether or not you control a template (which is a type of form) depends on whether or not you consider it important to prevent users from changing it. This will normally be determined by some sort of policy--i.e., a management requirement--that prescribes the content of job descriptions. Presumably, if one has gone to the trouble of creating a form or template, there is some desire to control the content, so it seems that some level of control of the template is in order. Maybe not, though, depending on your circumstances. Should you decide not to control it, you will probably be called upon at some point to justify your decision.

My organization does want to control templates but will I be called on at some point to show the revision history of the template?

Should the job desriptions just be controlled individually instead of making a template and just add a revision history to those documents allowing for better tracking of the changes?

My organization does want to control templates but will I be called on at some point to show the revision history of the template?

Should the job desriptions just be controlled individually instead of making a template and just add a revision history to those documents allowing for better tracking of the changes?

You're dealing with two different entities: a container, and the stuff inside it. Don't confuse the two. Think of it as the difference between the trash and the trash can. :D The template is the container, and as I suggested before, you may or may not decide to control it (although you indicate now that you will, which is fine). The job description forms the contents of the container, and a separate decision has to be made with regard to control. Personally speaking, if I'm going to control job descriptions, then I'm almost certainly going to want to preserve the history of revisions, and the rationale for them. Again, it's a personal decision and isn't generally affected by the the standard.

Do what makes sense.

I am creating a template for creating a job description and I was wondering if a template should have a revision history? If so what happens to that history once the template is used for creating a job description?

Do you think it is necessary to track changes to a job description? Does the job description need a revision history?

My reasoning...I think that once a template is used to create a job description it is a record and if that record needs to be replaced then the old record is archived or deleted. I do not really see a need to have history of how a job description changes over time. Does anyone else agree? I want to make sure I am following the ISO standard in setting this up correctly.Just for the benefit of others... as has been pointed out here before the other advantage of controlling the template (apart from ensuring consistency) is it reduces the review time of the records generated from it (as only the editable content needs review).

So if you're going to the trouble of controlling the template then it should have a revision, and a revision history is useful. My templates generally use non-printable areas to show their revisions and change history that is preserved in the final record or document, but clearly identified as applying to the template.

On your second question, personally I don't track job description changes explicitly. They have a revision number and previous revisions are obsoleted but still available for historic purposes. The changes could be derived by comparing the old and new, but I've never had a requirement for this. It would probably be evident why a revision occurred from the personnel records.