How to Set Up a Client Portal (And Why Retainer Clients Need One)
A client portal is a single link where a client sees their deliverables, documents, requests and approvals in one place, without needing an account or password. Set one up per client, put real work in it before sharing the link, and keep a monthly activity log so retainer clients can always see what they are paying for.
Most status-update requests are not really requests for information. They are requests for reassurance. A portal answers them without you having to.
What a client portal replaces
Without one, everything you have delivered lives scattered across email threads, file transfer links that have expired, and a text message where someone said "looks good" three weeks ago.
That costs you twice: your client cannot find things, and you have no clean record of what was approved and when.
| Without a portal | With a portal |
|---|---|
| "Can you resend that file?" | It is in their portal, permanently. |
| "Where are we up to?" | They can look. |
| Approval buried in a text message | Approval recorded, with a name against it. |
| Monthly value is invisible | Activity log shows the month's work. |
Set one up per client
Create the portal against the client, and you get a link. That link is the access — there is no account to create and no password to reset, which removes the single biggest reason clients never log in to things.
The first time a client approves something they are asked for their name, which is then recorded against the approval. So you get accountability without imposing a login.
Put something in the portal before you send the link. An empty portal is worse than no portal — it makes you look less organised, not more.
What to put in it
- Deliverables — the actual work, with a status you update as it moves.
- Documents — files they will want again later.
- Pages and boards — anything they need to read or follow.
- Brand guide — their brand details, so nobody is guessing at a hex code.
Then check it from their side. Open the portal link in a signed-out browser window and look at what they will actually see.
Requests and approvals
Requests give clients a proper channel for asking for things, so it does not arrive as a text message at 9pm that you later cannot find.
Approvals are the more valuable half. When a client approves work in the portal, it is recorded — what was approved, and who approved it. That is a materially different position to be in than "they said it was fine".
Both show a count so you can see at a glance what is waiting on you and what is waiting on them.
The monthly activity log (for retainer clients)
This is the part that saves retainers.
Retainer clients cannot see your work. In a quiet month they start wondering what they are paying for — not because you did nothing, but because nothing was visible. That wondering is how retainers get cancelled.
An activity log fixes it cheaply. Add a line whenever you finish something, tagged as a Deliverable, a Milestone or an Update. It takes seconds. At month end, generate a report that pulls those entries together with your hours worked, tasks completed and deliverables for the month.
Two minutes a week here means the monthly report is already written the moment a client asks what they are paying for.
One thing worth being clear about: the activity log produces a client report, not an invoice. If you want your tracked time to appear as invoice line items, that is a separate feature — see the guide on itemising invoices.
Frequently asked questions
Do clients actually use portals?
They use them when there is something worth opening. A portal with current deliverables and a monthly report gets visited. An empty one does not, which is why you should add content before sharing the link.
Do clients need an account?
No. The link is the access — no account, no password. They are asked for their name the first time they approve something, so approvals are still attributable.
Should every client get a portal?
Every ongoing client, yes. For a one-off project it is often more effort than it saves — though it still gives you a clean record of what was approved.
What goes in an activity log entry?
One line describing what you did, tagged by type. "Delivered March content calendar" as a Deliverable. "Reached 10k followers" as a Milestone. "Rebuilt reporting dashboard" as an Update. Short is fine — the value is in the record existing.