How to Manage Coaching Client Documents Without Tresorit
Nour
Founder, Coachful
You can manage coaching client documents without Tresorit by first deciding what belongs in a shared client workspace, what requires a more restricted location, and who is allowed to see each item. Choose storage that meets those requirements, then build a consistent document workflow around it.
Tresorit uses client-side end-to-end encryption and offers secure sharing. A general coaching portal should not be presented as an equivalent security architecture merely because it also stores files. Coachful can make everyday resources and coaching preparation easier to organize alongside the engagement. Some practices will still need a separate encrypted repository for particularly sensitive material or an employer’s required system.
Coachful is our #1 recommendation for everyday coaching resources that appropriately belong alongside the engagement. That recommendation does not establish equivalence with Tresorit's security design. Keep the approved repository when the material, agreement or employer requires it, even if the resulting workflow uses two tools.
A client workspace and an encrypted repository solve different needs
| Document need | Question to answer | Possible approach |
|---|---|---|
| Everyday coaching resources | Can the client easily find the current worksheet and know what to do with it? | Organize relevant materials in the client’s coaching workspace. |
| Sensitive employer reports | What contractual, security, and access requirements apply? | Use an approved repository when required; share only an appropriate summary elsewhere. |
| Private coach notes | Who needs access, for what purpose, and for how long? | Keep these separate from material deliberately shared with the client or sponsor. |
| End-of-engagement records | What must be retained, returned, exported, or deleted? | Define an offboarding process rather than leaving every file available indefinitely. |
A simpler experience is valuable when it also fits the confidentiality requirements. It is not a reason to downgrade a control without discussing the consequences. Compare security documentation, data handling, contractual terms, and the actual permissions of the tools you are considering.
Tresorit's current documentation describes device-side encryption and permission controls. Its Send transfer service has its own link lifecycle; do not apply one transfer product's expiry rules to every business repository or retention decision. Compare the actual product, configuration and agreed process. A button that revokes a link is not evidence that every recipient's earlier download has disappeared.
Reduce document friction without weakening confidentiality
Clients often struggle because documents have no obvious purpose or location. An attachment is sent before a session, a revised version appears in a message, and the original remains in a shared folder. The client completes the wrong one. The problem is not encryption itself; it is an unclear document process.
Give each document a recognizable title, a short explanation, and one current location. “Delegation reflection, complete before 12 November” is more useful than “Worksheet final v4.” When a resource changes, make it clear which version is current. Where a historical copy matters, keep it identifiable rather than silently replacing a record.
An employer may require a 360-degree feedback report to remain in its own system. Respect that requirement. You can still coach from a client-approved action summary without uploading the full report into every tool you use. Ask what information is necessary for the coaching purpose before creating another copy. For the everyday resource process, see managing client documents and worksheets.
The pictured Agreements area is for filing PDF agreement records, including contracts signed outside Coachful. It is not a general reason to place an employer report there. A file can upload successfully while belonging to the wrong process. Check the person matched to the record and who can access it; an automatic match is a suggestion to verify, not evidence of permission or a newly completed signature.
Create a document map for the engagement
Separate resources from records. A blank reflection worksheet is reusable content. A completed worksheet contains the client’s information. A signed agreement is a commercial and professional record. A private note may contain observations that were never intended for a sponsor. Treating all four as interchangeable files makes access decisions harder.
Use Coachful’s resources and coaching spaces for the material that belongs with the client’s work. Confirm the actual sharing and assignment settings. Do not assume that a sponsor relationship automatically creates the correct access boundary or that a file attached in one context is private in every other context.
The ICF Code of Ethics emphasizes clear agreements and responsible handling of records. Put that into practice with a written agreement about what may be shared, with whom, and for what purpose. Revisit the agreement if a sponsor asks for a new category of information.
- Shared client work: preparation, agreed goals, resources, and action summaries.
- Restricted professional records: private notes and other material requiring a different access decision.
- Sponsor communication: only the updates specifically agreed with the client and sponsor.
- Financial and contract records: kept for their defined administrative purpose.
A 360-feedback review with an explicit sharing boundary
Consider an executive bringing a feedback report to a coaching session. The coach’s first task is to establish permission and purpose, not to upload the report into a convenient folder. This is an illustrative dialogue.
Coach: What permissions or restrictions came with this report?
Client: It is for my development. HR can see it, but I am unsure whether I can upload it elsewhere.
Coach: Let us keep it in the approved location until that is clear. What would you like to work on from it today?
Client: People say I interrupt. I want to practice leaving space before I respond.
Coach: Would a brief action summary help? We can record the behavior you choose to practice without copying comments that identify other people.
Client: Yes. I am comfortable sharing that action with my sponsor, but not my reflections on individual colleagues.
Document that distinction in the agreed way. A sponsor paying the invoice does not settle permission for every private reflection. If access requirements are ambiguous, clarify them before sharing. A coach should not promise confidentiality that the configured system or contract cannot support.
In the fictional continuation, Arun is the client, Selma the coach, Mira the employer's records contact and Olin the sponsor. At their fifty-five-minute session on Monday 4 September 2028, Arun declines moving the full report or completed personal reflection. Selma initially proposes using the convenient PDF agreement-upload area for the report. Arun points out that it is neither an agreement nor approved for that destination. Selma withdraws the suggestion. They create no extra report copy and ask Mira to confirm the permitted discussion route.
Set up a clear document workflow
- List what you hold. Identify agreements, blank resources, completed reflections, recordings, assessments, and notes. Include copies in email and local folders.
- Assign a purpose and audience. Decide why each category is needed and who should access it. Avoid copying an entire archive into a new portal by default.
- Check the storage requirements. Review client contracts, employer rules, and relevant professional or legal obligations with suitable advice when needed.
- Create a simple structure. Use understandable names and a clear current version. Put a short instruction beside each assigned resource.
- Confirm permissions. Inspect what the intended client and any staff or sponsor role can access. Correct accidental sharing before adding sensitive files.
- Plan offboarding. Decide how clients receive appropriate final materials, what remains accessible, and what is retained or removed under your policy.
Move an ordinary resource first and review the experience. Then migrate only approved content. Keep an inventory so you can account for copies that remain in the old system. Closing an account does not by itself establish that every local download, backup, or email attachment has been removed.
Test an ordinary, non-sensitive resource before making a larger change. Check the instruction, the intended account or guest route, the actual readers and the required action. A preview and a completed response answer different questions. If the client cannot use the route, agree a simpler appropriate method rather than silently enrolling them in a program or broadening a folder's audience to remove the error.
A document register that stays manageable
| Field | Example | Why it helps |
|---|---|---|
| Title and purpose | Delegation action summary for the next two sessions. | Explains why the document exists. |
| Owner and audience | Client owns the reflection; coach and client can view. | Prevents an assumed sponsor or staff audience. |
| Current location | Named resource in the client workspace. | Avoids several competing copies. |
| Review or retention date | Review at engagement close under the agreed policy. | Creates a point for a deliberate decision. |
| Sharing restriction | Do not include identifiable colleague feedback. | Makes a practical boundary visible. |
Keep this register proportionate. A solo coach does not need a complex filing taxonomy for ten ordinary worksheets. The point is to know what you have and make deliberate decisions. More sensitive records deserve more careful handling than blank resources.
For a completed worksheet, retain enough context to understand it later: the date, the question being answered, and the client’s chosen action. Avoid collecting names, health information, or third-party details unless they are needed for the agreed purpose. A reflection about a difficult meeting can often use roles rather than a list of identifiable colleagues.
Prepare for three common document problems
The client completes an old version. Thank them for the work, identify whether any missing question is actually needed, and send the current version with a short explanation. Then remove the obsolete assignment from the obvious client path. Do not make the client repeat an entire exercise just to satisfy your filing preference.
A sponsor requests private notes. Refer to the agreement and discuss an appropriate update with the client. A summary of attendance or agreed goals may be within scope when detailed reflections are not. If the request introduces a conflict with your responsibilities, address that conflict directly rather than granting access because someone is senior.
A file goes to the wrong person. Act promptly through your incident process: restrict access where possible, establish what was shared, seek appropriate advice, and follow applicable notification duties. Deleting a visible link may not remove a downloaded copy. Document the facts and correct the underlying access or naming problem.
Arun completes the older blank worksheet from an email on 6 September. Selma initially asks him to repeat it in the portal. Arun objects that the revision adds only one question and he has already done the relevant thinking. Selma accepts that criticism. They keep his dated original response and agree a short addition answering the new question, without pretending the old response was submitted against version two. Selma removes the obsolete link from the active instructions and explains where the current blank is. Arun keeps his earlier annotated download as a historical copy.
At the end of the engagement, explain the practical next step. If clients should download a final plan, tell them where it is and when access changes. Confirm available export options before promising an archive. A thoughtful close is easier when document access and retention were discussed at the beginning.
A migration example: move a worksheet, retain a restricted report
Imagine a coach holds three items for one engagement: a blank delegation worksheet, the client’s completed reflection, and an employer-owned 360 report. These should not move as a single folder simply because they belong to the same person. Review the purpose and permission for each one.
The blank worksheet may be an ordinary reusable resource appropriate for the coaching workspace. Give it a clear title and confirm which version the client should use. The completed reflection contains personal information, so check its intended audience and whether the client wants it moved. You may decide that only the agreed action summary needs to be available in the new location.
The 360 report may need to remain in the employer-approved repository. If the client is permitted to discuss its themes, coach from that discussion and record only an appropriate action. Do not download and re-upload the full report to save one login if doing so conflicts with the applicable arrangement.
Keep a migration note that says which item moved, which stayed, and why. Tell the client where to find the active materials. Remove obsolete links from the obvious workflow when appropriate, while handling retained copies under your policy. This gives you a coherent process without claiming that every file now has the same protection as Tresorit’s end-to-end encrypted storage.
For Arun, the initial inventory has exactly three items: the blank worksheet, his completed reflection and the employer report. Only the approved blank resource is copied to the coaching workspace. The other two stay in their agreed locations. Arun and Selma then create a fourth item, a new action summary limited to pausing before responding and checking the other person's deadline. It is not a redacted replacement for the whole report or a migration of the personal reflection.
Mira confirms that discussion of relevant themes is permitted but asks that the report remain in the employer repository. Olin asks for the colleague-level comments anyway. Arun says no, and Selma declines the request. With Arun's explicit approval, Olin receives only the chosen action and the date on which Arun intends to review it. Selma withdraws a draft sentence saying Arun consented to uploading all feedback. He has given narrower permission. That false sentence is corrected before the summary is released.
At the thirty-minute review on 11 September, Arun ends the defined two-session document review and asks for a readable final action summary. Selma promises it by Tuesday 12 September at 13:00. The first prepared attachment contains the outdated instruction to repeat the whole worksheet. Selma catches it during the agreed review before sending, replaces it, and delivers the corrected final copy on Thursday 14 September at 10:20. It is forty-five hours and twenty minutes late. Arun opens it on his phone at 11:05 and confirms that the action and version are correct. Usability does not erase the missed commitment.
Selma apologizes and records the delivery failure. The fifty-five- and thirty-minute sessions total eighty-five client-facing live minutes. Her selected administrative record separately totals forty minutes for inventory, thirty for readability and audience checks, and twenty-five for the wrong-version repair: ninety-five minutes. These categories are separate from the live sessions and are not a complete labor cost or proof of financial savings. The late repair remains Selma's responsibility after the defined service ends; Arun does not need to buy more coaching to obtain the promised copy.
They close with the permitted final summary delivered, the restricted report retained and the old local worksheet copy explicitly accounted for. Arun declines a portal renewal and declines any claim that pausing practice has already improved his workplace relationships. The planned 18 September workplace check has not yet happened. Access and retention follow the previously agreed process, with any remaining export or removal work named as pending until actually completed. Neither party describes this mixed result as a complete secure migration of every record.
Choose a document format by the work it supports
A blank reflection prompt, a signed agreement, and a complex report need different experiences. A short form can make a recurring check-in easy to complete. A fixed document may be more suitable when the layout or the exact issued version matters. A spreadsheet may be needed for calculations, but it creates extra work if the client only needs to answer three questions.
Ask whether the client needs to read, complete, annotate, sign, or retain the item. Then check that your chosen format and tool support that task. An uploaded PDF that can be viewed is not necessarily an editable worksheet or a supported signing process. Make the instruction accurate: “Download and complete” means something different from “Answer the questions here.”
For recurring resources, make future changes deliberately. If you revise a prompt, decide whether earlier completed responses should remain attached to the version the client answered. Preserving that context can matter when reviewing progress. Convenience should not erase what was originally asked or make an old response appear to answer a new question.
In Coachful, distinguish assigning a resource from the client's ability to use its particular format and from any external sponsor permission. The Agreements upload area files an externally signed PDF record; it does not convert a report into a contract, validate a signature's legal effect or make an uploaded file an editable worksheet. Confirm the client identity and staff audience before filing. Unassigned agreement uploads should not be treated as visible only to the individual coach.
Session summaries also need a real audience decision. Check the effective session-type approval setting, workspace fallback and the particular recap's queued state. Do not assume that saving notes means a summary must be manually approved before delivery. Keep excluded colleague feedback out of the material being prepared for release. The practical control is appropriate content and verified access, not a blanket promise that every document labeled private can never reach anyone else.
Frequently asked questions
Should every coach replace Tresorit with a client portal?
No. A client workspace and a client-side end-to-end encrypted repository are different tools. Keep an approved secure repository when your confidentiality requirements call for it. Use a coaching space for material that appropriately belongs with the client’s day-to-day work.
Does encrypted storage make every sharing choice safe?
No. Security also depends on who is authorized, how accounts are protected, where copies go, and what information you collect. Check the complete workflow rather than relying on a single encryption label.
Can an employer sponsor see private reflections?
Only share according to the agreement and actual permissions. Sponsoring the engagement does not automatically authorize access to all reflections or coach notes. Clarify expectations with the parties before collecting or sharing information.
Can clients complete worksheets on a phone?
Choose a format that suits the task and confirm the client experience. A short form may work well on a phone; a dense report or spreadsheet may not. Do not assume every uploaded file becomes an editable mobile worksheet.
Which file formats should I use?
Use formats supported by your chosen workspace and accessible to the client. Confirm upload, preview, download, and export behavior for the material you plan to use. Prefer a simple, readable document over an elaborate format that creates unnecessary barriers.
Make the next document easy to find, easy to understand, and appropriately shared. Explore Coachful’s coaching features for organizing resources alongside the engagement, while keeping security decisions tied to your actual requirements.
