I agree with Craig.

You need to know the requirements, not try to guess them. Your guesses may be right, but if they are wrong you can easily spend time doing something that is not necessary, or missing something that is necessary.

Personally, I would prepare a compliance document. This could identify each requirement as a section heading, followed by a description of the requirement followed by what you have done to satisfy the requirement. This becomes a document that can be audited for completeness, and gives you a base to work from if a requirement changes.