Consultants who take part in application development projects for their clients will no doubt field all kinds of requests from stakeholders. For large-scale projects with hundreds of requests, you’ll likely coordinate your programming requests using a spreadsheet application with a large database.

However, that approach might be overkill for smaller projects with fewer requests. To help you with this task, we’re featuring an Excel spreadsheet to track your programming backlog. This spreadsheet was produced by TechRepublic contributor Mike Sisco, an IT consultant and former CIO for a healthcare company.

You can use this download to track requests and ensure they are resolved. Each of the four worksheets in the download contains fields for individual requests, priority, who made the programming request, start and end dates, who will perform the request, how long it will take to complete, and the status of the request.

Here’s how Sisco suggests that consultants use this spreadsheet: As the team leader or the consultant, you’ll list all the programming requests in the Backlog—ALL ITEMS worksheet. Sisco recommends that you place unresolved requests in bold. Copy all unresolved requests in the Active Items spreadsheet. Use this list to keep track of outstanding items from week to week.

You can also add columns to suit your needs or to help you with billings. For example, you could insert an “Actual Hours” column next to the estimated hours column to assess which tasks proved most difficult for your team.

What do you use for smaller programming engagements?

Do you use smaller Excel or Access files when keeping track of programming requests? If you think other TechRepublic members would benefit, send them to us. If we publish them on the site, we’ll send you $50.