S
You've been offered plenty of forms, so I'll offer a perspective instead:
As you develop the form you end up using, determine whether QA will actually be filling in the entire form, or if the requester will be filling in the form -the ideal design and behavior of a form used primarily by QA might be different than the ideal design and behavior of a form used primarily by other staff.
Also, do you plan to have it filled out on paper and sent around, or do you plan on having any of the information entered on the computer? That difference can dramatically affect how you organize the form, if you are trying to design it intuitively.
Prior to my current position, I worked on a document management system that was part spreadsheet/part paper, which got pretty unwieldy sometimes, and now I'm working on implementing a new automated system. If you make the form and the process as easy to use as possible, you get fewer mistakes and fewer audit problems down the road.
As you develop the form you end up using, determine whether QA will actually be filling in the entire form, or if the requester will be filling in the form -the ideal design and behavior of a form used primarily by QA might be different than the ideal design and behavior of a form used primarily by other staff.
Also, do you plan to have it filled out on paper and sent around, or do you plan on having any of the information entered on the computer? That difference can dramatically affect how you organize the form, if you are trying to design it intuitively.
Prior to my current position, I worked on a document management system that was part spreadsheet/part paper, which got pretty unwieldy sometimes, and now I'm working on implementing a new automated system. If you make the form and the process as easy to use as possible, you get fewer mistakes and fewer audit problems down the road.

