What changed after the switch
Three departments, three different reasons for leaving their old editor, and what actually happened afterward.
40%
fewer formatting fixes before submission
Kestrel Systems Lab
A 12-person computational biology lab moved off a shared account on a traditional editor after a formatting conflict cost them a day before a deadline. Six months in, their coordinator tracked a 40% drop in last-minute formatting fixes across the group's projects.
“We didn't switch for the AI. We switched because compiling stopped being a coin flip. The AI review turned out to be the part we now can't work without.”
— Postdoctoral Researcher
34
active projects migrated in one weekend
Northgate Polytechnic, Physics
The physics department ran two rounds of PhD defenses on the old setup before deciding the per-seat collaborator limits weren't worth it anymore. The graduate coordinator moved 34 active projects over a single weekend using the ZIP-import flow.
“I expected the migration to be the hard part. It took an afternoon. Explaining to faculty why we hadn't done it sooner took longer.”
— Graduate Program Coordinator
3 weeks
before a NeurIPS deadline, they switched anyway
Bellcourt University, Applied Statistics
A broken .cls file three weeks before submission forced an unplanned switch mid-cycle. The lecturer expected friction; the department stayed on Scripta afterward without anyone asking them to.
“We migrated out of necessity, not conviction. The conviction came from actually using it for a month.”
— Senior Lecturer
Want to see if Scripta fits your group?
See pricing