Skip to main content

How to Request an IT Project

To request an IT project, please follow the two-step process below.

1. Evaluate your request

To be considered an IT project, your request must meet one or more of the following criteria:

  • Work requiring more than 24 hours (3 working days) of IT time
  • Cost > $5000 (project cost adjustments > 25% must be reviewed by appropriate technology committee)
  • Work/impact broader than one campus department or equivalent unit
  • Requires coordination across IT
  • ­Involves standing up a new technology or expanding functionality of an existing technology solution

Please note, an IT project:

- does not include repeating support activities (e.g. tax table updates, leave roll-forwards, etc.)
- does include emergency compliance requests - work will begin and be reported for information (e.g. GA time-critical data, legal, security, etc.)

If your request does not meet the project criteria, it will be considered a service request and re-routed to the IT Help Desk.

2. If your request meets the project criteria (see above), make your IT project request:

Use the IT Self-Service portal at or contact the Help Desk at 227-7487 to enter your project request. You may also use the following link to enter a request directly:

You will receive acknowledgement of receipt of your request within 24 hours.

What happens once you've made your request?

The department of Academic Engagement & IT Governance will schedule a meeting with you and other stakeholders (within and external to IT) as required to determine the complete scope of your request, and will then work with you in formally documenting the project within IT's project management system. The request will then be presented on your behalf to the IT Leadership Council (ITLC). The ITLC determines in what order IT projects are ranked and activated. The following criteria is used for the ranking of projects:

  • Compliance: Is the project necessary for regulatory, audit, accreditation requirements?
  • Strategic alignment/need
  • Benefit (return on investment)
  • Risk (technology, culture, organization, scope of change—the higher the risk, the lower the score)
  • Resources (skills, expertise, contention, project management—the more demand the lower the score, estimated staff hours)
  • Criticality (urgency)
  • Constraints and dependencies (the project depends on other work or technologies; the higher the constraints and dependencies, the lower the score)

Once approved and prioritized, your project is assigned a number and a manager who will lead the work of your project. Once IT resources are available to work on your project, the IT project manager will contact you directly to start the project.

Office of Web Services