File sharing with clients: attachments or shared links?

File sharing with clients starts with the required action: reading, commenting or editing. With an existing working account, prepared harmless file and available agreed test recipient or second account you control, fifteen minutes can produce a route, recipient check and saved record. Otherwise prepare the route and question but retain “pending”; new accounts, administrator permission and replies are not guaranteed within that time.

Last updated: 2026-10-17

In his published reflection “Perfect or Effect”, Anar Rüstəmli describes how pursuing perfection delayed his projects. Applied to this workflow, that principle suggests testing whether the recipient can use one small practice file before polishing the delivery message. This is an application of his documented working principle, not a claim that he ran this file-sharing exercise with a client.

Should you send an attachment or a shared file link?

An attachment is a separate file carried with your message. A shared link points to an item held in a file service. Those are different delivery arrangements. A sent message is not proof that the recipient opened the item, and a working link in your own browser does not prove that someone else can use it.

Consider a fictional independent designer sending a brochure to a client. The client might need a printable copy, or they might need to leave feedback next to the wording. The first task can suit a PDF attachment. The second may be easier in a shared document. This scenario illustrates a decision, not a reported client result or a tested account configuration.

For the wider operating process, see how to write a standard operating procedure. The narrower outcome here is an observable delivery check: the intended person can reach the intended item and perform the intended action. Whether that content is correct or approved remains a separate question.

Choose the delivery method before drafting the email

Write the recipient task as a verb. “Review the brochure” is still ambiguous. “Add comments without changing the wording” gives you a testable requirement. You can now decide what capability is needed and what capability would be unnecessary. Do not begin by granting editing access simply because it is easy to select.

Google Drive distinguishes viewing, commenting, and editing roles. External sharing can be restricted for work or school accounts. Treat the matrix as a business decision aid, then inspect the controls actually available in your account. It is not a promise that every organization permits the same arrangement.

If you send both a PDF and a link, identify which item the recipient should act on. Otherwise feedback may arrive against two different copies. The separate document version approval check addresses whether an approval reference belongs to the exact content. Passing an access check does not answer that question, and the delivery record should not imply that it does.

Prepare a small recipient test without private material

Use a dummy file with harmless text. A two-paragraph sample brochure is enough. Do not move a customer list or a confidential proposal into a second account merely to learn the workflow. Keep the practice item separate from the live deliverable, and label it clearly so nobody mistakes it for client work.

Confirm the account the recipient intends to use. The address receiving an email may not be the account currently selected in their browser. A person can read work mail on a phone while the document service is signed into a personal account. Asking which account is selected is useful; asking for their password is not.

• Item: the practice file name and where it is stored.
• Owner: the person responsible for its sharing arrangement.
• Recipient: the exact account used for this test.
• Required action: read, comment, or edit.
• Unnecessary capability: what this recipient should not need.
• Evidence: what observation will count as a successful test.
• Follow-up owner: who will investigate a failure.

If nobody owns the decision, settle that first. The guide to building a small business team provides a broader role framework. For this exercise, you only need one named person who can resolve the delivery decision and one person who will report the recipient result.

Run the five-step recipient acceptance check

Step one: inspect the selected item. Read its name and opening text rather than trusting a familiar icon. Expected result: you can identify the practice material you intend to deliver. A similarly named file in a recent-items list is not sufficient evidence. Stop if you cannot tell which item is selected.

Step two: for a prepared harmless Google document, open drive.google.com → the file → Share. Enter the agreed test recipient’s exact address, select Commenter, then Send/Share. Do not make the general link public. If that role or access is unavailable, retain “blocked/pending”. For an attachment, add and inspect the dummy file in a test email, then select Send to the agreed test address. Expected result: the intended object has been sent, not yet proven usable.

Step three: the agreed recipient opens the received link using the recorded account, or opens the attachment actually received. You can use a second account you control; do not sign into a customer’s account. Expected result: a recipient-side observation. Without an available tester, record “pending”. The sender’s email draft is not recipient evidence.

Step four: test the required action. If comments are needed, add a harmless practice comment. If reading alone is needed, check that the arrangement matches that requirement instead of requesting unnecessary editing rights. Expected result: the intended task works. If the available capability is broader than planned, refer the difference to the sharing owner before live delivery.

Step five: search Start for Notepad, open it and create a new blank document. Enter the date, route, test account, required action and actual observation or “pending”. Press Ctrl+S, choose Documents, name it file-access-test-V1.txt and select Save. Close it; in File Explorer/Documents double-click that file. Verify that pending has not become passed and the account and required action remain. Remove practice comments afterwards. This is not a recovery test; see the small business backup guide separately.

Copy a delivery message that explains the next action

A good delivery message tells the recipient what the item is, what to do with it, and where to report a problem. It does not need to describe the entire project. Complete every bracketed field before using this template, and adapt it to the communication arrangement already agreed with your client.

Subject: [project] file for [required action]

Hello. Please use the [attachment / link] to [read the deliverable / add comments]. Intended account for the link: [address]. The item to act on is [file name and location]. Please confirm that it opens by [agreed time]. If it does not, send the error wording and tell us which account is selected. Do not send a password. The person handling delivery issues is [name and contact].

Save a separate internal note: “Practice brochure; named-recipient link; commenting required; opened with the recorded test account; practice comment added; no unnecessary capability observed; owner to review temporary sharing.” This is an example record format, not a claim that this particular platform exercise was performed.

Write down limits as carefully as successes. If the recipient tested only a phone browser, record that fact. Do not write “works everywhere.” If the recipient says only “received,” ask whether they opened the item and completed the requested action. Receipt, opening, and useful access are three distinct observations.

What should you do when the recipient cannot open it?

Classify the failure before changing the audience. Is the browser using the wrong account? Is the intended person missing from the access arrangement? Does the organization block external sharing? Does the message point to the wrong item? Ask for the error wording, and avoid circulating screenshots that reveal unrelated private information.

Making a link available to anyone is a different audience decision, not a neutral troubleshooting step. Ask the sharing owner to resolve that choice. Google documents that access inherited from a parent folder may require attention at the folder level. Inspect where the access comes from rather than assuming one change on one file has settled the wider arrangement.

For an attachment failure, ask which received file the person tried to open and which application they used. The problem may involve the format or the uploaded item rather than permissions. Personal Gmail accounts have a 25 MB total attachment limit; work account limits can be set by administrators. If a large attachment becomes a Drive link, perform the link-access check instead of treating it as an ordinary attached copy.

If your actual task is collecting documents from many people, file upload in Google Forms addresses a different intake workflow. End this exercise with three concrete outputs: a chosen delivery route, a recipient-side observation, and a list of unresolved access questions. Those outputs are useful even when the live file must wait for an authorized sharing decision.