The operating system for organizational memory
Tenure is the system of record for any organization where people rotate faster than knowledge transfers: clubs, university offices, teams, and growing companies. It keeps finance, events, approvals, members, and memory in one governed place, and Tenure AI turns that record into instant answers, so each new leader is productive in days, not a semester.
Runs alongside the tools you already use. No rip-and-replace. Founding Fall 2026 pilot with Simon's Office of Student Engagement.
Finance
auto-touring ↺Treasury balance
$12,400
▲ $1,300 · 11.7% this month
Budget by category
Founding Fall 2026 pilot
A year of relationships, vendor deals, budgets, and playbooks walks out the door, and the next person spends a semester relearning what the organization already knew.
Every other tool models people and rosters that wipe clean each year. Tenure models a durable seat, a position that keeps its money, contacts, playbooks, and decisions no matter who is sitting in it this term.
VP Finance & Operations
durable seat · SCC-VP-FINA-OPER
Occupant · term 2026–27
the person rotates ↻Institutional memory on this seat
records, carried across every handoff
Who’s our banquet caterer, and what did we overpay last year?
Prestige Catering. The ’25 gala ran $1,240 over, Marcus renegotiated it to a flat $3,800.3 sources ↗
Tenure isn’t a binder someone hands over on their way out. The work itself becomes the record, so every transition starts from everything that came before, not a blank page.
Finances, events, members, and decisions get logged as the work happens, no separate wiki anyone has to remember to update.
Knowledge belongs to the role, not the person who held it, so nothing walks out the door at term’s end.
They open a handoff packet assembled from the record itself, current the day they arrive, then ask Tenure AI about anything in it.
Every seat, side by side: who holds it now, who held it last term and how to reach them, how many knowledge cards are attached, and who is shadowing in. It isn’t a document someone remembered to write on their way out. It is assembled from the record, so it is current the day you open it.
Handoff packet
Student Culture Council · every seat, as of today
President
SCC-PRES
Dana Osei
Marcus Lee ’26
m.lee@u.rochester.edu
22
VP Finance & Operations
SCC-VP-FINA-OPER
Marcus Lee
Maya Chen ’25
maya.chen@alum.rochester.edu
34
VP Events & Partnerships
SCC-VP-EVEN-PART
Sana Ali
Ines Duarte ’25
i.duarte@alum.rochester.edu
19
VP Sponsorship
SCC-VP-SPON
Tomas Reyes ’26
t.reyes@u.rochester.edu
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
No departing officer writes this. Tenure assembles it from the seats, the approvals, the deliverables, and the ledger already on file.
There is no first day where somebody opens an empty account. Access attaches to the seat, so a handoff is a change of status, not a transfer of files, passwords, and folders somebody has to remember to send.
What the incoming officer sees: everything the seat can see, read-only, from the day they are named to the day their term starts.
The incoming officer is added to the seat with read-only access to everything it knows: past decisions, vendor terms, and the reasons behind them.
The same access becomes write access. Nothing is copied over and nothing is rebuilt, the seat simply changes hands.
The outgoing officer keeps their record and loses the keys. A seat that carries history is retired, never deleted, so the record stays where the work happened.
What the seat model is built to deliver, Fall 2026 pilot targets.
seat onboarding
the incoming officer gets read-only access to the seat's record before their term begins
knowledge lost at graduation
everything stays attached to the seat, not the person
approval chain, 7 request types
every decision appends a permanent step naming the seat that made it
of actions logged
immutable, RBAC-scoped, nothing silently editable
Finance, scheduling, approvals, members, documents, messaging, and memory: the dozen tools an organization juggles across spreadsheets and logins, unified into one record that every transition inherits.
Ask in your own words across everything the seat can see, plus the seat’s own private memory. Every answer links the records, files, and decisions it came from. No model is trained on your data.
How do we run elections?
Nominations open week 10, two-week window, ranked-choice ballot in the Members module.
Bylaws §4 · 2 records ↗Multi-step approval chains, routed by seat. Every decision snapshots the exact policy in force, so you can always prove the rules, not just who said yes.
Budgets, dues, reimbursements, and vendors in one ledger. Request, approve, and reconcile in place, with the full history kept by seat.
Plan events, vendors, and run-of-show. Tenure catches hard and soft scheduling conflicts before they become a double-booked room.
Hard conflict, Schlegel 207, 5:00 to 6:30p
The living record, decisions, context, and know-how that survives every turnover instead of leaving in someone’s head.
Roster, roles, and contacts, organized around positions that persist. Access follows the seat and revokes itself at graduation.
Contracts, decks, and spreadsheets open in Tenure: PDF, Word, Excel, and PowerPoint with speaker notes. Text files and spreadsheets can be edited in place, versioned, and Tenure warns you if someone else saved first.
Every allow and every deny, append-only. Denials are logged too, so you can prove nobody did something. Rows are only ever created, never updated or deleted.
budget.approved · SCC-VP-FINA-OPER · allow
Role-aware conversations with sensitivity levels and delivery across in-app, email, and push, threaded to the work they’re about.
A shared feed where teams co-host and partner. Every cross-org request is gated and audited by whoever oversees them.
Roll spending, participation, and continuity into board-ready reports, and search the entire record in one box, scoped to what you can see.
Budgets, dues, and reimbursements live in one ledger. Officers request, leadership approves, and the whole history stays with the role, so next year's treasurer sees exactly what things cost and who signed off.
Finance · fall
live$12,400 / $18,000
When leadership rotates, the work doesn't reset. Deals, contacts, and playbooks move to the incoming board with the context that made them matter, who built them, what they cost, and why.
Term handoff
2024–25 → 2025–26Outgoing
Incoming
$4,000 · Maya ’24
Ask Tenure in your own words (how a deal was closed, what the last board decided, why a decision was made) and get an answer grounded in the seat’s own record, with every source linked. The incoming officer gets read-only access to that record before their term begins, so the first week isn’t spent reconstructing the last one.
What's our sponsorship pipeline?
From last term’s sponsorship cards: Aramark renewal sent, M&T Bank a warm intro from Maya ’24 awaiting reply, Rochester Print at a standing 15% rate.
3 sourcesHow do we run elections?
Nominations open week 10, two-week window, ranked-choice ballot in the Members module. Last cycle’s timeline and the bylaws clause are attached.
Bylaws §4 · 2 recordsA dean, an operations lead, a finance office, a student-engagement director, anyone accountable for an organization gets real oversight, on the record. Approvals, audit, and access control are built in, not bolted on.
Live audit log, every allow and every deny, append-only.
Multi-step approval chains routed by role. Every decision snapshots the exact policy in force, so you can always prove the rules, not just who said yes.
event · budget · vendor · comms · document · roster
Access attaches to the seat, not the person. Incoming officers get read-only access before their term starts; outgoing ones keep the record and lose the keys. No orphaned access.
SHADOW → ACTIVE → ALUMNI
An append-only audit trail captures every allow and every deny. The denials are what let you prove nobody did something. Rows are only ever created, never updated or deleted.
allow / deny · create-only · 35 write sites
Multi-tenant isolation enforced at the query layer, not by convention. The tenant filter is attached to the database client itself, so no query can decline it, and every table in the schema must be classified before it can ship.
tenant-isolated · enforced in production · verified in CI
On the AI:Tenure AI reads only records you already have permission to see, and shows its sources. Answers are generated by Anthropic’s API from those sources. Your record is never used to train any model, by us or by them.
The pilot runs on both sides of the record at once: every organization the office stewards, and the office’s own administrators. One console across all of them, what is pending, what is vacant, and what got denied.
Administration console
Office of Student Engagement · every organization it stewards
Spring Gala vendor contract
$4,200 · Student Culture Council · SCC-VP-EVEN-PART
approval.force_approved · Director, Office of Student Engagement · allow
A director inherits everything staff can do, and staff inherit everything an advisor can do. So an advisor sees advising and a director sees everything, without anybody maintaining a permissions spreadsheet.
Publish or cancel an event, archive or restore a document or a memory card, adjust a budget, read the audit log. The console builds its own navigation from those powers, so nobody is shown a tab that would only turn them away.
Force-approve and force-reject work institution-wide and bypass both gates. Then they land in the audit log exactly like every other action, naming the seat that used them and when.
The outgoing director keeps their authority until the named successor accepts. Then the grant and the step-down happen together, in one move.
The director names a successor
Nothing moves yet. The outgoing director keeps every power they had a minute ago.
The successor accepts
Until they accept, the transfer does not exist. Nobody is half in, and nobody is holding a login that belongs to someone else.
One move, both sides
The grant and the step-down commit together, so the office is never without somebody who can approve.
The people rotate. The seat stays. Wherever turnover outpaces knowledge transfer, the same durable-seat model keeps the operations and the memory with the role, not the person who happens to hold it this term.
VP Finance & Operations · SCC-VP-FINA-OPERLeadership turns over every spring
Run the club and hand it off clean, finances, events, members, and a record the next board inherits on day one. No scattered drives, no lost passwords, no starting from zero.
Office of Student Engagement · DirectorOversees dozens of orgs at once
Govern every organization you steward from one seat, approvals, spending, and compliance that persist by role, without approving every bake sale. The knowledge you fund stops walking out the door.
Head of Operations · OPS-HEAD-OPEREmployees leave, roles remain
When someone resigns, their vendors, playbooks, and hard-won context shouldn't leave with them. The same seat model applies outside a university: knowledge attaches to the role, and whoever takes it next reads the seat's record before their first day in it.
Board Chair · BRD-CHAIAnnual board & volunteer rotation
Volunteer boards reset every year and relearn the same lessons. The same engine already configures a structurally different organization, programs, committees, sites, and funder relations in place of clubs and boards, so donor context and deadlines can persist across every term.
Committees, agencies, chapters, guilds, sports clubs, if the calendar changes the people but not the work, Tenure is the seat that remembers.
Upload the budget spreadsheet and Tenure reads your columns however you named them. Drop in the decks, contracts, and PDFs and they open in-app. Subscribe your Outlook, Google, or Apple Calendar with one signed link, no password shared.
ExcelContracts, decks, and spreadsheets open in the app, PowerPoint with its speaker notes. Spreadsheets and text files can be edited in place and versioned, and Tenure tells you if someone else saved first.
xlsx · docx · pptx · pdf
Outlook
Google CalendarSubscribe to the Tenure calendar from the one you already open. No account connection and no password shared: the link is signed to you, so it carries only what your seat is allowed to see. One-way today, Tenure fills your calendar and does not read it back.
signed feed · one-way today
ExcelUpload the budget you already keep. Tenure works out which column is which, whatever you named them, drops your subtotal rows so nothing double-counts, and shows you what it read before anything is saved. Or start from our template, generated by the same code that reads it.
columns auto-matched · preview before save
No. Tenure doesn't connect to them, it's where the record itself lives. Bring your spreadsheets, decks, and documents in, subscribe your calendar to Tenure's, and the files and decisions that define how the organization runs stop living in someone's personal account and start belonging to the role.
No. It's built for any organization where people rotate faster than knowledge transfers, student clubs, university offices, companies, nonprofits, and volunteer boards. The seat model is identical everywhere: knowledge stays with the role, not the person who holds it this term.
The organization does. Access passes cleanly to the next occupant at every transition, and nothing leaves with an individual when they graduate, resign, or roll off the board.
Days instead of a semester. Because the memory stays with the seat, Tenure AI answers from the role's own record, budgets, vendors, past events, and the reasons behind decisions. It doesn't train a model on your data; it surfaces and explains what's already in your record.
Yes. Tenure runs least-access by default, isolates each organization's data at the query layer, and logs every action to an immutable audit trail. The organization owns its records, not Tenure, not any individual. Documents are encrypted at rest and only ever served through short-lived signed links, never a raw file URL.
We're setting pilot pricing with Simon's Office of Student Engagement directly, at the level of the whole portfolio it stewards rather than per club, so it fits a real budget. Contact sales and we'll walk you through it.
Still deciding whether Tenure fits your organization? .
See Tenure on your organization's real handoff. A short walkthrough: we'll show you exactly what carries forward.