Project Experience Documentation

I have one question and one concern.

My question is in reference to section 3.6.a of the CCM Application vs. section 3.7. In reviewing the Guidelines for completing the application it appears to me that section 3.6.a should contain the bulk of information needed to describe my RIC project experience and that section 3.7 should be shorter statements defining each management role and responsibility I had on the project that will support the bulk of the information that I provided in paragraph 3.6a. Is my understanding of this correct?
My concern is about the last sentence in paragraph 3.7 of the Guideline for Completing the Application which states “Responsibilities that are listed identically for multiple projects, while feasible, tend to raise concerns related to the specificity of the information related to each project.” I find this interesting in as much that every CM@Risk project that I manage all share common threads with a few examples being:

1.Working with Owner’s to insure that the Architect’s design meets their expectations and managing the process of getting changes made if the design is lacking.
2.Analyzing contract documents to determine the best course for constructing the project and then building a project schedule to represent that predetermined course within the overall projects duration
3.Updating, maintaining and revising the project schedule throughout the life cycle of the project.
4.Reviewing the drawings to break the project down into various scopes that can then be competitively bid.
5.Taking those bids and determining an overall GMP.
6.Taking that GMP and turning it into a schedule of values for pay requests.
7.Managing the process of project closeout including O&M’S as well as Owner Training.
8.Directing subcontractors on warranty issues after the project is complete.

These are just a few examples I can think of. I have no choice but to document my RIC experience for each project on its own merits and if these “Responsibilities that are listed identically for multiple projects” raises concerns then it is what it is. Any ideas on combating this?