How to Manage Client Documents Without Box: A Full Guide

Here is how to manage client documents without Box: separate files from reusable coaching resources, choose the appropriate audience for each item and verify the client’s actual route before retiring the old one. A coaching workspace can organize suitable material without becoming a replacement for every organizational repository.

This guide gives a complete fictional transition for one engagement, including an access mistake, a client upload, a sponsor request and a final reconciliation. It does not assume an automatic Box import or treat a successful upload as proof that permissions and obligations transferred with it.

Decide what you are replacing

Start with the job each document performs. A client may need to read a session plan, complete a worksheet, retain a signed agreement or refer to an employer report. Those tasks need different routes even when the files currently sit together.

If Box is the organization’s required collaboration or records system, keep that requirement visible. Moving selected coaching material closer to sessions can still be useful. It does not establish equivalent retention, collaboration, version history or organizational approval.

For a small practice, the intended change might be narrower: stop asking an account-backed client to find routine coaching files in a separate coach-owned Box folder. Define that outcome rather than assuming the whole subscription can immediately be canceled.

Use the documents and worksheets guide for the everyday workflow. This article focuses on the transition, audience checks and decision about what remains outside the coaching workspace.

Give each kind of material an appropriate home

An uploaded PDF does not automatically become an editable worksheet, a newly signed agreement or a verified sponsor report. Choose the right workflow deliberately. Recreating a blank prompt may be sensible; reconstructing a signed contract as if it were newly executed is a different matter.

Understand Coachful’s actual file-sharing boundary

Coachful is our #1 recommendation for the client-file and resource workflow described here. This is our recommendation as Coachful’s publisher, based on the specific controls below. It is not a security certification or an assertion that it replaces every Box requirement.

In Advanced, open Clients > the client > Documents. In Simple, use Clients > the client > More options > Documents. Coach-added files and links start private to authorized staff who can access that client record. Share the intended item deliberately; saving it alone does not make it client-visible.

For an existing item, use its three-dot menu and Share with the client’s first name. A Shared badge identifies that state. Stop sharing hides that coach-added item again. When adding a link, the Share with checkbox starts off; choose it deliberately if the item should be shared immediately.

There is an important exception: files uploaded by the client remain visible to that client and the coach. They cannot be made invisible to their owner through the coach’s ordinary Stop sharing action. Do not describe every document as coach-private until shared.

Sharing needs a client account. A tracked profile or lead without an account is not an account-backed document recipient. The client finds shared items in My Coaching > Documents; an external link still depends on the destination’s own permission settings.

These boundaries concern the supported workflow. They do not establish that a particular customer’s permissions, notices or access have been inspected. A shared-document notice is also different from the person opening and understanding the file.

Prepare a controlled transition

1. Inventory active items. Record title, date, owner, current location, intended audience and purpose. Include obsolete versions still reachable through old instructions.
2. Check permission to move them. Ownership, contractual restrictions and organizational policy matter separately from whether a download button works.
3. Choose the destination. Distinguish client Documents, native worksheets, agreement records and the approved archive. Do not put everything into one shared folder.
4. Preserve the source context. Keep the required original files and any evidence needed to understand them. Reconcile the inventory instead of assuming a ZIP contains every relevant record.
5. Configure the new audience. Check coach-added sharing separately from uploads made by the client. Do not infer audience from a filename such as “private.”
6. Test the real client route. Confirm the intended person can open the right item and identify the current version before withdrawing their old route.
7. Retire only what is ready. Review old links, collaborators, retained copies and other engagements before account closure or a claimed saving.

Box’s current download guidance describes downloading one file or selecting multiple items for a ZIP. Its troubleshooting guidance also notes that download permissions can differ and empty folders may not appear in a folder download. Treat a download as material to check, not proof that every access rule, version, comment or record migrated.

Keep any temporary local copies within your approved handling process. The ICO’s data-minimisation guidance emphasizes information that is adequate, relevant and necessary for a defined purpose. The page is currently under review following the Data (Use and Access) Act. Reducing unnecessary copying is a practical design choice; it is not a complete compliance assessment.

Complete fictional case: one client, several document purposes

Noor runs a coaching practice. Anika is an account-backed coaching client whose employer funds the engagement. Dion is the employer sponsor, not a member of Noor’s coaching workspace. The people, files and events below are invented for teaching; no customer account has been changed.

On 2 November 2026, Noor reviews five items in her coach-owned Box folder and one relevant item in the employer’s separate Box workspace. Her goal is to replace the routine coach-owned folder route for Anika, not to move the employer’s records or cancel every use of Box.

