
Education
Chairs, deans and student leadership turn over on a fixed calendar, and the reasoning behind last year’s budget leaves with them.
The system of record for organizations that rotate
Budgets, vendors, approvals and the reasoning behind them attach to the seat, not to whoever is holding it this year.
Already using Tenure? Ask us for your sign-in, accounts are set up in advance for a named person, so there is no public signup to find.
Finance
Treasury balance
$12,400
Budget by category
Illustrated interface, with representative data.
Connects to the systems your office already runs on
Once when a year of relationships, vendor terms, budgets and playbooks walk out the door, and again while the next person relearns what the organization already knew.
The handoff, both ways
one row per thing that is lost, and what keeps it
Turnover is scheduled in some industries and constant in others. The mechanism does not change: attach the record to the seat, and whoever holds it next starts from it.
Other tools model people, and the roster wipes clean every cycle. Tenure models a durable seat: a position that keeps its money, contacts, playbooks and decisions no matter who holds it.
Term 2026–27
the person rotatesInstitutional memory on this seat
12
records, carried across every handoff
Term 2027–28
handoff 1+ 1 more alumni on this seat
Institutional memory on this seat
34
records, carried across every handoff
Term 2028–29
handoff 2+ 2 more alumni on this seat
Institutional memory on this seat
58
records, carried across every handoff
Twelve modules on one record. Work happens here, so the record writes itself, pick any one to see what it actually does.
Tenure
one organization · one term · one record
Budgets, allocations, spend, reimbursements and vendor terms in one ledger, approved in place.
Where a committed dollar sits
Reimbursements this term
Tenure assembles it from the database when you open it. No AI, and nothing for the outgoing holder to remember.
Handoff packet
Student Culture Council · every seat · worked example
President
SCC-PRES
Dana Osei
Marcus Lee ’26
22
VP Finance & Operations
SCC-VP-FINA-OPER
Marcus Lee
Maya Chen ’25
34
VP Events & Partnerships
SCC-VP-EVEN-PART
Sana Ali
Ines Duarte ’25
19
VP Sponsorship
SCC-VP-SPON
Tomas Reyes ’26
27
3 requests
two sitting in the office gate
2 deliverables
next one closes in 6 days
$12,400
of $18,000 committed this term
An incoming holder gets read-only access to the seat’s record before their term begins, then searches it, and gets an answer built from what past holders filed as they worked, with the records it came from linked.
sponsorship renewal
From last term’s sponsorship cards: Halden Catering renewal sent, Harbour Mutual awaiting reply after Maya ’24’s intro, Fenwick Print at a standing 15% rate.
3 sourceselection nominations
Nominations open week 10, two-week window, ranked-choice ballot in the Members module.
2 recordsTenure AI is given only records you can already open, and answers link the records they came from. Text goes to the model service, inside our own cloud account, for three things: the records retrieved for a question, a text document someone asks to summarize, and an instruction typed into Draft Assist. Your records stay yours, they are never used to train a model. The controls behind it →
Every organization you steward on one screen: who holds which seat, what is pending, what got denied, and a console whose navigation is derived from the capabilities your own seat actually holds.
Administration console
Office of Student Engagement · worked example
Sections
Spring Gala vendor contract
$4,200 · Student Culture Council · SCC-VP-EVEN-PART
approval.force_approved · Director · allow
No. Tenure is where the record lives, alongside them. Your budget spreadsheet imports with whatever the columns were called; PDF, Word, Excel and PowerPoint open in place rather than downloading to someone’s laptop; deadlines publish to Outlook, Google or Apple Calendar through one signed link per person. Beyond that, the integration catalog covers Slack, Microsoft 365, Google Workspace, Box, Dropbox and Zoom among others. Everything it connects to →
The organization does; access attaches to the seat, not the person. An incoming officer gets read-only access to the seat’s record and knowledge cards before their term begins, and when a term ends the record stays on the seat while the outgoing officer’s access does not.
Isolation is enforced at the query layer by the database client itself, so an individual query cannot opt out of it, and privileged actions append to a create-only audit trail that records refusals as well as approvals. Documents are encrypted at rest and served through signed links that expire in ten minutes. What isn’t built →
The seat is what holds the work, so nothing has to be reassembled. The departing person moves to alumni: their access ends, and the budget, vendors, approvals and decisions filed against that seat stay exactly where they were. Whoever takes the seat next opens the same record on their first day.
Onboarding runs live with your office rather than as documentation and a login. Accounts are created in advance against named people, the first import from your existing drives is done together, and the seat map is built before the first rotation so the record has something to attach to.
Yes, and that is the point of the console. Staff work through sixteen capabilities across three strictly nested tiers, and the tier decides which actions are offered at all. Approvals show which seat decided, what the request moved from and to, and how long it has been sitting.
They are your organization's records, not ours. The account is exported on request in full, and the seat model is what makes that coherent rather than a folder dump: everything is already attached to the position it belongs to.
Pricing is per portfolio, not per organization: one budget line covers every organization a body stewards, whether that is a university office, a national association or a nonprofit with regional chapters. A single organization is priced on its own. Figures are set in a written agreement rather than published on a page, and the first deployment term runs free.
Something we haven’t answered? Request a demo.
See Tenure on your organization’s real handoff. A short walkthrough: we’ll show you exactly what carries forward.