One Page Per Client
One page per client gives you a stable place for the latest update and the history behind it.
The useful version has a stable URL and no client login, but you must treat the private link as access, not as magic security.
How one page per client works
A stable URL lets the client bookmark one location. Each new update appears on the same page, so you do not create a fresh document or portal address every week.
The page should show the current update first and older updates in chronological order. Dates make the sequence clear. A reader can check today's status and then look back for when a deadline or decision changed.
Do not rewrite old entries to match the current plan. Project history is useful because it records what was reported at the time. Add a correction or later update when facts change.
Send the update as well
A page does not help if the client has to remember to visit it. Send each update to the client by email and include the stable link.
The email gives the client the current information where they already work. The page gives them the ordered history when they need context. The two formats solve different parts of the problem.
Keep the email readable without opening the page. A link that says "update posted" moves the work back to the client. Send the actual summary, then offer the history.
Remove the account requirement carefully
A no login client portal lowers friction. The client does not need to create an account, remember a password, or recover access months later.
No login does not mean no access control. With a private bearer link, anyone who holds the link can open the page. The link itself acts as the credential.
Do not describe such a page as public if it is not listed or indexed by search engines. Do not describe it as risk free either. A recipient can forward the link, paste it into the wrong conversation, or leave it in an account that another person later controls.
Treat the link as sensitive
Send the private link only to intended readers. Avoid placing highly sensitive credentials, personal data, legal advice, or confidential source material on the update page.
If a link may have been shared incorrectly, you need a way to replace or revoke it. When a project requires strict identity checks, regulated records, or detailed permissions, use a system with authentication and suitable controls instead.
Convenience and security are not absolute choices. Match the access method to the sensitivity of the update. A normal project summary and a medical record should not use the same standard.
Separate clients and projects
"One page per client" is a useful shorthand, but the practical unit is often one page per project. A client with two active projects may need separate histories, dates, and recipients.
In Friday, each project has one client email. One account can own several projects, so you can keep different work streams separate under the same account. Anyone holding a project's private link can read the updates and reply.
The reply option gives the client a direct way to respond without joining your internal project system. Because link holders can reply, you should still confirm important approvals by naming the decision and person in your next update.
Write for a continuing record
Each entry should make sense later. Replace vague phrases such as "the usual changes" or "what we discussed" with the actual item and decision.
Name dates in full when confusion is possible. State whether a number is an approved cost, an estimate, or an example. Link to source files when the update depends on details stored elsewhere.
Keep each entry concise. A long page is manageable when each dated update has consistent headings and fewer than 200 words. A short entry also makes old decisions easier to scan.
Give access to the right people
Decide who should receive the email and who may use the link. A single client email keeps delivery simple, but the client can forward an update to colleagues when needed.
Forwarding can be useful because a sponsor or manager gets the same wording and context. It also means the link may reach more people. Put only suitable information on the page and use a more controlled channel for restricted material.
When a contact leaves the client company, update the delivery address and consider replacing the private link. Access reviews are less glamorous than a new dashboard, but they prevent avoidable surprises.
Use the page as a summary, not storage for everything
The page should hold client updates, not every draft, task, and internal comment. Link to approved documents when needed and keep working material in the tools that suit your team.
The clear boundary helps both readers. Your team can discuss unfinished options freely, while the client gets a considered account of results, next steps, requests, and changes.
The weekly client update guide explains how to write each entry. One page per client project then turns those entries into a useful history without asking the client to maintain another account.
Friday provides that stable private page, email delivery to one client address per project, and support for several projects under one account.