How MFDs Can Automate Portfolio Review Meetings

What parts of a portfolio review meeting can an MFD automate?

Most of the effort in a review cycle happens before and after the conversation, not during it. Deciding who is due, pulling current holdings, checking pending paperwork, booking a slot, sending reminders and following up on agreed actions are all repeatable steps. These are the parts worth automating.

The conversation itself should stay human. A CRM can remind you that a client raised a concern about a goal last time, but it should not script what you say. Think of automation as the preparation desk and the follow-up desk, with the advisor in the middle.

• Identifying which clients or families are due for review this month
• Creating a preparation task for the relationship manager ahead of the meeting
• Sending scheduling requests and reminders to the client
• Attaching a standard agenda and a checklist of documents to verify
• Creating follow-up tasks from the meeting record with owners and dates
• Flagging reviews that were missed, cancelled or rescheduled more than once

How to set a review cadence by client segment

A review cadence only works if it is written down and applied the same way across the book. Many practices group clients by household rather than by individual PAN, because a family usually meets together and makes related decisions. Segmenting by household also avoids booking three separate meetings for one family.

Keep the segmentation policy simple enough for the team to apply without asking the owner. Store the segment and the review frequency as fields on the household record, so the CRM can calculate the next due date instead of someone maintaining a separate spreadsheet.

• Define segments using criteria the business already agrees on, such as relationship size, complexity or stage of life
• Assign a default review frequency to each segment
• Allow a documented exception, for example a client who asks for more frequent check-ins
• Record the last completed review date so the next one is calculated from reality, not from the plan

What should a pre-meeting preparation checklist include?

Preparation is where most reviews lose quality. When the relationship manager opens the meeting without current data, the first twenty minutes go into catching up. A checklist task created a week or two before the meeting keeps preparation consistent regardless of who runs it.

The checklist should point to where information lives rather than duplicate it. Holdings and transaction history usually come from the back-office system or RTA reports from CAMS and KFintech. The CRM holds the relationship context, open service requests and notes from the last review.

• Current holdings summary and SIP, STP or SWP status from the back-office report
• Any SIP rejections, bounces or stopped mandates since the last review
• Open service requests, pending KYC updates or nominee changes
• Folios with missing details such as bank mandate, email or mobile mismatch
• Actions agreed at the previous review and whether they were completed
• Life events or concerns recorded since the last meeting

How to record meeting notes in a CRM without losing context

A good meeting record balances structure with free text. Structured fields make reporting possible: meeting date, attendees, mode, topics covered and whether follow-up is required. Free text captures what the client actually said, which is what the next person reading the record needs most.

Write notes on the same day. If the relationship manager has to remember the meeting two days later, detail is lost. A mobile-friendly form or a short voice-to-text note can help, as long as it ends up on the household record and not in a personal chat.

Avoid recording anything in notes that reads like a recommendation you have not documented through your proper process. The meeting record is an operational log. Suitability and product discussions should follow whatever documentation standards your practice and applicable guidance require.

Turning agreed actions into follow-up tasks

Reviews often end with a list of things to do: update a nominee, change a bank mandate, send a statement, start a new SIP, schedule a call with a family member. If these stay in the notes field, they get lost. Each action should become a task with an owner and a target date.

Link every follow-up task back to the review record. That way, when you open the review a month later, you can see which actions closed and which are still pending. It also makes the next preparation checklist easier because open items carry forward automatically.

• One task per action, not one task for the whole list
• Owner assigned before the relationship manager closes the meeting record
• Client-facing actions include a planned communication back to the client
• Overdue tasks escalate to a team lead or the owner after an agreed period

Which dashboards show whether the review process is working?

Review automation is only useful if someone looks at the results. A short weekly dashboard helps the owner see coverage without chasing each team member. Focus on exceptions rather than totals, because the goal is to catch clients who are slipping through.

In Aina CRM, these views are typically set up as household-level reports so the team sees families rather than scattered individual records. Whatever tool you use, the same questions apply.

• Households due this month with no meeting booked
• Reviews overdue beyond the planned date
• Meetings completed without a meeting record
• Follow-up tasks from reviews that are past their target date
• Clients who have rescheduled repeatedly

Core checklist

A practical action plan

1. 1

   Define review frequencies and exceptions with the business team.

2. 2

   Generate review tasks ahead of the target month or date.

3. 3

   Use a standard meeting record while allowing free-form context.

4. 4

   Track completion, rescheduling and open actions on dashboards.

Frequently asked questions