One proposal, several editors and a clear sign-off
Agree on a document approval process before a proposal goes to the client. An agency and a client are developing a campaign. Sales emails a PDF, the editor continues working in a document and the client emails revision requests. By the end, nobody knows which headline received approval. Google Workspace offers a way to test a different process with Drive and Docs. Choose one authoritative working location and explain where comments belong. Someone reviewing a file needs different permissions from the person implementing changes.
Walk through the process from the external client’s perspective. Can the intended account comment? Can the editor tell which requests have been addressed? Can the project lead identify the version submitted for approval later? A resolved comment alone does not answer that final question. Agree how the responsible person records approval and which version is archived. Revisit shared links when the project ends. Removing one team member will not necessarily close a link that still allows broader access.
Organise storage around the work
A folder structure is most effective when it reflects people’s tasks. In a client campaign, working material, content awaiting review and approved deliverables have different requirements. Editors need quick access to sources. An external client needs an understandable place to sign off. If both face the same confusing collection, they often return to email attachments. Start with one project and see whether a newcomer can identify the current version.
Agree on names for durable documents and temporary drafts. A date helps identify an invoice, whereas a living proposal may be easier to find through a stable link. Avoid creating copies merely because another person wants to comment. Also identify the formats required at formal delivery. Google Workspace can simplify collaboration. Deciding when a version becomes binding and where it is retained remains part of your project organisation.
Prepare for a change of personnel
Imagine that the project lead changes roles at short notice. What will their successor need on the first morning? Beyond files, that usually includes the next meeting, open approvals and client contacts. Rehearse the handover in a sample project. Inspect documents using the successor’s intended account. Checking from the previous lead’s session conceals personal sharing arrangements and missing permissions.
Agree on a procedure for people joining, changing roles or leaving. Who requests access, who approves it and who checks whether it is still necessary? Allocate responsibilities so one absence cannot block work. These organisational requirements often matter more to plan selection than the number of available apps. Compare the administration features your operation needs with the current offer and resolve open questions before rollout.
How do you hand over client documents when someone leaves?
Use a fictional client folder to rehearse a project manager’s last day. Their successor must find the current offer, discuss a revision with the client and later establish what was approved. Let them do all three using only your filing system. Pay attention to links that exist only in a personal inbox and documents distinguished by names such as “final” and “really final”. Record the precise point at which the successor had to ask a question.
Repeat the exercise from the client’s perspective. Open the material expressly intended for external collaboration with an authorised test account. The client should be able to comment on their draft without seeing your cost calculation or another client’s drafts. Record the external permission, internal owner and intended end of access together. That information is more valuable to a stand-in than a long folder description that nobody maintains.
Three tests for your pilot
Comment with an external test account
Share a sample document with the intended external account. Open it in a separate session, add a comment and try a direct edit. Compare the result with the intended role. Record the exact sharing setting that allows client input while leaving the editorial team responsible for final wording.
Identify a change made after approval
Record one version as approved, then change a figure in the working copy. Ask a colleague to establish which figure the client saw. If this requires searching several inboxes, the handover is incomplete. Capture the date, version and approver, then repeat the exercise.
Rehearse a handover to a substitute
Give a substitute the project’s internal instructions. They should find the current proposal, understand the comments and identify the approval link. Watch for personal storage locations and links to private copies. Decide where durable project documents belong and who adjusts access and ownership when staffing changes.
Preparing your team to use the tool
Identify the version submitted for approval
As soon as several people contribute to one deliverable, approval needs a specific object. A comment such as “looks fine to me” leaves open which version was seen and whether it covered content, design or a single correction. Establish a simple handover rule. The reviewer sees the proposed final version, receives a precise question and knows the deadline. They can approve, request an identified change or explain which evidence is missing. Record the answer where the team organises subsequent work.
Then simulate a change after approval. A new price, a different scope or a changed recipient may require another review. Decide which changes are material and who can make that judgement. Otherwise every spelling correction can trigger a fresh approval cycle while a consequential edit passes unnoticed. For a pilot, a short version record with a date, reason and owner is sufficient. After several runs, assess which details proved useful and which fields people complete merely out of habit.
Move a proposal from a personal draft into shared storage
A fictional consulting proposal with a cost estimate, a description and a presentation is enough for the exercise. One colleague started the estimate and another revised the description. Both refer to files in their emails. Someone joining the project immediately faces a practical question. Which link points to the current working document and which version did the customer actually receive? Put those two situations side by side before deciding on folder names or access rights.
Then stage a handover to a substitute. The colleague is away for a week and the customer wants to add an item. The substitute should be able to work out where to continue without calling the absent colleague. Watch where they hesitate. Perhaps they find the document immediately but cannot tell whether the current estimate matches it. Alternatively, the link may be correct while the permission needed to revise the draft is missing.
Use the exercise to agree on the filing arrangement. Which documents belong to the project, who can change them internally and how will people recognise the version approved for the customer? These questions apply whatever the size of the team. Then check which shared storage and external sharing options are actually available in your Workspace edition. A rule becomes practical only when a substitute can follow it under ordinary working conditions.
Read a sharing invitation as an external recipient
A customer invitation is a good reason to change perspective. Use a designated external test account and a file containing no real customer information. Open the link exactly as the customer would receive it. Do you see the intended document? Can you comment if that is part of the review? Does permission to edit reach further than the project lead expected? Looking at the owner’s internal view only answers part of the question.
Next change the agreed scope and make the revised version available. Ask someone outside the project which version applies to the next meeting. If they can only guess from a filename, the status needs clearer communication. Consider downloaded copies too. Editing a shared document later will not automatically update a file already sent to the recipient’s computer.
At the end of the project repeat the exercise with a different question. Which material must remain accessible for follow-up and which external invitation can expire? Record the event that triggers the access review and identify the person who carries it out. Storage then has a lifecycle from drafting through closure. For recurring projects this avoids each new proposal being organised a little differently until only the original authors know where to find anything.
Reconstruct approval without the project lead's inbox
Ask a colleague to reconstruct the latest client approval using only the shared project folder. They should identify the approved version, find the date it was accepted and point to the working file from which the next revision should begin. If they have to request a private email, part of the decision history is missing from the project. Agree where future approvals belong and how the team distinguishes working drafts from files already sent. Repeat the exercise with someone who joined the project later. They will spot folder names that make sense only to the original authors. Finish by checking the recipient's view with an authorised test account. Can the client open the intended delivery while the internal costing sheet stays private? Write down the result alongside the approval so a substitute knows what was shared. When the project closes, name the person who will review that access and confirm whether the recipient still needs it for the next stage. Include the date of that review in the handover.
Where document editing ends and project tracking starts
A comment on a paragraph is ideal when someone needs to correct a particular sentence. An approval involving three teams and a publication deadline can easily get lost in the same place. Keep the correction in the document and agree on a visible work item for the wider decision. Test whether a stand-in can reach the correct version from that item and identify the person responsible.
Read the monday.com guide