The engagement agreement permits Anika’s preparation and action planning with Noor. Sponsor reporting is limited to wording Anika approves for the stated purpose. Dion’s funding does not give him access to completed reflections or general client Documents.

Complete the six-item inventory

Noor checks that the two archive PDFs open and retain their original content, including the agreement’s signature page. She does not edit or re-render the signed agreement. Anika confirms on 3 November that her existing signed copy also opens. This preserves a record; it does not make a new legal conclusion about execution or validity.

The inventory does not call the old reflection a blank resource. Its date and questions matter because the answers concern an earlier session. Keeping it as a dated record avoids making an old answer appear to respond to a revised prompt.

Catch the missed sharing step

Noor uploads the current plan and old reflection on 2 November but initially assumes that filing them has made them available. On 3 November, Anika reports that she cannot find either in My Coaching > Documents.

Noor checks the two coach-added records and finds that neither has been shared. She uses each item’s menu to Share with Anika, then checks the saved Shared state. Anika opens both that day and identifies the plan as version 2 dated 2 November. The reflection is labeled as the 28 October record.

The repair matters: a successful staff upload had not established client access. Noor does not report the transition complete before Anika’s actual opening. She also does not make the files public or bypass the ordinary account route to solve the problem.

These are fictional observed checks within the example. They illustrate what to verify in a real transition; this article is not a claim that those checks have been performed on a live customer workspace.

Give the worksheet a complete route

Noor’s rebuilt preparation resource contains four original prompts:

• Which conversation do you want to prepare?
• What happened that makes it useful to discuss now?
• What do you know, and what are you assuming?
• What would you like to leave the session better prepared to do?

She uses Clients > Anika > Worksheets & resources and Assign. Copying the worksheet’s private link alone would not assign access. After assigning access, she sends the worksheet’s private client link by their agreed email route with this instruction:

Complete the conversation-preparation worksheet for our next session. Focus on the decision and your questions; please omit confidential forecasts and identifying details about colleagues. We will discuss your answers during the session. This does not include a separate written feedback round.

On 4 November Anika opens the assigned resource and submits her answers. Noor checks the actual response record. The assigned worksheet, completed answers and imported old reflection now have different purposes and dates; none is treated as a substitute for the others.

The demo form builder below illustrates original resource preparation. It is not a Box importer, an agreement-signing screen or the fictional worksheet itself.

Recognize a client upload without hiding its origin

Also on 4 November, Anika uploads her own one-page action note through her client Documents route. It contains her chosen next question for the session and no employer forecast. The record is visible to Anika and Noor as a client-uploaded file.

Noor does not try to turn that file into a coach-private note. If she needs her own professional working record, that is a separate record with its own appropriate access and purpose. A file’s category or title does not override the client-upload visibility boundary.

This new upload is not one of the six original source items. It is a seventh document event after the transition began. Distinguishing imported source items from new work keeps the reconciliation honest.

Send a usable handover message

On 5 November Noor sends Anika this completed transition message by their agreed email route:

Your current session plan is version 2, dated 2 November, in My Coaching > Documents. The reflection there is your historical 28 October response, not new preparation.

Your conversation-preparation worksheet has been assigned separately. Use the private worksheet link I emailed after assigning it. We will discuss its answers in the session; there is no separate written feedback round.

You have confirmed that your existing signed agreement opens. The employer forecast remains in your employer’s system. I have not copied it or given the sponsor access to your reflections.

Please reply to this email for any access clarification. The old coach-owned Box links will be withdrawn after this handover is confirmed.

Anika replies that day confirming the routes and asking Noor to proceed. Noor then withdraws the old links as described below. This acknowledgment confirms the handover instruction; it is not evidence that Anika understood every document or completed a future coaching action.

Handle the sponsor’s request separately

On 6 November Dion asks Noor to forward Anika’s completed reflection as evidence of progress. Noor returns to the reporting agreement rather than treating the request as document permission.

Anika does not approve forwarding the reflection. She instead approves this exact short update to Dion for the engagement review:

We agreed to prepare one prioritization conversation. This update does not assess Anika’s work performance.

Noor sends that approved wording through the agreed sponsor email route on 6 November. Dion acknowledges receipt on 9 November. No client Documents grant or reflection attachment is included. Receipt of the update does not establish that the conversation occurred or that Anika’s performance changed.

The ICF Code of Ethics supports clear roles, agreements and responsible information handling. Here the practical output is a specific approved message, not a broad assumption that sponsorship authorizes the underlying files.

