Matt Miller (#4) (7/15/2015)

---

T & M is used to define: rough duration, billable rates, what is assumed to be in scope and any other specifics as to what's acceptable. This sample I pulled up using Google points to a fair amount of items you might care to cover.

http://www.cdboyd.org/computer/linked/standard_system_development_time_and_material_contract.pdf

Certainly not a perfect fit, but should give you some pointers. Things like:

- what the scope currently is.

- what the expected pace would be

- (if requested) a high level estimate of hours. Be sure to couch this carefully so you aren't stuck with the bill if the estimate is not accurate.

- billable rates (possibly based on monthly volume, or time of day, function being performed, etc...), any cases where a higher rate might be charges (e.g. any time above 6 hours in a given day, or minimum per day/per visit rate),

- what is considered to be billable/chargeable (e.g. any remote work, scoping meetings, documentation efforts, etc...),

- what is expected from them as well as what you will do,

- anything you'd end up charging them for in terms of materials (e.g. if you were to have to acquire additional hardware or software to perform the job, mileage/tolls, lodging and sustenance as appropriate).

- You should also have any exit strategies articulated (early termination provisions) and/or how the SOW could be extended.

- If this is for support, you would also want to articulate whatever is realistic in terms of response time (I could be there within x of initial call for urgent calls, within y for normal requests.

- Finally: clearly articulate how billing will occur and your terms: having the penalty for late payments is a good idea from what I've seen (don't kid yourself - they will slow-pay you if they can get away with it).

Remember - this is a contract, so make sure you can commit to what you offer.