A client portal for creative studios: sharing progress without the emails
Clients ask where things stand far more often than they give feedback. A client portal is the answer most studios reach for, and most of them end up showing either too much or too little. This is what to share, what not to, and how to keep it current without extra work.
By OIO · Updated · 6 min read
On this page
The short answer
A client portal for a creative studio needs to answer four questions without anyone writing an email: what are we making, where is each piece, what are you waiting on from me, and when is the next date. Show the deliverables with their status, the deadline, a short dated update from you, and the money only if you choose to. Keep your hours, internal notes, freelancer names and costs out of it. And make it something you update as part of the work, not a second job on Friday afternoon.
Why clients keep asking where things are
A client who has paid a deposit for a product film has a boss who asks them every few days how it is going. If they have nothing to show, they email you. Each email takes you ten minutes, breaks an hour of focus, and often triggers a call. Multiply that by six active projects and it is a real part of the week.
The fix is not more meetings. It is a page the client can open whenever they like that tells them the truth, so the question gets answered before it is asked.
What clients actually want to see
From the client's side, the list is short:
- The deliverables, by the name they know them by ("Kitchen, eye level, dusk", not "KIT_v2_fix").
- The status of each one, in plain words: not started, in progress, with you for feedback, done.
- The deadline, and the next date that matters to them, such as "notes on the drafts due Thursday".
- What you need from them. This is the line that speeds up the job.
- A short update in your words, with a date.
- Sometimes the money: the budget, what has been invoiced, what is due next.
That is enough for most clients. Anything more becomes something they read closely and ask about.
What to keep internal
| Share | Keep internal |
|---|---|
| Deliverable names and status | Hours per task |
| Deadline and next client date | Internal notes and to-dos |
| Your dated updates | Freelancer names, rates and costs |
| What you need from them | Margins and the studio's hourly cost |
| Budget and invoiced amounts, if you choose | Other clients' projects |
| Final files, on a download link | Work in progress you have not checked |
Hours are the big one. A client who sees that the lobby took 22 hours will ask why, and will use it to negotiate the next quote. Show progress in deliverables and stages, not in time.
Unchecked work in progress is the other one. A portal that shows every render as it lands invites notes on things you already know are wrong. Send drafts when you are ready for notes, and show status the rest of the time.
Portal, status link or weekly email?
There are three common ways to share progress, and they suit different studios.
A client login
Some tools give each client an account and a login. It works when clients are involved every day, such as a long retainer with a marketing team. For most creative jobs it is too much: clients forget the password, ignore the invitation, or never set the account up, and you end up emailing the update anyway.
A status link
A private link to a page showing the project's status, ideally behind a password you give the client. No account to create, works on a phone, can be forwarded to the client's boss. For project-based studio work this is usually the right weight. The risk is that it goes stale, so it has to update from the work itself, not from a separate document.
A weekly email
Three lines per project, every Monday. Cheap, personal and effective, and a good habit even with a portal. Its weakness is that it is out of date by Tuesday afternoon, and it lives in an inbox the client has to search.
Most studios end up with a status link plus a short email at each milestone with the link in it.
How to keep it current without extra work
A portal that someone has to update by hand on Friday is a portal that is three weeks out of date by the second month. The status the client sees should be the same status your team uses to run the job. When an artist moves the lobby view to "with client for feedback", the client should see it without anyone copying it anywhere.
Practical rules:
- Name deliverables for the client from the start. The name on your board is the name on their page.
- Use a small set of statuses and agree what each one means, so "in progress" is not hiding a week of waiting.
- Write one update when something changes, not on a schedule. "Drafts of all four views sent, notes due Thursday" is a full update.
- Put the next date in every update.
- Check the client view once a week. Two minutes, and you will catch the stale line before they do.
A worked example
Fenwick Studio, five people, runs a product launch for a kitchenware brand: eight packshots, three lifestyle scenes and a 20 second film. The marketing manager, her boss and the agency all want to know where things are.
Before: each of the three asked separately, about twice a week. That was six emails or calls a week, and the answers were not always the same.
After: one password-protected status page, forwarded by the marketing manager to the other two. It lists the twelve deliverables with their status, the launch date, and an update line when something changes: "Packshots 1 to 8 done. Lifestyle scenes with you for notes, due Wednesday. Film animatic next week." The emails dropped to roughly one a week, usually with notes rather than questions.
Money on the portal
Showing the budget and invoices is optional, and it depends on the client. A client with a purchase order system likes seeing the budget against what has been invoiced, and it makes the final invoice less of a surprise. A client who negotiates every line may treat it as an invitation. If you show money, show totals: budget, invoiced, paid, next amount due. Not rates or hours.
One useful step is letting the client confirm that an amount is ready to invoice before you send it. Their finance team gets the invoice they expected, and you skip the round of "can you reissue this with the PO number".
If an invoice is late anyway, the payment reminder email gives you the wording, and unpaid invoice follow-up the schedule.
Setting it up at kickoff
Send the portal link in the kickoff email, with one sentence on what it shows and how often it changes. The project kickoff email guide has a template, and the client onboarding checklist covers what to collect before the first update.
Doing this in OIO
In OIO the client gets a password-protected status link for their project, with no account to create. It shows the project, each ticket's name and status, progress, the deadline and the short updates you post. Ticket notes, to-dos, files and hours never show on it. If you switch it on, it also shows the budget, and the client can confirm that an amount is OK to invoice. Because the link reads the same tickets your team works on, it is current whenever the board is.
Final files go out on download links that expire after 1, 7 or 30 days. Quotes and contracts can be sent for e-signature, and the invoice comes from the same project. You can also invite a client to view the project; viewers do not use a seat. The project's chat is for your team, and clients are not in it.
Questions
What should a client portal for a creative agency show?
The deliverables and their status, the deadline, the next date that matters to the client, what you need from them and a short dated update. Money only if you choose, as totals. Keep hours, internal notes and freelancer costs out of it.
Do clients need a login to follow a project?
For most project work, no. A private status link behind a password is enough, works on a phone and can be forwarded inside the client's company. Logins suit clients who work in the tool every day.
Should clients see work in progress?
Show status all the time, and send drafts when you are ready for notes. A portal that shows every render as it lands invites notes on work you already know is unfinished.