Here is what we use for looking at the performance of BA's. Whenever we introduce a new measure we dont worry about the level, instead we focus on measuring. Once we are able to get into a pattern of measurement then we can start to manage to the measure. It is really tricky putting bonuses on the measures.

We have a lot of posts on the topic of BA as a job. Some are about interviewing, managing etc 

http://requirements.seilevel.com/blog/category/product-manager

At seilevel we work with clients as product managers/business analysts so all of our employees are BA's. Ultimately what we looking for is end user satisfaction, end user adoption and success of the projects. The last one is the hardest and I would suggest only tracking measurement of project success not actually managing for success. I know it sounds silly, but getting people in the habit of measuring project success is extremely difficult.

The danger in things like #4, is that if they are going to get yelled at for making changes they will start to resist changes. Ultimately what you are looking for from your BA's is did they develop the right product. You might want interim measures of the requirements - I would tend to get those from the customers - such as subject matter experts, testers and developers.

The other things are busy work that may or may not get you to project success. We do review documentation to ensure adherence to some standards - that takes a lot of work.

Drop me an email and I can put you in touch with our person who does the reviews.