The hidden cost of Google Forms in CGE survey mode
Google Forms is free and deploys in 30 minutes. For a one-off student satisfaction survey, it's the right tool. For an annual CGE campaign (6 months + 30 months) that comes around every year, the hidden cost adds up.
First cost: the lack of pre-filling. Every alumnus has to retype their name, class, major, and dates. Google Forms allows pre-filling via a parameterized URL, but you have to generate 400 to 600 unique links by hand or via a script. From what we observe, few schools do this properly, and the completion rate stalls 20 points below that of a native platform. To measure the impact, see our article on pre-filling and response rate.
Second cost: reminders. Google Forms doesn't send reminders. The team has to do it by hand from Mailchimp or Gmail, managing its own "non-respondents" lists. Across 4 waves, that's 2 person-days per campaign.
Third cost: the export. Google Forms exports a raw CSV. The expected CGE format is precise (29 typical columns, specific codifications). Reprocessing in Excel to go from one to the other takes 1 to 2 person-days.
Fourth cost: hosting. Google Forms hosts in the United States. The school's DPO has to push through a Google Workspace addendum, validate the transfers, justify the legal basis. Many DPOs now refuse Google Forms for personally identifiable alumni data.
Cumulatively, on an annual 6-month + 30-month campaign, we're talking about 3 to 5 person-days of reprocessing per year. At €350/day fully loaded, that's €1,200 to €1,800 of hidden operating cost — for a "free" tool.
What dedicated survey software concretely changes
The difference isn't in the collection (Google Forms and a dedicated SaaS collect equally well). It's in everything around the collection: preparation, reminders, export, compliance.
Automatic pre-filling. The software receives the alumni database, generates the unique links, pre-fills the data already known. No script to write. No URL to concatenate.
Scheduled multi-channel reminders. Email + SMS, waves defined once, targeted at non-respondents. A dashboard shows the response rate in real time by class, by wave, by segment. For the mechanics of optimal reminders, see the 7 mistakes that sink a CGE survey.
Export in CGE format. XLSX directly compatible with the format expected by CGE asso. No reprocessing, no column mapping.
Built-in benchmarks. The indicators (employment rate, median salary, share of permanent contracts) are calculated automatically and compared to previous classes. Cross-referencing with external benchmarks (CGE asso) in two clicks.
GDPR compliance. France hosting, DPA provided, legal basis documented. The DPO signs off in a few days.
On the Terrilink side, these functions are native on the CGE / CTI surveys page. The reprocessing disappears, the 3-5 person-days become available for steering and qualitative analysis. Mentorship scheduling or the dues follow-up benefit directly.
Step 1 — Map the current questions and exports
Before any migration, export the current Google Forms form to PDF or a document, and list:
- The mandatory CGE questions (typically 12-15);
- The internal questions added over the years;
- The abandoned questions or those rarely filled in;
- The codifications used for employment status, sector, contract type.
The goal is twofold: (1) start from a clean base in the new tool, (2) guarantee statistical continuity with previous campaigns. If you abruptly change the wording of a key question, you lose year-over-year comparability.
Step 2 — Import the alumni database and prepare the profiles
The most structuring phase. The new software needs the alumni database as a CSV or via an API. Prepare a clean file:
- Stable identifiers: a unique identifier per alumnus (ideally the student number if you kept it, otherwise a generated UUID).
- Contact details: personal email, work email, phone, postal address if applicable.
- Academic path: class, major/specialization, degree type, honors, any dual degree.
- Special statuses: alumni doing a PhD, on a gap year, on a break year — to exclude or flag.
Take advantage of the import to deduplicate the database. Many alumni databases have 2-5% duplicates (marriages with name changes, double registration). The migration software should offer a duplicate detector based on configurable rules. For schools that started from a raw IS export, see also our article on the fundamentals of a good CGE response rate.
Step 3 — Configure the questionnaire in CGE/CTI format
Take the mapping from step 1 and transpose it into the new tool. Three points to watch.
Codifications. The CGE format imposes precise codifications for sector, contract type, geographic zone. Good software offers these codifications by default; failing that, you have to configure them once and for all.
Conditional logic. If the alumnus is "employed", you ask them the questions about their employer. Otherwise, you skip. This logic must be tested on 5-10 profiles before launch.
CGE / CTI differentiation. If your school is also subject to CTI (engineering school), you need two distinct questionnaires (with a common part). See our details in CTI vs CGE questionnaire: the 8 differences and the CGE vs CTI guide.
Step 4 — Run the first campaign in parallel
The classic trap: cutting off Google Forms overnight. Bad idea. The first campaign on the new software should run in parallel with the old tool for 2-3 weeks.
Concretely, you launch the year-1 class (6 months) on the new software, and keep Google Forms as a backup for residual questions or urgent reprocessing. This lets you:
- Compare response rates to the equivalent N-1 campaign (reassures management);
- Identify bugs or poorly worded questions before the 30-month campaign;
- Train the team on the dashboard and the exports.
Based on our field observations, from the very first campaign on the new tool, schools gain 10 to 15 points of response rate thanks to pre-filling and scheduled reminders. By the second campaign, the team has mastered it — and the gain becomes lasting.
Step 5 — Archive Google Forms and capitalize
Once the second campaign has succeeded on the new tool, you archive Google Forms. Three concrete actions: export all the CSVs from past campaigns and keep them in a secure school Drive; add to the internal report the note "2024 and earlier campaigns collected via Google Forms, 2026+ campaigns via [new tool]" — for traceability; finally, formally close the old Google forms.
On the final gains: across the schools we've supported through this migration, we observe, in a stable regime, +15 points of response rate, 3 to 5 person-days freed up per campaign, and GDPR alignment validated by the DPO. The cost of the SaaS is typically repaid by the second campaign. To get started, the fastest route is to book a demo.