


Free download
How to choose a digital prospectus platform: 25 questions to ask before you buy
For university recruitment, marketing and procurement teams. Use it in supplier calls, or lift the questions straight into a tender or RFP.
1. Content and updates
1. When a fee, deadline or entry requirement changes, who makes the change?
A good answer: a named person or team, a simple way to request it, and a turnaround stated in hours or days.
2. If we change something once, where does it update?
A good answer: everywhere that content appears, including agent and market versions, without anyone re-exporting files or resending links.
3. Do our links stay the same after an update?
A good answer: yes. Students and agents keep the same URL and always see the current version.
4. Can we see what changed, when, and undo it?
A good answer: a version history showing who changed what and when, and an easy way to restore an earlier version.
2. Mobile reading and accessibility
5. What does a publication look like on a phone?
A good answer: text reflows to fit the screen. Pinching and zooming around a shrunken page doesn’t count. Ask to see it on a mid-range Android phone, not only on a laptop in the demo.
6. Which accessibility standard do you meet, and what’s the evidence?
A good answer: WCAG 2.1 AA as a minimum (or 2.2 AA if your policy requires it), backed by an accessibility statement or a recent audit rather than a line on a slide.
7. If we still need PDFs, are they accessible too?
A good answer: tagged PDFs that meet PDF/UA, or an honest “no” along with what the accessible alternative is.
3. Localisation and agent or market versions
8. How do we make a version for one country or market?
A good answer: start from the main content and change only what’s different, such as fees, entry requirements, contacts or language. Everything else stays linked, so it stays current.
9. Can each agent have their own version or link?
A good answer: yes, with the agent’s details where you want them, and without rebuilding the publication every time you add an agent.
10. How does translation work, and who checks it?
A good answer: a clear process, a named owner for quality checks, and a straight answer on whether translation is included or charged separately.
4. Analytics and data
11. What can we see about how people actually read?
A good answer: views, time spent and clicks, broken down by section. You should be able to tell what gets read and what gets skipped.
12. Can we see results by country and by agent?
A good answer: yes, as standard reporting rather than a custom project you pay extra for.
13. Does it work with GA4 and the reporting tools we already use?
A good answer: it connects to your own GA4 property and can feed dashboards such as Looker Studio, so this data sits next to the rest of your marketing reporting.
14. Who owns the data, where is it hosted, and how do you handle GDPR?
A good answer: the data is yours, the hosting location is stated in writing, a data processing agreement is ready to sign, and cookie consent is handled properly.
5. Security
15. Can our staff log in with single sign-on?
A good answer: SSO through your identity provider, for example over SAML. If it’s on the roadmap instead, you want a date.
16. Which security certifications do you hold?
A good answer: ISO 27001 or SOC 2, with the certificate or report available on request. If neither, an honest description of the controls in place and the plan to get certified.
17. When was your last independent penetration test?
A good answer: within the last 12 months, run by a third party, with a summary your IT security team can review.
6. Service model
18. Who builds the publications: you or us?
A good answer: a clear split. Some suppliers hand you the tools and some do the build for you. Either can work, but you need to know which one you’re paying for and whether your team has the hours.
19. What are your turnaround times, in writing?
A good answer: specific figures for go-live and for routine updates, plus what happens in your busiest weeks, such as Clearing or application deadlines.
20. What training and support do we get, and is it included?
A good answer: onboarding for your team, a named contact, support hours that cover your time zones, and no surprise charges for asking for help.
7. Pricing model
21. How is pricing worked out: per user, per publication, by credits or a flat fee?
A good answer: one model, explained in plain terms, with a worked example based on the publications and versions you actually produce.
22. What costs extra?
A good answer: a written list. Things to ask about specifically: page limits, extra users, additional versions, translation, analytics on higher tiers, custom domains and lead forms.
23. What happens to the price at renewal, or if we need more?
A good answer: renewal terms set out before you sign, and a clear price for adding publications or versions mid-year.
8. Exit and ownership
24. If we leave, what can we take with us?
A good answer: your content, images and data, exported in standard formats within a stated time and at no extra cost.
25. What happens to our links when the contract ends?
A good answer: publications can sit on your own domain, or old links can be redirected, so QR codes, printed materials and old agent emails don’t lead to a dead page.
Using this list in a tender
Send the questions in advance and ask for written answers. Where a question involves a standard or a certificate (questions 6, 7, 14, 16 and 17), ask suppliers to attach the evidence rather than describe it. Questions 2, 19 and 22 tend to separate suppliers fastest, so give them extra weight when you score.
It also helps to ask every shortlisted supplier to show the same real task live: change a fee in one place and show where it updates.
How theRACK answers these
theRACK by eduKUDU is a recruitment content system for universities. Prospectuses, international guides, viewbooks and agent versions run as live web pages.
The eduKUDU team builds your publications and makes your updates, so your team doesn’t need to learn a new tool (questions 1 and 18).
Publications go live in two to three weeks (question 19).
Updates are made within 24 hours (questions 1 and 19).
Publications meet WCAG 2.1 AA (question 6).
Analytics show reading by country, section and agent, and connect to GA4 and Looker Studio (questions 11 to 13).
Pricing is credit-based and quoted on request, based on what you need to produce (question 21).
To see how theRACK handles the rest of the list, ask us for written answers to all 25.
Lets talk!
Book a Demo
We will be in contact within 24 hours.