The archive
LegacyLegacy
The legacy file: what I want my daughter to be able to verify about my work
A folder, a format, and a rule that every claim inside it has to survive being checked by someone who was not there.
Adele FournierArchitect, retiredOct 22, 20267 min read
After thirty-one years of practice I began a file that is not a portfolio. A portfolio argues. This is meant to be checked.
The rule Every project gets one page: what I was asked to do, what I decided, what it cost, and what the client signed. If a claim cannot be supported by a document in the folder, it does not go on the page. Not softened — removed.
What survived Thirty-four projects. Eleven of them are buildings I am proud of. Six are buildings that went badly, and those pages are the most complete in the file because I had the most to explain.
The rest are ordinary work. Ordinary work is most of a life, and leaving it out would make the record a marketing document.
Why bother My daughter is an engineer. She will inherit an opinion about what I did, formed mostly from what I said at dinner. I would rather she inherited an index — dates, permits, sign-offs, and a note in my handwriting about the roof that leaked.
A record like this is not for the people who already believe you. It is for the person who arrives after you, with nothing but the folder.