Their Files Stay. Your Record Goes With You.
One line from a status deck
Here is a line from a quarterly status deck. The details are invented and the names are bracketed, but the shape will be familiar to anyone who has run a remediation program at a bank:
Q3: 4,212 high-risk KYC files remediated for [client name], three weeks ahead of the [regulator] exam. [Vendor] model cut average review time 38%. Tracker attached: KYC_Remediation_Q3_v14.xlsx
Say every word of it is true. Almost none of it is yours to take.
The count came out of their system. The client and the regulator are named. The 38 percent is a vendor's number under a contract you didn't sign. The tracker is a company file with fourteen versions of other people's work in it. It's a good line for the deck it lives in. As a record of your career, it's a line you can't keep, and it doesn't say what you did.
This is the season to notice that. The signs of a restructuring usually arrive before the memo does: a hiring freeze, a program paused at the budget review, a reporting line that changes twice in a quarter. Ottawa has sent 25,368 public servants letters telling them their jobs are affected, according to the government's workforce reduction figures as of mid-September. The big banks close their fiscal year on October 31, and at TD, restructuring charges were reported with the fourth-quarter results in late November 2023 and again in early December 2025. If you work in either place, the window between the signs and the announcement may already be open.
That window is when most people first ask what to keep when you leave a job. They usually ask it late, and the usual answer points at the wrong record.
"Save everything" is the wrong record
The usual advice for this window is to save everything: forward the emails home, export the decks, take a copy of the tracker. It feels like prudence, and it's the one record you're not allowed to keep.
One Ontario case makes the point. In April, an employment firm wrote up a case in which an employee downloaded hundreds of company files to a personal device before leaving: customer lists, pricing, sales data, business plans. The court ordered the files returned. The firm's summary of the principle fits in a sentence: information that belongs to your employer isn't yours to take, and even one customer list or set of files can breach your obligations. On that case's facts, the same court refused to stop the employee from working with those clients afterwards; a non-solicitation clause in your own agreement may say otherwise.
Relationships and experience travel. Files don't.
None of this is legal advice, and your own employment agreement or contract, and the confidentiality policies you work under, are what actually govern you. If you're unsure, ask an employment lawyer before you copy anything. But the general line is clear enough to plan around, and it holds for contractors as much as for employees: a client's files were never yours to begin with.
Relationships and experience travel. Files don't.
The copy wouldn't have helped anyway
Here is what the save-everything advice misses even when the files are harmless. A copy holds what happened. It doesn't hold why.
The tracker can tell you 4,212 files closed. It can't tell you that in week three you stopped working the queue in the order the files arrived and started working it by risk, because the oldest files weren't the riskiest ones, and that the change is what got the program to the exam with three weeks to spare. That decision is the part of the job an interviewer asks about, and it's in no file. It's in your head, and it starts to fade the week the program closes. I've written before about how outcomes survive and the reasoning doesn't. This is the same problem with a deadline attached.
It's the record you can't keep, and it's the record that wouldn't have helped.
So the copy-everything record fails twice. It's the record you can't keep, and it's the record that wouldn't have helped.
What goes with you
The record that does go with you is smaller, and better. Four things:
- Your own words. Written by you, about what you did. Nothing pasted from their documents, even the parts you wrote for them.
- The date, to the week. Memory keeps the event and drops the when, and the when is what makes a record believable.
- The decision and the reason. What you chose, what you chose it over, and why. This is the part no file holds.
- The number, rounded. About 4,000 files. Three weeks early. Your result, at a precision that doesn't reproduce anyone's system.
And what stays with them:
- Client, colleague and vendor names.
- Documents, decks, trackers, code and data, including your own drafts of them.
- Anything marked confidential, or anything that would let someone rebuild something that is.
- Anything they own, including your access. Nothing you write down should help you reach their systems after you've left.
A practical test, not a legal one: if you'd say the line out loud in an interview, word for word, it belongs in your record. If you'd lower your voice to say it, it stays behind.
Write it before the window closes
The timing matters more than the format. Access doesn't always end on a schedule you're given. In September, some Oracle staff reportedly had their email and files cut off before a 6 AM message told them it was their last day. Nobody should be building a record that morning, and nobody has to if it was written as the work happened.
The habit is small: ten minutes when something changes. A decision made, a number that moved, a program that closed. If restructuring news is weeks away where you work, now is a good time to start, while the last quarter is still fresh. It's a bad time to start copying. And if you're forty and nowhere near a restructuring, it's the cheapest time of all, because the record is built from this week's work instead of rebuilt from memory later.
The line, rewritten
Here is the Q3 line again, rewritten as the record that goes with you:
Shorter on data. Longer on you.
Where Tenure fits
I built Tenure because I kept running into this problem from the wrong side of it. The premise is simple: your career is an asset, and like any asset, it needs to be maintained. Not just dusted off when you need to sell it. Tenure is the platform built around that idea. It's live at owntenure.ca. Free trial, no credit card required.
Two of the modules map onto the four things above. Tool Filing Assistant captures the work when it happens, dated, so the record doesn't depend on what you remember in the last week. BattleCard keeps the decision and the reason next to the result, which is the part a tracker never held. Tenure doesn't change any of this. What you write in it follows the same list: your words, rounded numbers, and nothing from the stays-with-them list.
The line, rewritten
Here is the Q3 line again, rewritten as the record that goes with you:
Week of Sep 21, 2026. Led the remediation of about 4,000 high-risk customer files, finished three weeks before a regulatory exam. In week three I reordered the queue from oldest-first to highest-risk-first, because the oldest files weren't the riskiest ones.
It's shorter on data and longer on you. The client is gone, the vendor is gone, the file is gone, and for the first time the line says what you decided and why. Nobody can ask for it back, because it was never theirs.
Shorter on data. Longer on you.
Their files stay. Your record goes with you. Write it before you need it.
Own your tenure.