Technology and Software
Requisition submittal is required for software purchases, regardless of dollar amount, due to the requirements outlined below.
Process Overview
Pre-Purchasing Reviews Submitted and Completed
Department ensures that reviews necessary for software are submitted and completed. These include a Data Usage Form (DUF), Accessibility review, and others as relevant to the purchase and its use case.
Requisition Submitted
Submit Requisition through SharePoint and Colleague, including completed pre-Purchasing reviews identified above. This submission process will change in Spring 2027 as The Purch is rolled out.
Budget Approval
Budget Officer reviews and approves the requisition, certifying funds are available. The requisition is not visible for Purchasing before this approval.
Purchasing Receives Request
Purchasing receives the requisition once the Budget Officer Approves it.
Procurement Officer Review
Purchasing reviews the requisition for accuracy and completeness ensuring compliance with State and University.
Purchase Order Issued
A purchase order number is assigned, and the PO is issued to the vendor. A copy of the po is sent to the funding department.
Vendor Signature
If PO meets a requirements for a vendor signature, it will not be marked as complete until a vendor returns the signed document.
Pre-Purchasing Requirements for Software
Software purchases have additional submissions requirements. Some are reviews/approvals which need to be completed prior to submission to Purchasing. Others are documents/information that need to be included with the submission. One or more of these missing from a submission is the most common cause of requests being delayed.
Note: For academic software, The Office of Technology Solutions facilitates requests through the Academic Software Request process. This process helps ensure the Pre-Purchasing requirements below are met.
Contract/Agreement Documents
Software almost always has an associated agreement. This might be called by various
names, and may include one or more of the following:
- Terms and Conditions
- Terms of Service / Terms of Use
- End User License Agreement
- Master Service Agreement
- Privacy Policy
Even if there is no cost to the University, this is still considered a contract/agreement by
both the State and University and must be reviewed and signed by Purchasing.
When submitting your request, please be sure to include these documents, including
any Order Forms/Quotes. If you are working with a vendor, they will be able to help you
find them.
TIP: Vendors will often have Terms linked on their website, usually near the bottom of a
page. Sometimes these apply to their products, but often are specifically for the website
itself. This is usually identified in the opening paragraph. Checking that you’re sending
us the correct agreement saves a lot of processing time!
Data Usage Form (DUF)
A Data Usage Form (DUF) should be submitted for anything that handles University
data or accesses University systems. The Information Security Office (ISO) will review
this information and provide Purchasing with an assessment.
Products/services which can require a DUF include:
- Installed software
- Devices with built-in software (ex: smart devices)
- Web-based apps/platforms
- Contracted services (ex: 3rd party web developers)
If you are uncertain whether a DUF is necessary, or have questions about the DUF
process, please contact the Information Security Office.
Note: The Information Security Office’s DUF assessment must be completed prior to
submitting your request to Purchasing. If a request is still pending the completed DUF
assessment, it will be rejected to the requestor. If the Information Security Office has
confirmed that a DUF is not necessary, please provide their statement with your
submission.
Accessibility
intended for instructional/classroom use and public-facing use require an Accessibility
Review. Please see this page for more help: Accessibility Review Procedures
3rd Party Web Development
Communications (WEB) team. This can be submitted for review by using the
Accessibility Review Request form. Be sure to include detailed information regarding
the website(s) involved, the work being done, the vendor, and any other relevant
information. Once approval has been received, please include it with your Purchasing
request submission.
Legally Protected Data
If technology/software will handle legally protected information, this is important to identify. This is often determined by its use case. This is one of the key reasons it is essential that a detailed and accurate description of a product’s function and intended use case(s) are included when submitting it for review. There are both federal and state laws that we must be compliant with.
Common Categories:
-
Family Educational Rights and Privacy Act (FERPA)
- Federal law, applies to student education data / records
- Applies to both K-12 and Higher Education
- Resources:
- Full Text: FERPA | Protecting Student Privacy
- ISU Policy: 2.1.1 Student Records
- Registrar Information: Family Educational Rights and Privacy Act (FERPA)
-
Student Online Personal Protection Act (SOPPA)
- Illinois state law, applies to K-12 student personal information and education data / records
- Resources:
- Full Text: (105 ILCS 85/) Student Online Personal Protection Act -
Illinois General Assembly - ISU Laboratory Schools Policy: Student Online Personal Protection Act (SOPPA)
- Full Text: (105 ILCS 85/) Student Online Personal Protection Act -
-
Health Insurance Portability and Accountability Act (HIPAA)
- Federal law applying to medical records and other health information.
- Please refer to unit policies and procedures to determine if HIPAA applies. Please contact the Office of General Counsel for additional assistance if needed.
- Federal law applying to medical records and other health information.
-
Biometric Information Privacy Act (BIPA)
- Illinois state law applying to personal biometric information / data
- Policies still in development. Please contact the Office of General Counsel for more information.
Artificial Intelligence (AI)
Paying by P-Card (Exception Requests)
Avoid Common Delays
These are some common contributors to delayed requests. Avoiding them greatly helps us process your request in the best time possible.
-
Include specific name of product(s)
- Clearly identify the exact product being requested, including information like version name or subscription level. Vendors sometimes have different terms for different products (or even versions of products), so this specificity helps greatly.
-
Correct Agreement/Terms
- Having the correct product agreement/terms is essential for us to complete the contract review.
-
Product Description and Use Case
- A description of the product, how it is intended to be used, and by whom helps us ensure all compliances are in order, and greatly reduces the need for follow-up questions.
-
Cost / Total Value
-
Software costs can vary, and often depend on the type of license being purchased. Please be sure to specify whether the cost is a one-time fee, annual, monthly (with intended number of months), or otherwise.
- If you’ve received a quote or similar document from the vendor, please include it in your submission.
- If the product usually has a cost but is to be paid for by a grant, waived by the vendor, or otherwise provided to the University free or at a discount, please include this information with a reference document.
- If the product is to be paid for directly by students, please specify this and include an estimated cost. This estimated cost is equal to the expected student population (in an Academic Year) multiplied by the cost per student.
-
-
DUF and other prerequisite reviews completed
- All Pre-Purchasing reviews being completed prior to submitting your request to Purchasing is essential. If you’re getting ready for a submission and are unsure whether you have everything you need, please feel free to contact us at ISUPurchasing@IllinoisState.edu.