9.3 Day Planning, Time Management & the 3P Approach
Key Takeaways
- The 3P approach — Plan, Prioritise, Perform — is the curriculum's daily-effectiveness framework for RIA sales; the sequence matters, because prioritising without planning is only faster reacting.
- A workable day plan names three outcomes, marks fixed points including mutual fund cut-off times, and passes a realistic capacity check.
- The Eisenhower grid puts reviews, profile refreshes and proactive drawdown calls in the important-but-not-urgent quadrant — the quadrant where an advisory book actually grows.
- Batching the inbox into one or two passes is the single largest productivity gain, because continuous email monitoring fragments attention.
- Calls made and meetings booked are inputs; profiles completed, agreements signed and reviews held are outcomes — never let input volume stand in for outcomes.
9.3 Day Planning, Time Management & the 3P Approach
Quick Answer: An RIA sales day fragments into calls, paperwork, follow-ups and interruptions, and the work that actually compounds — profiling, reviews, proactive contact — is the work with no deadline attached. The curriculum's answer is a 3P approach: Plan, Prioritise, Perform, supported by daily effectiveness tools such as a written day plan, time blocks, a follow-up queue with service-level commitments, and an end-of-day review.
Why a PAIA's day needs a structure
The non-core advisory role is almost entirely made of interruptions: a client calls about a statement, a KYC document bounces at the KRA, an AMC asks for a re-signature, a prospect replies to an email from last week. None of it is unimportant, and all of it is urgent-feeling. Meanwhile the activities that build the book — booking review meetings, completing profiles, calling clients during a drawdown — carry no external deadline and quietly slip.
The result is a familiar pattern: a full day, a busy CRM, and no movement in the pipeline. Day planning exists to stop that.
The 3P approach
NISM's Series XXV-B curriculum lists a "3P approach" among the daily effectiveness tools for RIA sales. In everyday sales-productivity practice the three Ps are Plan, Prioritise, Perform, and they map cleanly onto an advisory desk. (Use NISM's own free study material on its YouTube channel for the exact wording the examiners use; the discipline below is what the framework is testing.)
| P | Question it answers | Concrete output at an RIA desk |
|---|---|---|
| Plan | What does today have to achieve? | A written day plan made the previous evening: the three outcomes that matter, plus the fixed appointments |
| Prioritise | In what order, and what gets dropped? | Each task sorted by urgency and importance; the day's one "compounding" task protected |
| Perform | How does the work actually get done? | Time blocks, single-tasking, same-day CRM logging, an end-of-day review that rolls the misses forward |
The sequence matters. Prioritising without planning is just reacting faster. Performing without prioritising is being busy.
Plan — the evening ritual
Build tomorrow's plan today, while the context is fresh. A workable plan has:
- Three outcomes, not twenty tasks — for example: "complete the Sharma profile", "book two reviews", "clear the KRA rejection queue".
- Fixed points — meetings, the RIA's advisory desk hours, the AMC cut-off time (mutual fund purchase and redemption requests must be time-stamped before the applicable cut-off, or they get the next day's NAV).
- A realistic capacity check. If the plan needs nine hours in a seven-hour day, it is a wish list.
Prioritise — urgent versus important
The Eisenhower grid is the simplest tool that survives a real advisory day:
| Urgent | Not urgent | |
|---|---|---|
| Important | Client complaint, KYC rejection, missed SIP, cut-off-bound instruction → do now | Review meetings, profile refreshes, proactive drawdown calls → schedule; this is where the book grows |
| Not important | Most inbound "quick questions", routine forwarding → batch or delegate | Idle report-refreshing, unstructured browsing → eliminate |
Two rules make it operational: (1) protect at least one "important, not urgent" block every day before the inbox opens; (2) segment the client base — a small share of clients accounts for most of the assets and most of the service load, and the review cadence should reflect that without ever leaving a smaller client unserved.
Perform — time blocks and single-tasking
| Block | Time | Work |
|---|---|---|
| Opening block | First 60–75 min | The day's one compounding task — profiles, reviews, proactive calls |
| Client calling window | Mid-morning | Outbound calls, when clients actually answer |
| Processing block | Late morning | KYC, forms, KRA queue, cut-off-bound instructions |
| Inbox / query batch | Post-lunch | Email and service queries handled in one pass, not continuously |
| Review & meetings | Afternoon | Scheduled client and RIA meetings |
| Close-out | Last 30 min | CRM logging, follow-up queue update, tomorrow's plan |
Batching the inbox is the single biggest win. Continuous email monitoring fragments attention and is the main reason a 20-minute profiling task takes ninety.
Daily effectiveness tools
- The follow-up queue with an SLA. Every open item carries an owner and a promised date. "I'll get back to you" without a date is how complaints start.
- The pipeline board. Prospects visible by stage, so stalled ones are obvious.
- The call plan. Ten named clients before the calling window starts, not "some calls today".
- The end-of-day review. Five minutes: what moved, what did not, what rolls forward, what the CRM is still missing.
- Activity metrics, read honestly. Calls made and meetings booked are inputs; profiles completed, agreements signed and reviews held are outcomes. Track both, and never let input volume substitute for outcomes.
Common traps
- Planning in the head. An unwritten plan is a preference, not a plan.
- Letting the loudest client set the agenda. Responsiveness is a service standard, not a scheduling algorithm.
- Deferring the CRM to Friday. The record loses evidential value and the week loses its detail.
- Confusing motion with progress. Twelve calls that book no meeting is a day's activity and no day's outcome.
- Skipping the drawdown call because it is uncomfortable. It is the highest-value ten minutes in a bad month — and it is service, not advice, so it stays firmly inside the non-core boundary.
Using the urgent-versus-important grid, where do proactive calls to clients during a sharp market drawdown belong, and what follows for the day plan?
A PAIA reaches the end of the day having handled 40 inbound emails and 12 calls, but has completed no client profile and booked no review. Which diagnosis best fits the 3P framework?