Skip over navigation

OIT Web Application Services Policies

Non-billable hours

  • Bug fixes. Work required to keep applications we have built running due to bug fixes (i.e., program errors that are our fault) or system changes on our web hosting service will not be billed.

  • Meetings. Consultations about proposed projects or reviews of work on ongoing projects will not be billed.

  • Consulting. Web Application Services  staff will advise OIT colleagues and customers in their areas of expertise at no cost, as long as this does not translate into work being done for the advisee.

Billable hours

  • Projects. Unless one or more points above are met, work on Web Application Services projects will be billed at the hourly rate shown below.

    • Elapsed hours will be kept track of on a daily basis and will be rounded to the nearest quarter hour.

    • Projects will receive a write-up and price quote before they are undertaken.

    • If we underestimate the required time, and that is due to our error, we will stick to the original estimated amount for billing purposes.

    • If a customer asks for features not included when the original project write-up and estimate were created, we will bill the customer for the extra time needed to implement those features after first presenting a write-up and a revised cost estimate.

    • Projects are billed at the completion of work. We do not accept payment in advance. 

  • Enhancements. Work undertaken to change the functionality of finished projects will be billed as above.

  • Ongoing operations. Web Application Services strives to deliver systems that do not require further involvement from us in order to be fully operational. If it becomes necessary for us to be involved in the normal ongoing operation of a system, such time spent will be billable at our normal hourly rate.

Hourly rates

  • Web Application Services' standard hourly rate is $100.00 per hour.

Change control

  • Web Application Services observes the AIS Change Control Documentation Policy.

    • Briefly stated, for changes to existing applications we will migrate changes into production only when authorized in writing by the customer.

    • For new systems, we will migrate the application to production only when we have written authorization from the customer that all requirements have been met.