First, get an estimate of the amount of code to be delivered to satisfy your requirements. This can be done using various units, but source lines of code (SLOC) is good (if defined first), since the collection of SLOC can be automated, in order to track actual contractor status. SLOC should be accompanied by some measure that equates to functionality, however, since you don't want to encourage your contractor to simply deliver lots of code - you want your requirements met. If you have good documented requirements, I suggest counting requirements before coding begins (e.g., paragraphs, pages, use cases, etc) and tracking code back to requirements as code is delivered and verified. When all requirements are satisfied with code, the software development part of the project is complete.
On a T&M contract, you will also have to worry about how much effort is being charged to your project. Normalizing effort with SLOC can give you an indication of efficiency (e.g., SLOC per person month). However, be careful with this measure, because if you apply it to an individual developer, it could backfire on you by sending the message that you want lots of code. A better efficiency measure is Productivity Index (PI), developed by Larry Putnam of QSM, but this is a more advanced metric, and could be more difficult to implement.
Obviously, there is more to managing a software project than this, but from a metrics standpoint, this should help.
Regards,
James T. Heires, PMP
President
James Heires Consulting, Inc.
Home of EZ-Metrix code couting utility
http://www.ez-metrix.com