Client Portal Onboarding Checklist: The First 48 Hours
Most client portals fail in the first week, not because they are badly built but because nobody told the client what it is for. Here is the checklist that fixes that.
A portal that nobody logs into is worse than no portal. You still answer the same emails, and now you also maintain a second surface.
Adoption is almost never a product problem. It is an onboarding problem, and it is decided in the first 48 hours.
Before you send the invite
The most common mistake is inviting a client to an empty portal. They log in, see nothing useful, and never return.
- At least one real, current item in every section the client will see
- No placeholder or test rows - delete 'Test project 1' before inviting anyone
- Empty states that read as intentional, not broken ('No invoices yet' beats a blank panel)
- Correct client relation on every record, verified by viewing as that client
- Internal fields hidden and checked - run the privacy audit before, not after
- The client's contact email exactly matching the member record they will sign in with
Never invite into an empty portal
If there is nothing to look at, the client learns that the portal is not where things happen. That lesson is very hard to unteach. Populate first, invite second.
What the first screen has to answer
A client landing in a portal for the first time is asking three questions, in this order.
Where am I?
Your logo, your domain, and a heading naming their company. If it looks generic, it feels like spam.
What is happening?
Current status of their work, in words a non-specialist reads without translation.
What do I do?
Anything waiting on them, clearly separated from what is waiting on you.
If the first screen answers those three, people come back. If it opens on a dense table of every task ever created, they do not.
The invite itself
The invite email does more work than the portal design. It sets the expectation of what this thing is for.
What a good invite says
- What the portal replaces - 'instead of me emailing you status updates every Friday'
- The one thing to do right now - 'have a look at the two items waiting for your approval'
- That no account or password is needed, just their email
- Who to reply to if something looks wrong
Send it from a person
A magic-link email from a no-reply address looks like a phishing attempt, especially to clients who were not expecting it. Tell them it is coming, ideally in a message you were already sending.
The first 48 hours
Day 0: invite and mention
Send the invite, then mention it in whatever channel you already use with them. The mention matters more than the email.
Day 1: check they got in
If they have not signed in, the link went to spam or the email on the member record is wrong. Both are quick fixes if you catch them early.
Day 2: route one real thing through it
Post the next update in the portal and reference it rather than repeating it by email. One repetition teaches the habit.
Making it stick past week one
The portal becomes real when it is the only place something lives. As long as you also send the update by email, the email wins — it arrives, and the portal does not.
- Stop duplicating status into email; link to the portal instead
- Put approvals in the portal so there is a reason to log in
- Keep it current - a stale portal is read once and abandoned
- Give it a predictable rhythm, so the client knows when there is something new
- Ask, after two weeks, what they wish it showed
The honest test
Two weeks in, count how many status questions you answered by email. If the number has not dropped, the portal is not carrying its weight yet — and the fix is usually routing more real work through it, not redesigning it.
A reusable version
Once this works for one client, the goal is to stop doing it by hand.
What to templatize
- The portal structure itself, so a new client is a new row rather than a new build
- The invite email, with the one-thing-to-do slot left to fill in
- The pre-invite checklist above, as a task list in your own workspace
- The day-1 and day-2 follow-ups, as scheduled reminders
How much should be in the portal before I invite a client?
What if the client just keeps emailing me?
Should clients be able to comment or only read?
How do I onboard a client who is not technical?
Onboard the next client in minutes
One portal template serves every client, each seeing only their own records. Add a row, send an invite.