I agree with Anderson's post on this one. Definately its not about software its about process.
"next action and does it need tracking" would work if you add it to the rest of the GTD discipline.
As far as recording goes my advice is that you first work out the dimensions you wish to report by:
Define what your 'output' looks like first.
Then start with a very simple paper based form to capture 'input' data and record it against those 'output' dimensions for a couple of weeks. When you come to analyse this it will give you more insights into what you want as 'output'. Trust me I used to design data capture systems.
When you have done this will have a much better way to assess the software systems to see if they best fit your needs. Otherwise you have a solution looking for a problem rather that visa versa.