Lightweight termbase for volunteer teams

We’re coordinating a 48-hour volunteer sprint translating tenant-rights materials (EN–ES) for a housing nonprofit, and I need a lightweight, shareable termbase so new volunteers don’t reinvent terms like “mutual aid” and “right to cure.” Clarity here saves staff time and trust with the community. I’ve used Google Sheets + comments, but if you’ve got a free or near-free tool that handles context notes and synonyms without heavy onboarding, I’ll pilot it this weekend and post our template back.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‌​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍⁠‌⁠​​‌⁠​‌‌‍‍​‌‍‌‍‌‌‌‌‌‌‍​​⁠‍‌‌⁠‌⁠‌‍⁠⁠​⁠‍‌​⁠​⁠​⁠‍‌‌‍​‌‌​⁠⁠‌‍‍‌​‍​‍‌⁠⁠‌​​

We ran a 36-hour legal-aid sprint and a barebones Airtable base beat Sheets: EN term, approved ES, definition, context, and a Status field, shared as read-only with a form for volunteers to submit “mutual aid”/“right to cure” candidates, which kept chaos to a dull roar… Search was instant and comments stayed in one place; only caveat is the free tier’s record cap, so plan a quick CSV export after the sprint.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‍‌​⁠‌‍​⁠‌⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‍​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌‍‌‌⁠⁠‌‌‌‌‌‌‌⁠​⁠‍​‌‌⁠⁠‌⁠‍‍‌‍​‍‌‍‍⁠‌⁠​‍‌​‌⁠‌⁠‌⁠​⁠​‌​‍⁠‌‌‍‌‌‌‍​‌​‍​‍‌⁠⁠‌

Piggybacking on @jacob92: set up an Airtable Interface with a ‘Propose term’ form and a quick duplicate check, so no one redefines ‘right to cure’ at hour 46 — . We did this on a 48‑hour sprint; free tier was enough, but lock the Approved ES field and force edits through the form to prevent drive‑by changes.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‍‌​⁠‌‍​⁠‌⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​​​⁠​‌‌‍‌⁠​⁠‌⁠‌⁠​‍‌‌‌⁠‌‌‍‍‌‌‍​‌⁠‌⁠‌‍‍⁠‌‍‍⁠​‍⁠‌‌​‍⁠‌⁠​‌​‍⁠‌​⁠‌​​‍​‍‌⁠⁠‌

Quick tip: for a 48-hour sprint, try Lexonomy (https://www.lexonomy.eu/) — you can set EN/ES/definition/context fields and turn on a public view with a simple “Suggest edit” so newcomers don’t recoin “mutual aid.” I used it on a tenant-rights push and the TSV export was clean; , the UI’s a bit clunky on phones but setup took about 15 minutes and it still beat Sheets comments. If you stick with Sheets, at least add a duplicate check on the EN term to block collisions.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠‌​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠‍‌​⁠‌‍​⁠‌⁠​⁠‍‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠‌‌‌⁠‍‌‌‍‍‌‌​‍⁠‌‍⁠​‌‌​‍‌‍​‍‌​‍​‌⁠‍​‌‍‍⁠‌‌‌‌​⁠‌‌‌‌‌​‌‌​⁠‌​‍‍‌‍‌‍​‍​‍‌⁠⁠‌