Skip to main content
GullySystem
Financial services

Task Management for Mutual fund distributors

Give project work an owner, due date and visible status.

Project Management

Does this function belong in your operation?

Use when work crosses people or requires follow-up beyond personal reminders.

A piece of work needs assignment or follow-up.

Chasing a KYC hold, collecting a nominee form and calling a bounced SIP client become tasks for named staff. Due dates are set. The partner sees what is overdue each morning.

Bring the records the workflow depends on.

  • Task descriptions
  • Owners and due dates
  • Project and dependency references

Outputs to check

  • Owned task register
  • Overdue and blocked-work list
  • Completion and handover history

Follow the task management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the result

    Record the work, project and evidence expected at completion.

  2. 2. Assign the owner

    Set responsibility, due date and any prerequisite.

  3. 3. Record progress

    Keep comments, attachments and blocked-work reasons on the task.

  4. 4. Review completion

    Check the expected result through the agreed responsible person.

  5. 5. Close or reopen

    Retain completion history and create explicit follow-up where work remains.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Team member

Updates assigned work, records blockers and submits completion evidence for the agreed review.

Coordinator

Assigns work, reads what is overdue, and knows who is genuinely full before promising a client a date.

Owner

Looks at what is stuck and not at what is moving. Those are the ones that cost money.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Owner leaves or is absent

Reassign open work with comments and attachments intact.

Dependent work blocked

Show the unresolved prerequisite and identify who must act.

Task reopened

Retain the earlier completion and record the new issue or missing outcome.

Can this work independently?

Tasks can stand alone with named users and due dates. Project schedules, time records and document approvals provide context when connected. Completing a task should not automatically post an invoice, release stock or approve a document unless that separate handoff is explicitly designed.

Systems and records it connects with

  • Project timelines with Gantt charts: Planned dates, dependencies and recorded milestone progress.
  • Project time tracking: Approved task hours and their billable classification.
  • Notifications: Approved event messages and delivery or failure status.
  • Client portal: Permitted customer documents, requests and account views.

Configure, test and introduce the workflow.

  • Name the kinds of tasks your team handles. We return task types and checklists for each.
  • List the clients or projects tasks belong under. A structure arrives to browse. Open tasks from your sheets or chats are loaded. Owners are checked and dates fixed.
  • A few people use it daily. Phone use is tested, and the rest join after changes.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Open tasks have an owner.
  • Overdue tasks are identifiable.
  • Closed work retains its completion record.
Mutual fund distributors

How the business operates.

Your book is hundreds of SIPs across families, fund houses and folios. It earns trail only while those SIPs keep running, and keeping them running is follow-up work done on the 5th, 10th and 15th of every month.

SIP failure and cessation alerts

Flag mailback entries every morning with the client’s number beside them, so the call happens before the next debit date.

KYC, mandate and nominee board

List every investor’s KYC, debit mandate and nominee status in one place, with the missing item named.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Family and folio register. Group every folio of a household together, with fund house, plan type, holder names and the goal each holding was opened for.
  • SIP calendar and failure alerts. List each plan against its debit date and flag rejections or lapsed registrations in the morning, with the client’s number beside the line.
  • Debit mandate register. Track each mandate from form to approval, with bank, limit, validity and the plans that depend on it, and chase any stuck for too long.
  • KYC and nominee board. Show every investor’s KYC status and nominee declaration in one list, with the missing item named and the person who will chase it.

Operational bottlenecks to check

Failed SIP debits are spotted too late

After two rejected instalments the registration lapses, and the client has quietly stopped investing. You hear about it at the next review.

KYC on hold blocks the next purchase

A KYC record shows on hold, or the nominee declaration was never given, and you learn when a fresh purchase is rejected. The client asks what went wrong.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry

    Each referral or walk-in is recorded with where it came from, what the family wants and the next step promised. The reminder fires on the date the owner set.

  2. 2. Onboarding

    The investor’s KYC status, nominee choice, bank account and debit mandate are recorded, with the missing item named. Scanned forms are kept on the client’s file.

  3. 3. Plans and folios

    Each regular plan is entered with its folio, fund house, amount and date, and grouped under the family. The goal each plan was started for is noted beside it.

  4. 4. Report reading

    Reports from the registrars and platforms are loaded each morning. Rejected debits, ceased plans and status changes become tasks on a named staff member’s list.

  5. 5. Reviews and statements

    Before a review, the family page shows plans, dates and notes from the last meeting. At year end, holding and gains statements are gathered family by family.

  6. 6. Brokerage check

    Expected trail is worked out per folio and compared with what each fund house paid. Folios with a gap go onto a query list for that fund house.

Industry reports to connect with

  • Failed and lapsed plans by client, fund house and week
  • Mandates and KYC items outstanding, oldest first
  • Enquiries by source, goal and stage
  • Follow-up tasks open and closed by staff member

Questions before implementation.

When should mutual fund distributors consider task management?

Use when work crosses people or requires follow-up beyond personal reminders. A piece of work needs assignment or follow-up.

What should we bring to the requirements discussion?

Bring anonymised examples of Task descriptions; Owners and due dates; Project and dependency references. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Give project work an owner, due date and visible status. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A completed status records the team's decision rather than independent proof that work meets a standard.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Open tasks have an owner. Use this check when reviewing the first working version.

Talk to us

Discuss task management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements