On this page
What clients want to know during a project
A client paying for a server migration or an office move rarely wants a task list. They want answers to a few questions:
- Is it on track, and if not, why?
- What happens next, and when will it affect my staff?
- What do you need from me, and by when?
- What has been decided, and who decided it?
If the client has to ask for these answers, the project feels slower than it is. If they can check for themselves, they come to project meetings already informed.
Common ways MSPs report project progress
| Method | Works well for | Where it falls short |
|---|---|---|
| Status emails | Small projects with one contact | Scattered across inboxes; hard to find the latest |
| Regular meetings | Decisions and difficult conversations | Status is out of date between meetings |
| PSA notifications | Telling a client a ticket changed | Too granular; no picture of the whole project |
| Shared spreadsheets | Detailed plans | Rarely kept current; no record of decisions |
| A project view in the client portal | Ongoing visibility for several contacts | Needs someone to keep updates and milestones current |
Most MSPs combine a client-visible project view with fewer, shorter meetings that focus on decisions.
What a useful weekly project update includes
Keep updates short and consistent so clients learn where to look:
- Completed this week. Two to five items in plain language.
- Coming up next. What happens before the next update, especially anything that affects the client's staff.
- Risks and concerns. Be honest about slipping dates early, with the reason and what you are doing about it.
- Decisions needed. Each with an owner and a date.
Keep internal notes, such as vendor problems or effort overruns, out of the client-facing update and in your team's notes.
Keep client decisions and approvals out of email threads
Decisions buried in email are the main source of project disputes. Record each approval, question or decision as an item with a named person on the client side, a due date and the answer they gave. When the client approves a change in scope, both sides can see when and by whom. This also makes the next QBR meeting easier, because the history is already written down.
How MSPortal shares project progress with clients
MSPortal runs native projects with phases, tasks, time tracking and a dependency-aware schedule, or syncs projects from ConnectWise, HaloPSA or Autotask. Either way, the client-facing parts work the same. The project management feature page shows both views.
Clients see the projects you allow in card, list, Kanban or schedule views. Inside a project they can:
- read the weekly updates you mark as client-visible, organized into completed work, next steps, risks and decisions needed;
- follow milestones and deliverables with their documents;
- see the project's health status with its reason, and the milestone dates you share;
- answer approvals, questions and decisions assigned to them, from the project's Decisions and Action Items lists.
Clients cannot comment on updates. You control access by company, role, project type and per-item visibility, so internal updates stay internal. The project updates guide and the guide to responding to project decisions show the client side.
Project AI reads a project's tickets, milestones, updates and decisions to explain progress and blockers. It drafts weekly updates and proposes milestones, deliverables, decisions and status changes, and nothing saves until someone selects Apply. Client users can ask it questions but cannot apply changes.
Projects also feed reviews. The report builder has project blocks for health, progress, timeline and cost, and a project added to a meeting agenda shows its next milestone and the next client decision. For PSA projects, status, schedule dates and assignees write back to ConnectWise, HaloPSA and Autotask, while milestones, updates, decisions and deliverables stay in MSPortal.
Related questions
Can clients see projects synced from the PSA?
Yes. MSPortal syncs projects, project tickets and time entries from ConnectWise, HaloPSA and Autotask, and clients see the projects and fields the MSP chooses to share.
Can clients see internal project notes?
No. In MSPortal, updates and items have their own visibility, so internal updates are hidden from client users. Clients see only the updates, milestones and deliverables the MSP marks as client-visible.
Does AI write project updates automatically?
No. In MSPortal, Project AI drafts weekly updates and proposes changes, but nothing is saved until a person reviews the draft and selects Apply.
How is new-client onboarding tracked as a project?
In MSPortal each onboarding portal is linked to a project, so the client sees their tasks and progress while your team tracks every phase. See what an MSP client onboarding process should include.
How do projects connect to a client's IT roadmap?
Projects are often the delivery side of roadmap items agreed in a review. See how MSPs build a technology roadmap with clients.