How to run a client resource hub without the email pile-up

Freelance work produces a trail of URLs: the kickoff doc, three competitor sites, a Notion page the client swears is “the latest,” a Figma file, a stock folder, and a final ZIP that lives in email because Drive permissions broke. Six weeks later someone asks for “the blue logo” and you are scrolling. The hub is not a pretty portal. It is a single directory with a name the client would recognize and notes that survive you being on a train.

One directory, named after the job

Call it “Harbor Coffee — website redesign,” not “New project.” Put in the description what belongs there and what does not. Example: “Brief, brand files, inspiration we actually discussed, and the final handoff. Contracts and invoices stay in email. If a link is only for me, it is not in this folder.” That last sentence saves you from publishing a private recording by accident.

If the engagement is large, split by phase: discovery, design references, feedback, final assets. People scan phase names. They do not scan a hundred undifferentiated bookmarks. Split when you cannot describe the folder in one sentence. Not before.

Notes are how you stop repeating yourself

Every link gets a line of context. Not an essay. The line you would say on a call:

• “Hero layout only — ignore the product shots.”
• “Final SVG and PNG. The JPG in Slack is old.”
• “We chose option B on 12 Mar. Do not reopen A unless they pay for a round.”

That third one is a decision note. It prevents the “can we see the other version again?” loop. If you use a poll in the same directory, summarize the outcome on the winning link the same day. Votes without a written result are theater.

What the client can see

Invite them as a viewer if they only need to look. Editor makes sense if they are dropping assets. Public sharing is for inspiration and public docs, not for the contract, the recorded call, or the staging site with real customer data. Password protection (Pro) is a middle ground: a URL you can send without indexing the whole web.

Be explicit in the description: “You can view this. Please do not add random inspiration without a note — it is how we lose the thread.” Most clients will follow a rule that is written down. They will not follow a rule you mentioned once on Zoom.

Handoff is a directory, not a farewell email

At the end, make a short “Approved / final” section or directory: live URLs, asset exports, login instructions if they own the accounts, and a paragraph of what is out of scope. Future-you (or the next freelancer) should be able to take over without a forensic investigation of your inbox.

Put a calendar reminder for two weeks after launch: “Check the hub still matches production.” Sites drift. The hub should drift with them or it becomes fiction.

Sharing mechanics are covered in the collaboration guide. For the note format, see decision notes.