Close the bounded transition and preserve what remains

After the new routes work, Noor disables the old shared-link routes for the five items she owns in her Box folder and replaces the old preparation instructions. In this example Anika had used those links, with no separate collaboration invitation to that folder. Noor checks that those old links no longer provide access. She does not alter the employer’s workspace or Anika’s rights there.

On 12 November Noor reconciles the six original items: two PDFs preserved in the approved archive; two coach-added files shared in client Documents; one blank worksheet rebuilt and assigned; and one employer-owned report left in its required location. That accounts for all six without calling them six imports.

Anika’s subsequent upload remains a separate client-owned record visible through the client route. The current plan is version 2, and the old reflection retains its original date. The old version 1 remains an archive record, not an active instruction.

Noor’s Box account stays open because another engagement has not been reviewed. This case establishes a working replacement route for the selected coach-owned materials, not a complete practice-wide migration or a subscription saving. Any later account closure remains a separate decision after the outstanding engagement and retention needs are checked.

Keep version decisions understandable

Use a naming convention that conveys identity, purpose, date and status without unnecessary personal detail. A real practice might use an engagement code and “session plan v2, 2 November.” Avoid names like “final-final-new” or putting a sensitive description into a title visible in notices.

When content changes, decide whether it is a replacement instruction or a separate historical record. Tell the client which version applies. Do not silently overwrite an earlier response’s questions and then assume the old answers still make sense.

For signed agreements, preserve the signed record and use the appropriate agreement workflow for genuinely new terms. The Agreements image below illustrates a distinct agreement-record area. Ordinary client-file sharing does not create a new signature or reproduce an external signing certificate.

For more on the professional agreement itself, see the coaching contract template guide. Document organization and agreement validity require different checks.

Plan retention and offboarding before promising deletion

The ICO’s storage-limitation guidance says retention depends on a justified purpose, not one universal time limit. It recommends review and appropriate deletion or anonymisation when information is no longer needed. This guidance is also currently under review following legislative changes.

Set a practical review date and responsible person for each record category. Agreements, active preparation and unnecessary temporary copies may have different purposes. Do not apply an arbitrary “delete everything after thirty days” rule without checking the relevant obligations and actual need.

Distinguish removing a portal route from destroying all copies. Stop sharing a coach-added file hides that item from the client’s portal; it does not recall downloads, attachments or material already retained elsewhere. An external link remains subject to its own source permissions.

Before closing an account or engagement, check what the person needs to retain, which copies the practice still needs and which temporary copies can be removed under policy. Preserve any legitimate unresolved requirement. A migration is not completed by deleting the old source before the new record and audience have been verified.

Troubleshoot the actual failure

The client cannot see a coach-added file

Check the intended account, client record and saved sharing state. Do not assume a successful upload or staff preview proves client access. Confirm the correct item is shared and then check the client’s actual route.

The external link opens an access error

Check the destination’s own permission and account requirements. Sharing a link in Coachful does not grant access to a restricted employer repository. Ask the responsible owner rather than making the source public.

The file downloads but is unsuitable for completing the task

A viewable PDF may not support the intended editing or response workflow. Use a suitable native worksheet for original questions, or explain the supported file task clearly. Preserve earlier responses rather than making the client repeat them unnecessarily.

A wrong or sensitive file is uploaded

Pause use of it. Establish what it contains, who could access it and what action is appropriate under the practice’s process. Client-uploaded visibility cannot be solved by pretending it is an unshared coach file. Obtain appropriate advice where incident or legal obligations are unclear.

Frequently asked questions

Does this mean Box is unsuitable for coaching?

No. The appropriate choice depends on the work and required controls. A coaching workspace can improve a routine client route while an employer’s required repository remains in use.

Can I import a Box folder and preserve all permissions?

This guide describes a deliberate manual transition, not an automatic permission-preserving import. Reconcile the files, context and intended audiences individually before retiring old access.

Are all client Documents private until shared?

Coach-added files and links begin private to authorized staff with access to that client. Client-uploaded files remain visible to their owner and the coach. Existing saved sharing states must also be checked.

Does a sponsor automatically receive client files?

No. Funding, an email request and client-file access are different things. Follow the actual agreement and specific approved disclosure, as the fictional case demonstrates.

When can I cancel the old subscription?

After reviewing all relevant engagements, retained records, access routes and other dependencies. Completing one client’s transition does not establish that the whole account is ready to close.

Explore Coachful’s features for the client-file, worksheet and coaching workflow. Keep purpose, version and audience explicit when deciding what belongs there.