Build separate UC and CSU source maps
UC Procurement directs suppliers to the CalUsource Public Bid Site for opportunities across University of California campuses and publishes systemwide agreement information. CSU's official supplier resources direct businesses to public solicitation and vendor-registration paths, including Cal eProcure, while campuses maintain procurement operations.
Do not assume an account, contract, or registration crosses systems. Record the university system, campus or central office, official sourcing platform, event identifier, buyer contact, and document location for every lead.
- Maintain distinct registration and renewal records for UC and CSU.
- Identify whether the buyer is a campus, medical center, laboratory, or system office.
- Capture the official addenda and submission location.
- Follow the named event instructions when general portal guidance differs.
Distinguish campus demand from systemwide demand
A systemwide agreement can cover recurring needs across locations, while a campus may source a local project, service, or commodity for its own operations. The sales effort, references, implementation plan, and logistics can differ substantially.
For systemwide work, test governance, pricing consistency, catalog management, reporting, and support across multiple locations. For campus work, test local access, stakeholder coordination, schedule, site conditions, and the purchasing unit's specific procedures.
Use category evidence to prioritize campuses
Universities buy technology, research support, facilities services, equipment, professional services, food, transportation, communications, construction, and many other categories. Broad higher-education keywords will generate noise. Start with the company's proven deliverables and identify campuses whose operations or prior events show plausible demand.
Build a small account register with the official procurement page, likely category contacts, public events, existing systemwide agreements, and last review date. Historical activity can guide attention but does not prove a new competition or open buying path.
- Separate research, clinical, academic, housing, athletics, and administrative use cases.
- Match references to the operating environment the buyer describes.
- Note delivery, installation, badging, parking, and campus-access constraints.
- Avoid inferring a campus need from another campus's award.
Evaluate small-business paths precisely
UC publishes a Small Business First program and supplier guidance that explains current applicability, exceptions, quotation procedures, and use of recognized certifications. CSU publishes social-sustainability and supplier resources. These programs can create useful access, but the current policy and event determine eligibility and effect.
Verify certification status, commodity fit, dollar range if stated, exclusions, quote requirements, and campus implementation. Do not promise a preference or limited competition based only on company size or an outdated summary.
Read university terms as operating requirements
University solicitations can include insurance, accessibility, sustainability, data protection, research, healthcare, background, labor, intellectual-property, public-record, and site requirements. A familiar commercial service may need a different delivery design in an academic, clinical, residential, or laboratory setting.
Map every material term to a business owner before bidding. Confirm who can approve exceptions, whether exceptions affect evaluation, and how the pricing model absorbs required reporting, travel, onboarding, security, product standards, or contract administration.
- Review the draft agreement before solution and price approval.
- Identify protected data and system-access boundaries.
- Confirm accessible deliverable and technology requirements.
- Price multi-campus governance and service escalation explicitly.
Create one education queue without flattening the buyers
A shared review queue can normalize buyer, campus, event, status, scope, deadline, question date, mandatory activity, value if stated, and decision owner. Keep the system-specific portal, registration, contract program, policy, and submission fields alongside that common record.
Chase when the exact campus or system need matches documented capacity and every hard gate has an owner. Verify when a portal, certification, location, or contract-term question remains answerable. Pass when the team cannot support the campus environment, systemwide scale, mandatory schedule, or required agreement.
Official starting points
Sources to verify before acting
Procurement rules, dates, forms, and portal records can change. Use these official sources and the current solicitation.
Questions
Frequently asked questions
Do UC and CSU use the same procurement system?
No. UC identifies CalUsource for public bids, while CSU provides its own supplier and public-solicitation paths. Follow the current official instructions for the specific system and campus.
Are all university opportunities systemwide?
No. Opportunities may be systemwide, multi-campus, campus-specific, or tied to a particular operating unit. Scope and delivery capacity should be tested at the level stated by the buyer.
Does California small-business certification apply automatically?
Programs can recognize state certification, but applicability, procedures, exceptions, and benefits differ. Verify the current university policy and solicitation rather than assuming an automatic preference.
Should vendors contact individual campuses?
Use official campus supplier and procurement contacts where appropriate, while respecting solicitation communication rules. Account research should never bypass the designated question or submission process.
This guide is general business information, not legal, procurement, certification, tax, or compliance advice. The current official solicitation and buyer instructions control.