New Technology Investment Intake Process: Project Request

Purpose

Provide a consistent process for submitting, reviewing, and routing new technology project requests through the business case document (Technology Project Request) and the Technology Investment Intake form, so that proposed projects are evaluated on business need, strategic alignment, risk, and readiness before resources are committed.

Scope

New technology projects that need IT consultation, project management, implementation resources, or governance review. This includes new systems or platforms, major upgrades or replacements, integrations, multi-department initiatives, and vendor-supported implementations. Requests that only involve purchasing a product without project work follow the Tech Review Path of the Technology Investment Intake process.

Ownership

  • Requester/business owner: Completes the business case form and the Technology Investment Intake form, explains the business need, identifies clients and stakeholders, and provides vendor and funding details.
  • PMO office: Receives the intake request with the attached business case and proceeds with the request.
  • Project Manager(s): Help shape scope, timing, and the project plan once assigned; keep the project record current.
  • Intake Coordinator: Monitors the TDX queue, checks submissions for completeness, coordinates reviews, and confirms handoffs.
  • Reviewers: Address their assigned area (security, data governance, architecture, accessibility, policy) and record findings, questions, conditions, and recommendations.
  • Decision owners: Project approval, prioritization, funding, and risk acceptance remain with the authorized university roles and governance bodies.

Process

  • The requester completes the business case form (Technology Project Request) in TDX.
  • The requester then submits the Technology Investment Intake form with the completed business case attached.
  • The PMO office proceeds with the request once both are received.
  • Begin review within two business days of submission. This is a start-of-review commitment, not a completion deadline.
  • Check the forms and attachments; clarify only the information needed for the next action.
  • Identify the applicable review areas and assign the right people. Do not send every request to every reviewer.
  • Run independent reviews concurrently. Coordinate shared questions in the main ticket.
  • Consolidate findings into a recommendation, conditions, open actions, and named owners.
  • Route the request to the appropriate decision owner or governance body, and link it to a TDX project once approved.

Operating Standards

  • One project record: Keep the business case, review findings, and decisions in the intake ticket. Once approved, link the ticket to the TDX project.
  • Separate scope from history: Earlier requests or reviews can be used as a reference, but each request is evaluated on its own.
  • Clear authority: A favorable review does not mean the project is funded, prioritized, scheduled, or that institutional risk has been accepted. Make sure requesters understand that moving forward means their department accepts the risks identified in the review.
  • Escalation: [Add escalation path and contacts]

Step 1: Complete the Business Case Form

Use when and owner

Use when a department wants to start a new technology project or needs IT project consultation. The requester owns completing the form; the Intake Coordinator confirms it is complete enough to review.

How to submit

Open the Technology Project Request form in the TDX Support Center. Fields marked with an asterisk (*) are required. Select Show Help For All Fields to see guidance for each field while completing the form.

Request information

  • Title: A short, descriptive name for the project (for example, "Student Advising Scheduling Platform Replacement").
  • Requestor: Populated from the submitter's profile. Confirm it is correct.
  • Department: The department sponsoring and owning the project.
  • Project Manager(s): The person or people expected to manage the project, if known. Leave blank if a project manager still needs to be assigned.
  • Client(s): The primary business contacts, stakeholders, and user groups the project serves.
  • Project Duration: The estimated length of the project from start to completion.

Business case

  • Project Executive Summary: A brief overview of the project: what it is, who it serves, and the expected outcome. Write it so a decision maker can understand the request without reading the rest of the form.
  • Project Problem Statement: The business problem or opportunity driving the request. Describe the current state, who is affected, and the impact of not acting.
  • Project Alternatives: Other options considered, including existing university tools, other vendors, process changes, or doing nothing. Note why each was or wasn't chosen.
  • Project Recommendations: The recommended approach and why it best addresses the problem.
  • Recommended Vendor Details (Product/Services): Vendor name, product or service, hosting model (local, university-hosted, cloud), and any quotes, terms, or documentation already received. Attach vendor documents where available.

Strategic goals

Strategic goals describe how the project supports university, division, or departmental goals./p>

For each governance area below, select Yes or No to indicate whether the project relates to it:

  • Strategic Alignment: The project supports institutional strategic priorities and makes good use of IT investment.
  • Performance Management: The project includes measurable outcomes or success criteria, or improves how services are measured and delivered.
  • Security and Risk Oversight: The project involves university data, system access, integrations, or vendor access that requires security and risk review.
  • Oversee IT Policies: The project affects, depends on, or may require exceptions to university IT policies or standards.
  • Data Governance: The project creates, collects, stores, shares, or changes how university data is managed, including sensitive or regulated data.

Planning and risk

  • Project Timing/Plan: Key dates, phases, milestones, and any hard deadlines (contract end dates, academic calendar, grant timelines). Note dependencies on other projects or teams.
  • Risk Assessment: Known risks and how they'll be managed, such as data security, budget, staffing, vendor viability, accessibility, adoption, and schedule risks.
  • Call to Action – Next Steps Including Timing: What decision or action is being requested, from whom, and by when.

After submission

  • The Intake Coordinator reviews the form for completeness and posts an acknowledgement in the ticket so the requester knows it's being worked on.
  • Missing or unclear information is requested in the ticket. Only information needed for the next action is requested.
  • Any governance area marked Yes is used to route the request to the right reviewers.
  • Related tickets, earlier reviews, and existing projects are linked to the request.

Evidence to provide as applicable

Vendor quote or agreement, terms/EULA, privacy policy, VPAT/Accessibility Conformance Report, technical specifications, SOW, and any grant or funding documentation. HECVAT or SOC reports may be requested when university data enters the vendor environment.

Step 2: Submit the Technology Investment Intake Form

Use when and owner

Use after the business case form is complete. The requester owns submitting the intake form; the PMO office owns the request once it's received.

Steps

  • Open the Technology Investment Intake form in the TDX Support Center.
  • Complete the required fields for the request.
  • Attach the completed business case. This is required. Requests submitted without a business case attached will not move forward until one is provided.
  • Submit the form.

After submission

  • The PMO office reviews the intake request and business case and proceeds with the request.
  • Questions or missing information are handled in the ticket.
  • The intake ticket is linked to the business case request and, once approved, to the TDX project.