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 this guide is reviewed
CampusRFID reviews technical guides against standards and official documentation. Where a source list appears, it identifies the primary references used. Card and reader compatibility should still be verified with a sample on the institution's installed system.
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:
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:
Writing the RFP Document
A well-structured campus card RFP typically includes:
Evaluation Criteria
Establish transparent evaluation criteria before the RFP is issued. A common weighting framework:
Key Questions to Ask Vendors
During demonstrations and Q&A sessions, these questions separate serious vendors from those presenting a polished demo:
On integration:
On security:
On cost:
On support:
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:
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.*
Primary sources
Standards, regulations, and first-party technical documentation consulted for this review.
- Security and Privacy Controls for Information Systems and Organizations (SP 800-53 Rev. 5) — National Institute of Standards and Technology
- Family Educational Rights and Privacy Act regulations — U.S. Department of Education
- PCI DSS v4.x documents — PCI Security Standards Council
Explore this topic
Product pages selected for the subject covered in this guide.
Ready to Implement RFID on Your Campus?
Contact us to learn how our RFID solutions can improve campus security and student experience.
Related Articles
Campus Card Security: Encryption, Authentication, and Cloning Prevention
From the broken Crypto-1 cipher on legacy sector-memory 13.56 MHz credential to AES-128 encryption on modern AES-authenticated 13.56 MHz credentials, campus card security has evolved dramatically. This deep dive covers how encryption, mutual authentication, and diversified keys protect your campus — and why legacy systems must be replaced.
Campus Card Payment Integration: Connecting the Card to POS, SIS, and Mobile Ordering
A tap at the register is the easy part. The hard part — and where most campus payment programs succeed or stall — is the integration behind it: point-of-sale, the student information system, declining-balance accounts, mobile ordering, and PCI-DSS. Here is how the pieces actually fit together.