MFD Team SOP: Daily, Weekly and Monthly Checklist
A practical operating rhythm for leads, service requests, reviews, data quality, management reporting and process improvement.
An SOP is useful only when it defines observable work, ownership and review frequency. The checklist should be short enough to follow and specific enough to reveal missed commitments.
What should an MFD daily checklist include?
The daily checklist protects client commitments that cannot wait a week. It should take minutes to run, not hours, and each item should point to a specific list or screen rather than a vague instruction like 'check pending work'.
For a typical MFD office, the daily items fall into four areas: new enquiries, client service, transactions and records. The person responsible for each area should be named, and a backup should be named for leave days.
- Respond to or assign every new enquiry received since the last check
- Review service requests opened, due today or overdue
- Check transaction status and rejections on the platforms you use, such as BSE StAR MF, NSE NMF II or MF Utilities
- Follow up on pending KYC, nominee, bank mandate or document requests
- Log calls, meetings and WhatsApp conversations against the client record
- Flag anything urgent to the principal or team lead before end of day
What belongs in a weekly MFD team review?
The weekly review is where patterns become visible. A single delayed request is a daily issue. The same type of request being delayed every week is a process issue that needs a decision.
Keep the meeting short and run it from saved reports. Each item should end with an owner and a date, recorded in the same system the team uses daily.
- Lead pipeline ageing and leads without a next action
- Service requests open beyond the agreed turnaround
- Transaction rejections and their causes, grouped by type
- Upcoming client reviews for the next two weeks and their preparation status
- Action items from the previous week's meeting
- Any client complaint or escalation and its current status
What should the monthly MFD operations checklist cover?
Monthly work focuses on data quality, reconciliation and improvement. This is the right time to compare CRM records against RTA reports and platform data, and to fix gaps before they spread into dashboards and client conversations.
It is also the time to look at the team itself: workload balance, training gaps and whether the SOP still matches how work is actually done.
- Reconcile client and folio data against CAMS and KFintech reports
- Check for missing PAN, email, mobile, nominee or family mapping
- Review SIP additions, cessations and bounces for follow-up
- Confirm the review calendar for the coming month
- Review dashboard figures against source data for obvious mismatches
- Record process changes and update the SOP document
Should there be a quarterly or annual layer to the SOP?
Some tasks do not fit a monthly rhythm but still need a fixed home. Without one, they tend to be remembered only when something goes wrong.
A short quarterly and annual list covers these. The exact items depend on your practice, and anything touching regulatory or distributor obligations should be confirmed against current AMFI and SEBI guidance and reviewed by a qualified professional.
- Review user access and remove accounts for people who have left
- Check ARN and EUIN renewal timelines for the principal and team members
- Review document retention and record-keeping practices
- Revisit client segments and review frequency assignments
- Review templates for client communication and update outdated wording
How to assign owners and reviewers in an MFD SOP
An SOP without owners is a wish list. Every checklist item should have a doer and a reviewer, and they should usually be different people. In a solo practice with one assistant, the principal can review a short weekly summary rather than each individual task.
Write each item so that completion is observable. 'Follow up on documents' is hard to verify. 'Every pending document request has a follow-up date in the CRM' can be checked from a report in a few seconds.
How to make SOP adherence visible without micromanaging
The easiest way to check adherence is to look at the records the work produces. If every service request should be acknowledged the same day, a report of unacknowledged requests shows adherence directly, with no separate status updates needed.
A CRM such as Aina CRM can hold recurring tasks, checklists and dashboards that reflect the SOP, but the tool only shows the gaps. The manager's job is to discuss them, understand the cause and decide whether the fix is training, workload or a change in the process itself.
When a checklist item is skipped repeatedly, ask whether it still matters. Removing obsolete steps keeps the SOP credible.
Core checklist
Daily: new leads, overdue tasks and urgent service requests
Daily: data updates and client communication records
Weekly: pipeline ageing, service turnaround and review actions
Weekly: exception, rejection and escalation review
Monthly: data-quality checks and dashboard reconciliation
Monthly: team performance, training and process-improvement review
A practical action plan
- 1
Assign an owner and reviewer to each checklist item.
- 2
Link every SOP step to the screen or record where work is captured.
- 3
Use dashboards to review exceptions instead of preparing manual reports.
- 4
Update the SOP when the actual process changes.
Frequently asked questions
How long should an MFD daily checklist be?+
Short enough to finish reliably on a busy day. For most teams that means somewhere around six to ten items per role, each pointing to a specific list or report. If the checklist regularly takes too long, move lower-risk items to the weekly review.
Does a solo MFD need an SOP?+
Yes, even a solo practice benefits from a written routine, because it makes the work easier to hand over when you hire, take leave or bring in an assistant. A solo SOP can be a single page with daily, weekly and monthly sections. It also helps show a consistent process if you are ever asked to describe your operations.
How often should an MFD update its SOP?+
Review it at least every quarter and whenever a process actually changes, such as moving to a new transaction platform, adding a team member or changing how reviews are scheduled. An SOP that describes an old process is often ignored, so small regular updates work better than rare rewrites.
Where should the SOP document be stored?+
Store it where the team already works, with one current version and a visible date of last update. Linking each step to the relevant CRM view or report helps new team members find the right screen without asking.
A final note
A CRM can make adherence visible, but managers still need to coach, review and improve the operating rhythm.
See how Aina Tech sets this up in practice: MFD Operations Automation Software.
This article provides general operational and technology information. It is not investment, legal, tax or regulatory advice.