One system for how your organization actually runs.
Finance, events, members, documents and institutional memory in one governed record, and a handoff packet the next holder inherits already written. Below: the data model, what a week looks like on each side of it, and exactly what Tenure connects to. Every control, and what verifies it on each build, is set out on Security.
Finance, events, members and memory, one screen.
Memory
click a module ↗Records
142
carried across 3 terms
Decisions logged
38
↳ inherited from Dana Osei · FY24
↳ inherited from Priya Nair · FY25
↳ inherited from Sana Ali · FY25
↳ inherited from Priya Nair · last term
Illustrated interface, with representative data.
The record fills itself as the team does the work.
Nobody writes the handoff document at the end of the cycle. Tenure keeps four kinds of record current as the work happens, so the next board inherits the real thing rather than a scramble of screenshots and a shared drive nobody can navigate.
What lives on the seat
four kinds of record, kept current by the work itself
Contacts & relationships
01Sponsors, funders, partners and alumni, with the warm intro and the last conversation kept behind each name.
Deals & numbers
02Vendors, pricing and budgets, the real terms that were agreed, not a number someone half-remembers.
Decisions & rationale
03What leadership chose and why, so next year does not relitigate a call that was already settled.
Files & playbooks
04Decks, timelines and run-of-show checklists, the documents that carried the work, not a dead folder.
The next holder starts from everything that came before.
When a leader leaves and the next one takes the seat, they do not start from zero. They search the seat’s own record and get the sources back, with an answer whenever Tenure can ground one in them.
Ready on day one. Tenure AI answers from the knowledge, decisions and events recorded against the seat, from day one. Retrieval is literal keyword matching, every word of a question has to appear in a record, so short, specific queries work and full sentences often return nothing.
Answers link the records they came from. Responses link back to the records, files and decisions they were drawn from, and the model is only ever given records you are already allowed to see.
The knowledge stays with the seat. When this holder moves on, the next one inherits the same working memory, intact.
Ask Tenure
Treasurer seat · day 1
You searched
gala date change
The board moved it after the October attendance review, and the new date cleared the office the same week. See the decision card and the approval behind it. 2 sources ↗
You searched
fall mixer
The board moved that budget to the gala after low turnout. See the October decision log and the vote behind it. 2 sources ↗
Not a pitch deck. The mechanics, exactly as they work.
Every dollar, tracked and approved in place.
Budgets, allocations, 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
Records cross the term with their history intact.
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
Illustrated interfaces, with representative data.
What it connects to, including what it does not.
Most of this page describes what Tenure does. This part describes what it will not do for you, in the same words we would use in a security review, because finding out in week three is worse for both of us.
What Tenure connects to
5 rows, including the ones that say no
What comes in
3 liveThe files you already keep, opened and edited in place. Nothing to migrate.
Documents
.pdf.docx.pptxOpen them inside Tenure instead of downloading them to somebody’s laptop. Speaker notes come through with the deck.
Spreadsheets
.xlsx.csvEdit in place, with a warning if someone else saved first. The budget you already keep imports as it is: Tenure works out which column is which whatever you named them, and shows you what it read before anything saves.
Text and data files
.txt.md.json.xmlEdit in place like the spreadsheets. These four are also the only files the assistant will summarize, not PDF, not Office.
What goes out
2 liveWhat Tenure sends outward, into the tools people already open.
Your calendar
OutlookGoogle CalendarApple CalendarOne signed link per person, pasted into whichever calendar they already open, no account connected, no password shared. One-way: Tenure fills your calendar and never reads it back.
Deadline reminders
in-appPublish a deadline once and every organization sees it, with each person reminded once. In-app only, nobody is emailed.
See it on your own record. Not a demo org.
Tell us which modules matter and we will open exactly those, on a demonstration organization built like yours.