You know the file exists. You remember saving it after a long meeting, probably with a name that made perfect sense at the time. Now you're preparing a review, searching three folders, and opening documents called final, final2, and final_revised. There goes the afternoon.
Keeping records helps. But keeping everything in the same pile doesn't give you a usable dossier. Your working archive and your submitted dossier have different jobs, and separating them can make the whole process feel less overwhelming.
Your archive helps you remember.
The book recommends maintaining an evolving record of your teaching, scholarship, service, and professional development. Think of this as the place where you preserve material before you know exactly how you'll use it. A course revision, a grant decision, or a committee report can go there while the details are still fresh.
The archive can hold more than you'll eventually submit. Keep working notes alongside the appropriate records, clearly labeled as notes. Write down what you did, who else contributed, and why the work mattered. Six months later, that short explanation may be more useful than the attachment alone.
Use approved storage and handle sensitive material according to institutional requirements. Student work, personnel information, and confidential committee documents aren't ordinary attachments. Saving them somewhere convenient doesn't automatically make that location appropriate.
Your dossier helps someone evaluate.
A submitted dossier isn't the entire archive with a nicer cover. It's a selection organized around the actual review requirements. The reader needs to understand your contribution, find the relevant evidence, and see how that evidence supports the claims you're making.
Imagine a hypothetical course redesign. Your archive might contain planning emails, several assignment drafts, peer feedback, and notes from teaching the revised course. The dossier may call for a short explanation and selected supporting materials. Dumping every draft into it could hide the meaningful change rather than clarify it.
Follow the required submission rules, including any obligation to provide complete records. Selection means organizing within those rules, not removing inconvenient required evidence.
Connect each selected item to a purpose.
Before adding an attachment, ask what it establishes. A syllabus can show the structure of a course. It doesn't, by itself, demonstrate that students learned more. A committee appointment confirms a role. It doesn't explain your contribution to the committee's work.
That distinction makes your writing sharper. You can describe an activity, identify an output, and explain what you can reasonably conclude from the available evidence. You don't have to make every attachment prove everything.
Build a small routine between reviews.
Once a month, give new records clear names and place them in the appropriate teaching, research, service, or development folder. Add dates and a sentence of context. Keep a separate list of possible examples for the next review, but wait to finalize the selection until you've checked the applicable requirements.
When submission time comes, make a separate working copy for that specific review. Label the period and version clearly. Preserve the broader archive so you don't have to rebuild it for another purpose later.
Start today with one recent accomplishment. Save the appropriate record, add a short note explaining your role, and name the claim it could support. That's a manageable beginning. You don't need to organize your whole career before making the next review easier.
Adapted from The New Faculty Handbook by Zafer Unal, chapter 14, pp. 223–226.
