I like Skye's idea Ruby,
Another "do it yourself" option might be to use custom data on the Documents and adapt this Targeted Auditing Proof Of Concept to track the changes to its status as Rejected/Approved With Changes updates occur (or even simply count them, given your goal).
"As the time it happens", you could also trap the Last Updated By User's roleID, homeTeamID, etc. either in the Targeted Audit Text, or (if warranted) in dedicated "odometer" calculated custom parameters (e.g. one per Role, one per Team, etc.) in order to collect additional stats that could then drive Filters, Groupings, Views, Sorting, and Charting (e.g. last year, by role, how many documents were rejected).
One gotcha, mind you, is figuring out how to ensure the custom form gets onto the documents in the first place; but (once you've confirmed the approach), that could be monitored and corrected procedurally, and/or automated using our UberCalc solution (or Fusion, if you have it).
I'd be interested to hear which way you go, and how you make out.
Regards,
Doug
