No Dashboards
A client dashboard is often more interface than a freelancer or client needs. A clear owner project list and one readable page per client can cover the weekly update job. The goal is quick access to the next useful fact, not the removal of every overview.
Why a client dashboard is often unnecessary
A dashboard combines measures, charts, alerts, and controls so someone can monitor a system. It works when the reader has many changing signals to compare and knows what action each signal should cause. Without that need, a dashboard adds interpretation before action.
Freelancers often manage a smaller set of active projects. Imagine that you have three to eight projects at one time. That range is an illustration, not a claim about all freelancers. You may be able to scan a plain list faster than a set of charts about workload or status.
A client usually has an even narrower need. They want the state of their project, not a view across your business. Showing them a portfolio dashboard can expose irrelevant details and make their own update harder to find.
Keep the owner view clear
No dashboards does not mean no project overview. The owner needs to find each project, see whether an update was sent, and open its history. A list is an overview with fewer layers.
Use project names that match the words you and the client use. Put the most useful delivery information near the project, and make the full history easy to open. The owner should be able to answer, "Which update did I send, and when?" without reading a chart.
Friday has an owner project list, delivery lines, and private project history. It does not claim to replace project management reporting. The list supports the sending job, while the history supports checking what was recorded.
Hypothetical example: Six active projects. You open the owner app on Friday and see six project names with their delivery lines. You open each project that needs attention and send its update. A chart showing that 67 percent are current would only restate what the list already lets you act on.
Give the client one project page
A client page should answer direct questions in plain language. What finished? What happens next? What do you need from the client? Did a date, cost, or decision change? A dated set of updates can answer those questions without status gauges.
Percent complete is especially hard to use for creative and knowledge work. A project can stay at 80 percent while the final review takes longer than expected. A sentence about the remaining review and its date gives the client more information than a progress ring.
Traffic light labels also need explanation. "Amber" may mean a delay is possible, a decision is late, or a cost is under review. State the condition and the next action instead. The client should not have to learn your color rules.
A private page still needs an access rule. In Friday, the client link is unindexed, but anyone holding it can read and reply. Tell your client to share it only with people who may see the project history.
Use a dashboard when comparison leads to action
Dashboards become useful when you manage enough work that a list no longer shows risk in time. You may need to compare budget use, deadlines, staffing, or support volume across many projects. A well-designed dashboard can then direct attention to a specific problem.
The test is whether each measure changes a decision. If a chart looks useful but never causes you to act, remove it. If an alert tells you which client has missed an approval deadline and what will slip, it may earn its place.
Your main project software may already provide those management views. Keep using them if they help you plan. A client update product does not need to copy every internal dashboard when its purpose is to deliver a short message.
Do not make clients monitor your work
A live dashboard can shift the burden of communication to the client. You may expect them to check it, while they expect you to tell them about a change. Both sides can then claim the information was available without agreeing that it was understood.
Send important changes directly. A page can keep the history, but the new update should still reach the chosen client email. Each project in Friday uses one client email for that delivery, so choose the person responsible for receiving or passing on the note.
The client does not need an account. There are no client seats or client tiers to manage. The private link makes reading easier, but forwarding gives another holder access, as explained in why clients shouldn't need an account.
Prefer a list and a clear page
Skip a client dashboard when a project list and dated update page make the next action clear. Keep dashboards in the systems where measures and comparison help you manage complex work. Do not ask a client to decode a management screen to learn what changed this week.
Friday uses a project list for the owner and a private project page for the client. The small structure fits freelancers who want to send updates and keep a record, without adding charts that do not improve the conversation.