How to Manage Client Documents Without Google Drive
Nour
Founder, Coachful

To decide how to manage client documents without Google Drive, start with what each document is supposed to do. A preparation sheet, a completed reflection, a signed agreement and an employer's working presentation need different handling. Moving them into one place without preserving those differences can make the client journey harder to follow.
Coachful is our #1 recommendation for organizing documents around an ongoing coaching relationship. Its client files, deliberately shared resources, worksheets and agreement records support that workflow. This is our editorial recommendation for those jobs, not a market ranking or a promise that every collaborative document belongs in a coaching platform.
This guide explains how to choose the authoritative copy, limit the audience, test actual retrieval and close an access period honestly. The complete fictional example includes a failed first test, an employer's refusal to permit copying, a usable replacement worksheet and a client who still has an allowed downloaded copy after sharing ends.
Decide what the document represents before choosing its location
A blank template asks for information. A submitted response records what someone said under particular questions at a particular time. A reference PDF gives instructions or background. A signed agreement records an accepted version. A collaborative working original supports continuing changes by its authorized contributors. These are different records even when their filenames look similar.
For example, replacing a three-question worksheet with a new five-question version does not make an earlier response an answer to the new questions. Preserve enough context to interpret the earlier submission. If a client declined a question that did not exist in the earlier version, do not manufacture a missing answer in their history.
Likewise, a signed PDF can be a useful agreement record, but uploading an unrelated file does not establish who accepted which terms. Keep the agreement's actual signature and version evidence in its appropriate workflow. Do not use a folder name such as “Approved” as a substitute for checking the record.
Private process notes need another decision. They may contain tentative interpretations rather than agreed facts, and moving them into a client-facing resource would change their audience. A document's usefulness to the coach does not establish a reason to publish it to the client, sponsor or employer.
The practical unit is therefore a document purpose, not a file extension. Ask: who needs this, for what action, which copy should they use, and what should happen when that action ends? That question is more useful than deciding to migrate every PDF.
Choose an authoritative copy and an appropriate audience
Google Drive already supports viewer, commenter and editor roles, restricted sharing and organizational controls. Its official sharing guidance also explains that folder permissions affect their contents. A file placed inside a broadly shared folder cannot simply have less access than its parent. Review the actual location and audience rather than assuming a familiar link is private.
A live employer presentation may correctly remain in that employer's approved Drive environment. Copying it into Coachful can create an unauthorized duplicate, stale comments and two competing originals. A link can preserve the original location, but the link does not give the recipient permission at its destination. Someone still has to authorize the external access.
By contrast, a coach-owned preparation reference intended for one client can sit with that client's coaching records. A structured reflection can become a native worksheet instead of an attachment that travels through email. The useful distinction is between work that needs collaborative editing and work that needs a clear next step in the client relationship.
For UK personal-data handling, the ICO's data minimisation guidance links the information you keep to its purpose. Relevant, sufficient information is not the same as every available detail. The ICO notes that this guidance is under review following the Data (Use and Access) Act 2025. Use the principle to ask a concrete question, such as whether a client can explain their decision without copying colleagues' comments.
Possessing a report is not permission to redistribute it. Check its ownership, permitted recipients and any professional restrictions before uploading, adapting or feeding it into an AI tool. If permission is refused, a different coaching question may be possible. The refusal itself should remain effective.
Use Coachful's document routes deliberately
In Coachful, open Clients, select the client, then Documents and Files and links. In Simple navigation, use More options, then Documents. Staff-added files and links stay private to the coach team until deliberately shared. Existing items keep their current sharing state, so a migration needs an item-by-item check.
For an eligible staff-added item, use its three-dot menu and Share with [first name]. A saved link also has a sharing choice. Sharing requires a client with an account. A Shared badge is a useful staff check; the client's actual opening through My Coaching, then Documents is the more important completion test.
The native file-opening route checks the organization, the sharing state and the client's related account or profile. A file can therefore be correctly uploaded and still unavailable to the intended client. That is a permission or account problem to investigate, not evidence that the client failed to follow instructions.
Access has limits. An authorized file opening can produce a signed download URL valid for ten minutes. Unsharing stops a fresh authorized opening through the native route; it does not promise immediate recall of an already issued URL or remove a downloaded copy. A client's own uploaded file also cannot be hidden from that owner using the staff-file unshare control.
Use native forms or worksheets when the purpose is to collect a structured response. Keep agreement evidence in the agreement workflow. Use files for the reference material they actually contain. The Coachful features overview helps you select the appropriate part of the client workflow without treating everything as a generic attachment.

