Skip to main content
Account Readiness measures how completely each client is set up in MSPortal.ai, scores it out of 100, and tells you which team member owns every remaining gap. The Companies view evaluates current configuration when you open it; historical snapshots support comparison. It is not a continuous live monitor.
Account Readiness is the Readiness tab of MSP Tools > Client Success. Saved links to the Account Readiness page and to the Company Audit address /settings/companies/audit open the Readiness tab.

Before you start

  • This is an MSP staff view. Company users cannot open Account Readiness.
  • You need Account Readiness: Read to open it. Changing requirements needs Account Readiness: Manage. The By owner view has its own permission, so a scorecard of named staff is never granted by accident.
  • Requirements assign owners by Team Role, so assign people to roles on each company’s Team tab. See Account teams and Team Roles.

Open Account Readiness

1

Open the Readiness tab

In the left sidebar under MSP Tools, click Client Success, then select the Readiness tab.
2

Choose your scope

Use the company selector at the top of the page to look at one client, your assigned clients, or the whole portfolio.
3

Pick a view

Use the Companies and By owner switch beside the tabs. Companies shows the grid and By owner shows the per-person rollup. The switch appears when your role can see the By owner view.

Summary cards

How the score works

The score is the share of a company’s requirements that are ready:
A company that satisfies every requirement scores 100%. Exempt checks are removed from the denominator entirely, so exempting something never quietly lowers a score.
If there are no applicable requirements, the view can show No score. Exemption is an administrative decision, not evidence that missing configuration was fixed.

Check states

Ready and Unconfirmed are separate on purpose. Some values can be present but wrong, and for those a person confirms once that the value is correct. If the underlying value later changes, the confirmation lapses automatically and the check returns to Unconfirmed.
A check can never be marked ready by a person while the data says it is missing. Confirming only ever applies on top of a check that already passes.

The fleet grid

Rows are companies. Columns are your requirements, grouped by area: Profile, Team, Integrations, Delivery, Engagement, and Operations. Checks with a setup destination link to the relevant page, so you can open a gap in a new tab with cmd-click or middle-click without losing your place in the grid. Requirements added in the last 30 days carry a New badge, so a score that moved because the bar was raised is easy to tell apart from a score that slipped.

Filtering

Every column filters in place, including:
  • Company, as a multi-select list
  • Score and Open, as numeric ranges
  • Worst status, to find every client with something missing
  • Owning role, to see everything a role is behind on
  • Owner, to see everything one person is behind on
Filters combine and page through matching companies. Use Check owner to select Mine, Everyone or an available owner; scores and totals then reflect that owner’s checks. Hide completed checks hides requirement columns that are ready or not applicable for every company on the current page. It does not exempt requirements or remove completed records.

Freshness

Read Current configuration, evaluated when you open this page or the displayed snapshot date to identify the evidence being shown. Reopen after correcting source configuration. Nightly snapshots support history; a successful settings save is not proof of a new historical snapshot.

Bulk changes

1

Select companies

With Manage permission, tick companies on the current page, then click Bulk update. For one company, use the row’s Update readiness action instead. The selection covers only the current page. Changing page, filters, sorting, or scope clears it.
2

Choose the change

In Update readiness, review the named companies. In Change, choose Exempt a requirement, Remove an exemption, Confirm a requirement, Clear a confirmation, Exclude from readiness, or Include in readiness.
3

Fill in the details

Choose the Requirement where asked. An exemption also needs a reason. Confirming needs every selected company to already satisfy the check and require a person’s confirmation.
4

Apply

Click Apply to N companies. Click Cancel to close without saving.
Confirm a requirement loads complete checks for the selected companies, even when Check owner limits the grid. The Requirement list offers only checks that every selected company can confirm. Wait for the checks to load; if loading fails, click Retry. Changing Change clears the selected requirement so you can choose one that applies to the new action.
The check menu’s Exclude check and Remove exclusion actions can save immediately. Inspect the company and requirement before using them; there is no page-level Save to undo them.

Company drilldown

Click a company name to open its drilldown. This evaluates live rather than reading the overnight snapshot, and lists everything still open, worst first. Each item shows:
  • What the requirement is and what state it is in
  • What the check actually found, for example which fields are blank or which roles have no holder
  • Who owns it
  • A Fix button that opens the page that resolves it
