Back to News
Campus SecurityFebruary 22, 20266 min read

How Universities Buy Card Systems: Procurement & RFP Guide

Procuring a campus card system is a multi-year commitment involving complex stakeholder requirements and significant budgets. This guide walks through the RFP process, evaluation criteria, key vendor questions, and common procurement pitfalls that universities encounter.

How Universities Buy Card Systems: Procurement & RFP Guide

Procuring a campus card system is one of the most complex technology purchases a university will make. Unlike buying software or hardware that serves a single department, a campus card system touches every part of the institution — access control, dining, library, parking, recreation, IT, student affairs, and finance. The system will be in place for 7-15 years. Getting the procurement wrong means years of workarounds, integration headaches, and escalating costs. Getting it right requires a structured process with the right people at the table.

The Stakeholder Challenge

The first reason campus card procurements fail is insufficient stakeholder involvement. A campus card system serves:

Facilities/Security:: Building access control, lockdown integration, visitor management
Dining Services:: Meal plans, cashless payments, retail dining
Library:: Borrowing privileges, reserve access, printing
IT:: Network integration, identity management, mobile credentials
Student Affairs:: Student ID, orientation, campus life
Finance/Bursar:: Account management, billing integration, payment processing
Parking & Transportation:: Permit management, transit integration
Recreation:: Gym access, equipment rental, intramural registration
Human Resources:: Employee credentials, time and attendance

Each department has requirements that may conflict with others. Dining wants open-loop payment processing; security wants a closed system for tighter control. IT wants cloud-hosted; facilities wants on-premises for reliability. The procurement process must surface and resolve these tensions before an RFP is written, not after a vendor is selected.

Building the RFP

Requirements Gathering (2-3 Months)

Start with structured interviews or workshops with each stakeholder group. Document current systems, pain points, and must-have capabilities. Distinguish between requirements (non-negotiable functional needs) and preferences (nice-to-haves that influence scoring but don't disqualify).

Common requirement categories include:

Credential technology:: Which chip standards must be supported (DESFire, SEOS, multi-tech)
Mobile credentials:: Apple Wallet, Google Wallet, Samsung Wallet support
Integration:: APIs and connectors for existing systems (SIS, LMS, ERP, access control)
Scalability:: Number of cardholders, transactions per day, concurrent readers
Uptime/SLA:: Required system availability (99.9% is typical for critical campus infrastructure)
Data residency:: Where data is stored (particularly important for European institutions under GDPR)
Accessibility:: ADA/WCAG compliance for self-service components

Writing the RFP Document

A well-structured campus card RFP typically includes:

1.Institutional overview:: Size, locations, current systems, strategic context
2.Scope of work:: What the vendor must deliver (hardware, software, integration, training, support)
3.Functional requirements:: Detailed requirements organized by department/function
4.Technical requirements:: Infrastructure, security, integration, data standards
5.Vendor qualifications:: Minimum experience, references, financial stability
6.Evaluation criteria and weights:: How proposals will be scored (see below)
7.Timeline:: Key dates for questions, submissions, demonstrations, and decision
8.Contract terms:: Standard institutional procurement terms, insurance requirements
9.Pricing format:: How vendors should structure their cost proposals

Evaluation Criteria

Establish transparent evaluation criteria before the RFP is issued. A common weighting framework:

Functional fit (30-35%):: How well does the solution meet stated requirements?
Technical architecture (20-25%):: Security, scalability, integration approach, modern standards
Vendor experience and references (15-20%):: Higher education track record, reference site feedback
Total cost of ownership (15-20%):: Not just year-one cost, but 7-10 year TCO including licensing, cards, hardware refresh, support
Implementation plan (10-15%):: Realistic timeline, change management approach, training
Innovation and roadmap (5-10%):: Vendor's product direction, investment in mobile and emerging technology

Key Questions to Ask Vendors

During demonstrations and Q&A sessions, these questions separate serious vendors from those presenting a polished demo:

On integration:

"Show us a live integration with [your specific SIS]. How are student records synchronized?"
"What happens to in-progress transactions if the network connection drops?"
"How does your system handle mid-year enrollment changes — adds, drops, leaves of absence?"

On security:

"Which chip technologies does your system support natively? What requires a third-party integration?"
"How are cryptographic keys managed? Who controls the master keys — us or you?"
"Describe your breach notification process and timeline."

On cost:

"Provide a detailed 10-year TCO including all licensing, hosting, support, and estimated card production costs."
"What costs are incurred if we want to increase the number of readers or cardholders by 25% in year three?"
"Are there per-transaction fees for any payment processing functions?"

On support:

"What is your average response time for critical (system-down) incidents? Provide data from the last 12 months."
"If we need a system customization, what is the typical lead time and cost?"
"How many dedicated support staff do you have for higher education clients?"

The System Integrator Role

Many universities work with a system integrator (SI) rather than contracting directly with a platform vendor. System integrators like ColorID, ADVANTIDGE, and others specialize in campus card deployments and bring several advantages:

Multi-vendor expertise:: An SI can combine best-of-breed components — one vendor's card platform with another's readers and a third's mobile credential solution.
Implementation experience:: SIs have deployed campus card systems at dozens or hundreds of institutions and know the common pitfalls.
Ongoing support:: SIs often provide local or regional support that a national platform vendor may not.
Independent advice:: A good SI recommends the best solution for your institution, not the solution that maximizes their margin.

Independent Consultants

For large-scale procurements, some universities engage independent consultants like Robert Huber Associates, which specializes in campus card technology advisory services. An independent consultant can help write the RFP, evaluate proposals objectively, and negotiate contracts — bringing deep market knowledge without vendor bias.

Common Procurement Mistakes

Choosing on Price Alone

The lowest-cost proposal often becomes the most expensive solution over time. Cheap card platforms may require expensive custom integrations. Low-cost readers may have shorter lifespans. Vendors who underbid to win the contract often make up the difference in change order fees.

Insufficient Reference Checking

Always visit (physically or virtually) at least two reference sites of comparable size and complexity. Ask specific questions: What went wrong during implementation? How responsive is support? What would you do differently? Reference sites listed by the vendor are pre-selected — also ask for references the vendor didn't suggest.

Ignoring Migration Complexity

If you're replacing an existing system, migration is typically the hardest part of the project. Data migration (cardholder records, account balances, access permissions), parallel operation (running old and new systems simultaneously during transition), and user communication require detailed planning. Vendors who minimize migration complexity in their proposals may be setting unrealistic expectations.

Failing to Define Card Specifications

The physical campus card is the most visible component of the entire system, and card specifications should be part of the RFP. Define chip technology, visual design requirements, print quality standards, durability expectations, and card lifecycle policies. Universities that leave card specifications vague often end up with generic-looking cards that don't meet their quality or technology standards.

CampusRFID has extensive experience supplying cards for campus card procurement projects. We work with system integrators, platform vendors, and universities directly to ensure that the physical card specifications align perfectly with the chosen technology platform.

*Preparing a campus card RFP? Contact CampusRFID to discuss card specifications, chip technology options, and volume pricing for your procurement.*

Share:

Ready to Implement RFID on Your Campus?

Contact us to learn how our RFID solutions can improve campus security and student experience.

How Universities Buy Card Systems: Procurement & RFP Guide | CampusRFID