Make the migration an ordered client task
- Inventory before copying. Record the purpose, owner, current audience and authoritative copy of each item. Include completed responses and existing agreements, not just blank templates.
- Obtain the needed permission. Decide whether to copy, link, recreate your own prompts or leave the material in its existing system. A refused transfer needs a different plan.
- Create and test the current route. Give the client a dated instruction, share only the intended items, and check actual retrieval and submission.
- Complete any promised response. Distinguish internal review from returned feedback. Use an authorized client-facing channel and include receiving time.
- Close the stated access period. Apply the specific sharing and storage decisions, test them, and record which copies or later reviews remain outside that observed result.
Run a selective migration with a completed document register
Fictional worked example: Ari coaches Sol, an active client with a Coachful account. Bea is Ari's authorized administrator. Taylor controls Sol's employer presentation. Their pilot runs from 7 to 21 November 2074. Names, documents, permissions and results are invented for instruction.
They agree three completion conditions: Sol can retrieve the current preparation reference; Sol can submit the intended new worksheet without exposing employer material; and the end-of-pilot access change matches the promise made beforehand. They do not claim to replace the employer's collaborative workspace.
Ari and Bea inventory six items. The register records actual choices rather than labels such as “move later.”
| Item and purpose | Completed choice | Authority and audience |
|---|---|---|
| Preparation route, 7 November: new reference PDF | Create and share as one client file for this pilot; end sharing on 21 November | Ari owns the instructions; Sol may download and retain them for personal reference |
| Prepare one bounded request, V2: new response worksheet | Create manually as a native worksheet and assign to Sol | New prompts and response remain identifiable as V2 |
| Record three wins, V1: obsolete blank PDF | Remove its current preparation instruction and sharing; delete this staff-added blank file on 21 November | Do not claim this erases copies Sol already holds |
| Sol's completed V1 response from 1 November | Retain with its original questions and date | Historical response, not a submission to V2 |
| Existing signed coaching agreement | Leave the actual agreement record in Agreements | No new signature, amendment or replacement inferred from this migration |
| Employer working presentation | Keep the approved original in the employer's Drive environment; do not upload it | Taylor retains the employer's permission decision |
Sol asks Taylor whether the presentation can be copied into the coaching record. Taylor's actual fictional answer is: “No. Please keep the slides, figures and colleague comments in the employer workspace. You may describe your own purpose and availability without those extracts.” Sol reads the answer and passes that boundary to Ari. Ari accepts it and changes the planned preparation accordingly.
This is a usable refusal. The eventual worksheet concerns a request Sol wants to make to a community workshop coordinator. It does not need the presentation. Ari does not reinterpret Taylor's limited permission as permission to upload a redacted slide deck or its speaker notes.
Before issuing anything, Ari confirms the register and access terms with Sol. Only the new reference PDF loses sharing on 21 November. The existing agreement and submitted worksheets are outside that access change. Ari will review whether the retained coach copy of the reference is still needed on 30 November; that later review has not happened by the case's close.
Create a reference the client can actually use
Ari writes a short PDF with a dated title and ordinary headings. Its complete fictional instruction text is:
Preparation route, 7 November 2074
For this pilot, read this reference in My Coaching, Documents. Complete Prepare one bounded request, V2 through your assigned Forms & worksheets. The older Record three wins blank PDF is no longer the preparation task.
Use your own purpose, proposed request and availability. Do not include employer slides, figures, named colleague comments or extracts from the working presentation.
For access help, email Bea at docs@example.org. During this pilot, Bea replies by 17:00 Europe/Amsterdam on the next Monday-to-Friday working day. There are no excluded holidays in this fictional pilot. Send pilot access questions by 12:00 on 20 November.
Sharing of this reference ends on 21 November. You may retain a downloaded copy for personal reference. That change does not remove your existing agreement or submitted worksheets.
The reserved example.org address is an illustrative administrative route, not a real support address. Sol already received it in the pilot orientation, so a missing PDF does not also hide the route for reporting the problem.
Ari checks the exported text and reading order. W3C's PDF reading-order technique explains how tagged document structure affects reading and keyboard navigation; complex conversions can introduce a different sequence. Test the actual export rather than trusting its visual appearance. This one check does not establish complete accessibility conformance.
Ari keeps the reference short because its job is navigation and permission boundaries. It does not contain the signed agreement, a duplicate employer presentation or a second copy of Sol's completed responses. Those additions would make the reference harder to keep current.
Let the first access test fail, then verify the repair
Bea uploads the PDF and prepares the worksheet assignment. During the agreed 8 November access test, Sol signs in but cannot find the new reference. Sol sends the access problem to Bea using the previously supplied administrative address. Bea reads and answers within their test work. Sol's account works; Bea has left the staff-added PDF private.
Bea does not send an unrestricted Drive link as a workaround. She opens the correct client's item menu, selects Share with Sol and checks the Shared badge. Sol then opens My Coaching, Documents, finds the dated reference, downloads it and reads the three route distinctions: reference here, response through the assigned worksheet, employer original elsewhere.
They allocate separate active time to the initial test and the repair/retest. Bea records what failed and what Sol actually opened. A successful staff preview would not have proved the client route, and a Shared badge alone would not have caught a client signing into the wrong account.
Sol also confirms that the old blank PDF is no longer the current preparation instruction. The completed 1 November response remains associated with its original task. Nobody silently replaces its questions with V2. These checks establish both current usefulness and historical accuracy.
If the reference had instead linked to Taylor's presentation, native sharing would not have solved the destination permission. That contrasting case would require Taylor's separate approval or a different resource. The platform's successful redirect would not establish that the recipient can lawfully or practically open the employer file.
Replace the blank form with a complete response workflow
Ari manually creates three original prompts in Prepare one bounded request, V2. There is no AI upload or automated conversion in this case. The completed fictional response on 9 November reads:
| Original prompt | Sol's actual fictional response |
|---|---|
| What do you want this request to help you explore? | I want to find out whether a community workshop has space for one guest reading session. I am exploring the possibility, not announcing an agreed event. |
| What is the bounded next request, and what remains unknown? | I will ask the coordinator whether a public programme slot exists before offering a date. I do not know the available dates, audience requirements or whether my proposal will be accepted. |
| What information will you leave out? | I will use my own purpose and availability. I will not include employer figures, named colleague feedback, slides or extracts from the working presentation. |
Ari reads the submission and compares its context with V1. The earlier three-wins exercise served a different purpose; its response is not evidence that Sol already completed this request preparation.
On 12 November, Ari returns an actual individual comment through Sol's private client conversation: “Your V2 response separates an inquiry from an agreed event. If you choose to contact the coordinator, keep the first question about whether a slot exists. The employer material stays outside that message. We have not established an event date or acceptance.” Sol reads that comment.
Ari's internal worksheet Coach review is separate. Authorized coach-team review does not itself deliver feedback to the client. The explicit conversation return and Sol's reading time complete the promised feedback loop here. Sol has not yet sent the proposed coordinator inquiry by the case's end, and no workshop outcome is inferred.
A native worksheet therefore replaces a particular response task, not the client's whole file collection. See the coaching questionnaire guide for choosing useful prompts, and the client onboarding checklist for introducing the route before expecting its use.