Two actions are available with the Manage permission:
Records that a person has checked the value and it is correct. Available on checks in the Unconfirmed state. The confirmation lapses automatically if the value changes afterwards.
Exempts one requirement for one client, with a required reason. The check stops counting toward that client’s score until the exemption is removed. Exemptions do not expire, and they survive a requirement being switched off and back on.
Confirmations and exemptions are both listed further down the drilldown so either can be withdrawn later. Confirm, clearing a confirmation and removing an exemption are immediate actions. Marking a check not applicable opens a reason dialog and requires its submission; closing it does not save.

Readiness by owner

The By owner view rolls readiness up per person, based on who holds the primary owning role for each requirement at each company. Interpret vs team with the number and nature of assigned checks, client coverage and the period. Readiness is a configuration measure; it does not by itself establish an employee’s quality of work. People below the minimum client count are marked Small book and are left out of the team average so a very small book cannot skew everyone else’s baseline. Trend deliberately ignores requirements that did not exist at the start of the period. Adding a new requirement raises the bar, and that should not read as everyone regressing.

Configure requirements

1

Open the settings

Go to Settings > MSP Tools > Account Readiness, or click Configure in the header of the Readiness tab. You need Account Readiness: Manage.
2

Add a requirement

Click Add requirement. To change one, edit its row.
3

Choose what it checks

In What does this check?, pick a kind, such as Company profile fields or Integration company mapping. Then fill in its specifics, picked from your own data, such as your roles, custom fields, compliance groups, or report templates.
4

Set the owner

Choose a Primary owner role. Add Supporting roles if others can fix it. The score counts the check once, against the primary owner.
5

Choose the options

Optionally set a Name (optional), and turn on Needs a person to confirm it if someone must confirm the value on top of the data check.
6

Save

Click Save. Use the On switch to turn a requirement off or on, and Move up or Move down to reorder.
Each requirement has these settings.

Save behavior

Create or edit a requirement in its dialog and click Save. Changing its On switch or moving it in the requirements list saves immediately. Delete uses confirmation and is not staged for a later page Save. Bulk requirement editing applies the fields selected in its dialog; review the chosen requirements before saving.

Check kinds

A report schedule counts as covering a company whether it targets that company directly, its company group, its industry, or all active companies. You do not need a separate schedule per client for this check to pass.

Primary owner versus supporting roles

The split matters. The work list shows a failing check to every role that could fix it, so nobody is left out. The score counts each check once, against the primary owner, so a portfolio total always matches the real number of gaps.

Excluding a company

Some clients are not meant to be measured at all. Use the company row or bulk Exclude from readiness operation to remove the company from readiness measurement. Review excluded companies in Readiness settings and restore them there when appropriate. Excluding a company does not delete the company or fix its setup.

Requirements you cannot fix in MSPortal.ai

Primary contact is read from your PSA and there is no page in MSPortal.ai that sets it. It ships as a confirm-required check: set the contact in the PSA, then confirm it here once. If the PSA contact changes later, the check returns to Unconfirmed on its own.

Best practices

Every tenant starts with a default requirement set that covers company details, team ownership, compliance, reporting, standards, and the core records. Run with it for a couple of weeks, then add the requirements that reflect how your team actually works.
A requirement with no owning role still shows in the grid, but it will not appear in anyone’s rollup. Assigning owning roles is what turns the grid into a work list.
If a requirement genuinely does not apply to one client, exempt it there with a reason. Switching the requirement off removes it for everyone.
The By owner view is built for that conversation: review the assigned work, coverage and context rather than treating the score as a complete performance ranking.

Troubleshooting

Frequently asked questions

No. This is an MSP staff view. Read, Manage and By owner access are separate permissions.
No. The Companies view evaluates current configuration when opened and history uses snapshots. Check the evaluation message or date before drawing conclusions.
No. The underlying requirement is satisfied but needs human confirmation. A genuinely missing requirement cannot be made ready by confirmation alone.
No. It removes that requirement from the company’s applicable score denominator and records the reason. The configuration itself is unchanged.
No. Review the named selected companies. Page, filter, sorting and scope changes clear the selection; the grid does not select all result pages.
No. It hides columns completed for every company on the current page. It does not change requirements or exemptions.
No. The owner scope changes which checks contribute to the shown scores and totals. Confirm the owner scope before comparing results.
No. Confirmation and exemption-removal actions, requirement switches and reorder controls can save immediately. Requirement and bulk dialogs have their own submit actions.
No. It removes it from readiness measurement. Restore excluded companies in Readiness settings when they should be measured again.
No. It compares readiness rates within the available coverage. Consider assigned checks, client mix, small-book flags and the period before interpreting it.