Planning identifies the changes. Tasks turn those changes into action.

When you're working through the planning modules and you identify a gap (not enough life insurance, no emergency fund, an outdated will), you note the change. But someone still has to do something about it. That's where tasks come in.

Changes to be made are strategic: "open a Roth IRA," "increase disability coverage," "update the trust." Tasks are operational: who needs to do what to make that change happen. If the change is "open a new brokerage account," the task might be "Taylor sends account opening paperwork" or "client signs and returns the forms."

That separation matters. Changes live in the plan as part of the financial picture. Tasks live in the workflow as the execution layer. You can create a task anytime, from anywhere in the app. There's a button in the header that's always accessible, so when something comes up during a planning session, you capture it on the spot.

Each task has a description, an assignee (advisor or client), an optional due date, and a status. That's it. No categories, no priorities, no project management overhead. Just "what needs to happen" and "who's doing it."

Client-assigned tasks show up in their portal. When they complete something, you see it on your side. This turns the portal into a two-way channel: you tell them what to do, they do it, and you see the result without chasing them.

Kerdora flags overdue tasks and tasks due today, so you can see at a glance what needs attention across your client base.

Notes are your private scratch pad for each client. A rich text editor where you can jot down meeting observations, reminders, or anything that doesn't fit neatly into the plan structure. Bold, lists, links, the basics.

Notes are advisor-only. Clients can't see them. Write whatever you need to.