Close access without pretending to recall every copy
On 21 November, Bea unshares the new reference PDF as promised and deletes the obsolete staff-added blank V1 file. She records those two different actions. Sol checks the client Documents route: the new reference is no longer available for a fresh native opening. The downloaded reference still opens locally, which is permitted by the original personal-reference term.
They do not test or claim instant invalidation of every previously issued signed download URL. They also do not say that deleting a staff file remotely deletes Sol's older downloads. Access control, storage deletion and control over copies already delivered are different jobs.
Ari's final notice says: “The pilot reference is now unshared, and Bea has deleted the obsolete blank V1 staff file. Your downloaded pilot reference may remain for personal reference. Your submitted worksheets and existing agreement were not removed by this change. The employer presentation was not copied into Coachful. I will review the retained coach reference copy's continuing purpose on 30 November.”
Sol reads that notice as part of the closing test. No additional acknowledgment is invented. The later retention review remains future work, not an observed deletion. The ICO's storage limitation guidance explains that UK GDPR does not set one fixed period for every kind of personal data. Determine and document a justified period and review it. The ICO marks this guidance as under review; these fictional dates are operational choices, not universal legal deadlines.
Count the effort and preserve the remaining uncertainty
The whole pilot coordination account includes creating, sending, reading, replying, testing, feedback and closure. These are active person-minutes, not uninterrupted editing blocks or elapsed waiting time.
| Person | Actual included work | Actual / allowance |
|---|---|---|
| Ari | 20 inventory; 10 permission and instructions; 25 reference/worksheet creation; 10 issuing instructions and reading access reports; 15 response/context review; 6 returned feedback; 10 closing purpose review and notice | 96 / 105 minutes |
| Bea | 10 inventory; 15 upload, assignment and obsolete-instruction removal; 10 initial test; 10 sharing repair/retest; 10 closure | 55 / 60 minutes |
| Sol | 10 permission question/answer handling; 10 instructions; 10 initial test; 10 retest; 15 worksheet; 4 feedback reading; 10 closure test/notice reading | 69 / 75 minutes |
| Taylor | 8 reading the permission question and returning the refusal/limited alternative | 8 / 10 minutes |
The total is 228 of 250 person-minutes, leaving 22 unallocated. The first failure consumed real time despite the eventual correct sharing. This is not a measured saving against Drive, because no equivalent Drive workflow was timed.
All three completion conditions were checked: Sol retrieved the current reference after repair, submitted the intended V2 without employer extracts, and observed the stated access change. The proposed community inquiry remains unsent. The employer original remains where Taylor required. The 30 November retention decision and longer-term client usefulness are unknown.
Troubleshoot the document problem you actually have
- The client cannot see an uploaded file. Check the specific account, item sharing and actual client route. Separate a saved staff file from a shared file; do not broaden access to unrelated records.
- The client opens a link but its destination refuses access. Ask the external owner about permission. Native link visibility cannot override the destination's controls.
- Two versions both look current. Name the current instruction and date explicitly, remove obsolete preparation directions, and preserve submitted responses with their original context.
- The PDF reads in an unexpected order. Inspect the export's structure and test the relevant reading and keyboard sequence. Supply a usable alternative while repairing the file.
- An unshared document still exists on a device. Distinguish fresh platform access from an allowed or improperly retained copy. Follow the actual agreed handling and appropriate incident process if necessary; do not promise remote deletion.
Frequently asked questions
Can Coachful replace every Google Drive document?
No. It can organize coaching references, worksheets and agreement records around the client relationship. A jointly edited employer original may appropriately remain in its approved collaborative system. Decide by purpose and permission rather than demanding one storage location.
Does uploading a file share it with the client?
Staff-added client files require deliberate sharing and an eligible client account. Check the item's actual state, then test with the intended client. Existing items retain their sharing state.
Should I turn every PDF into a worksheet?
Only when collecting a response is its purpose. A reading reference can remain a file. Recreating prompts produces a new task; preserve the context of older completed responses and check your rights before adapting third-party material.
Does unsharing delete a downloaded copy?
No. It limits fresh native access, while an already issued file URL can remain valid for its short term and downloaded copies can remain. State permitted retention before delivery and do not imply remote recall.
Is internal worksheet review the same as returning feedback?
No. Record internal review appropriately, then deliver any promised client-facing response through an authorized route. Account for the recipient's reading and reply work as well as the coach's writing.







