2 Responses

1. reporting
   I would suggest you look for reporting capability at various levels: by account, group or user. This provides full flexibility in tracking the use of the system. You might also consider reports showing utilisation of the system to support return on investment, and reports that show the most popular modules, and the most popular rated content.

   I know that http://www.umbel.co.uk can offer this along with the opportunity to customise reporting functionality.

2. It depends
   Steve

   It really depends on what you are looking to achieve with the portal. FIrst know what your goals are – and the reports you need are those that will demonstrate the attainment of those goals.

   If you are thinking about a procurement exercise – be careful not to create a long wish list of reports that you are unlikely to actually use. Most systems are customisable so if you find you need more reports later, there are usually ways to add them.

   Having said this I would add test scores (though you would be hard pressed to find one that didn’t offer this. Also simple usage figures – how often do people login and for how long? What do people spend their time doing when logged on (depends on what they can do in your portal)? Is behaviour different in different parts of the organisation?
   Can you link activity to any marketing of the system you do?

   Think also about this – what information would the people paying for or championing the system need in order for them to decide it was a good investment?

   I hope this helps

   Richard