Publish updates
Share project progress and selected deliverables in a dedicated client space.
A better client experience
Give clients clarity without giving away your workspace.
Share only what is ready for your client to see. Internal tasks and agency notes remain separate.
pNorthstar × Pultify
Project on trackWebsite redesign · Update 04
A sharper first impression
We've brought the new homepage direction to life. Take a look and share your thoughts.
Homepage direction.pdfDownload
Your team
ASTeam member
JMTeam member
RKTeam member
Review and approve
Clients can approve a published update or request changes, with decisions recorded.
Files and feedback
Attach deliverables, receive comments, and keep review history close to the work.
An approval process clients can actually follow
Prepare an update
The agency selects the project information and deliverables ready to share.
Publish to the client
Only published material appears in the client-facing portal.
Collect a decision
The client can approve the update or request changes and leave comments.
Keep the history
The team can revisit feedback and the decision history alongside the work.
Illustrative workflow. Client portal access is scoped to the client relationship; internal notes and unpublished tasks remain private.
Can clients download files?
Yes. Published deliverables can be made available for download.
Can agency staff preview the portal?
Yes, through a read-only preview that does not impersonate the client.
How this works in practice
Publish intentionally, not automatically
A client portal should show work that is ready for review—not every internal task, discussion or draft. Prepare the update inside the agency, attach the relevant deliverable and publish it when the team is ready.
The client sees the published material in a focused view, while the agency retains its internal workspace and assignments.
Replace ambiguous approvals with recorded decisions
A reply in a chat thread can be hard to trace back to the correct version. Ask clients to approve a published update or request changes against that update.
Comments and approval history remain connected to the project, making it easier to see what needs revision and what has already been accepted.
Give clients files without opening internal storage
Clients may need a PDF, a design export or another approved deliverable. Published files can be downloaded from the portal without granting access to internal agency documents.
The agency chooses what to publish. Previewing the portal as an agency user is read-only and does not impersonate a client.
Keep expectations clear for both sides
The portal helps with project communication and sign-off; it is not a replacement for contracts, scope agreements or legal acceptance procedures.
For sensitive or regulated deliverables, define the required sign-off in your contract and use the portal as an operational record.
Illustrative workflow, not a customer case study.
Example: approve a campaign deliverable without opening internal work
A fictional agency needs a client to sign off on a set of social assets. The portal is a deliberately limited review surface.
- 1
Prepare the material internally
Complete the draft in the agency workspace and decide which file or update is ready for external review.
- 2
Publish a focused update
Share the selected material with the client through the project portal. Do not expose internal task discussions.
- 3
Collect a decision
The client comments, approves or requests changes on the published item.
- 4
Act on feedback
The agency translates the requested changes into its own internal work and prepares an updated deliverable.
- 5
Keep the record
Use the published update and its decision history to understand what was reviewed. Contractual acceptance requirements still come from the agreement.
Frequently asked questions
Can a client edit tasks or pipeline stages?
No. The portal is designed for review and communication, not editing agency operations.
Are all project files visible to clients?
No. Only deliberately published files and updates are client-facing.
Is portal approval a legal signature?
No. Agree any formal acceptance or signature requirements separately in the contract.