Records, not just responsibilities
Testimonial Records When an Employee Leaves
The person who ran your testimonials is leaving, and the risk is not only that requests stop. It is that the evidence goes with them: the email where a customer said yes, the raw clip on their laptop, the note about which quote must never be used. Pull those records into company hands during the notice period, while the person who knows where they are is still there to ask.
- A CSV snapshot dated on their last day
- Permission emails out of a personal inbox
- Raw files off their own devices
The problem, solved
Where testimonial records hide when someone leaves
We need proof of what existed
Months later someone asks whether a quote was in the library before the leaver went. Without a snapshot, nobody can say.
With StoryProof: Export each space’s testimonials as a CSV from the workspace settings on the last working day, and store the dated files in a shared drive.
Customer permissions sit in their inbox
The reply where a customer agreed to be quoted on the website often lives only in one person’s mailbox.
With StoryProof: Forward or file those threads before the mailbox closes. If requests went out from that personal address, note that from Pro requests can leave from your own domain instead.
Raw clips are on their laptop
Longer recordings, interview files and edits made outside the app may never have reached a shared folder.
With StoryProof: Collect them into company storage. Video files you already have can also be uploaded directly into StoryProof, so the library holds them.
Only they knew the do-not-use list
A customer withdrew permission, or a quote names a former employee. That knowledge is usually unwritten.
With StoryProof: Tags are on every plan. Ask the leaver to tag every restricted testimonial with a clear reason before the export, so the file records it too.
Their access outlives their contract
An account left open after someone leaves is a quiet route to a file full of customer names.
With StoryProof: Roles and permissions are on every plan. Adjust the leaver’s role during the notice period, and remove them from the space on their last day.
Flip the switch to see how StoryProof handles each one.
Records checklist
Testimonial records to secure before the last day
Grouped by where the record lives. Work through it with the leaver during their notice period.
This list keeps its ticks in your open browser tab only. Close it and they clear.
Prompts
Questions to ask the leaver in the exit conversation
Short, specific questions get records out of someone’s head faster than a general request to hand over.
About permissions
- Which customers agreed by email rather than through the form?
- Has anyone asked you to stop using their words?
About material outside the app
- Where are recordings that never went into StoryProof?
- Did you keep any testimonials in a personal notes app or spreadsheet?
Leave out
- Asking them to delete anything before you have a copy.
In StoryProof
Notice period plan
- You will need
- A shared folder the company owns
- An hour with the leaver in their first week of notice
- 1
Week one: ask where things are
Use the exit questions to map records across mailbox, drive and devices.
- 2
Tag the restrictions
Have the leaver tag every testimonial that must not be used, with the reason.
- 3
Move the evidence
Permission threads, releases and raw media go to the shared folder.
- 4
Last day: snapshot and access
Export each space, then remove the leaver from the workspace.
What happens next: Hand the records note to whoever now runs testimonials, and keep a copy with HR’s leaver file if your policy allows.
Before you start
What this checklist does not cover
Not a full program handover
Who sends requests next and how the queue is run is a separate job. See the handover page.
The export is a snapshot
It records the library on the day you download it. Later changes are not in it.
Email retention is yours to set
Whether a closed mailbox can be recovered depends on your email provider and IT policy, not on StoryProof.
Check what the file holds
This page names no CSV columns. Open the export and note whether your reason tags appear.
Sender changes need a plan
Requests leave from your own domain and provider only from Pro. On other plans, check which address customers will see after the change.
FAQ
Questions people ask
Short answers to what usually comes up next.
Why export on the last day rather than the first?
Do both if you can. The last-day file records the library exactly as the leaver left it, including tags they added during notice.
Who should own this checklist?
The leaver’s manager, with HR. The successor owns the program afterwards, but the records are the company’s responsibility.
What if the leaver already left?
Export each space now, ask IT whether the mailbox can still be searched, and contact the person politely about any recordings they may hold.
Should restricted testimonials be deleted?
Tag them with the reason rather than relying on memory. A tagged record explains itself to the next person; a missing one does not.
Still have a question? Ask the StoryProof team or book a demo.
Records that do not walk out the door
Keep testimonials, tags and access in one workspace, and export a dated copy whenever people change.