Todo Overview Public

Todo

Standalone ERPat Todo module. Controller, model, views, language, routes, menu, permissions, migrations and cron jobs are fully owned by this package and loaded at runtime through the HMVC compatibility layer (App_Router + module package paths).

Guide version: r1 Module version: 1.0.0 Updated: 2026-07-30 Estimated time: 2 min 1 views
You are viewing version r1 of this guide. View the current version
End-user documentation

Todo

A simple task list for personal and team reminders, due dates, assignments, completion, widgets, and scheduled reminders.

Where users startTodo
Primary goalHelp a beginner understand what the module does and how to operate it safely.
Last reviewed2026-07-10

Purpose and What Problem This Solves

The Todo module captures small actions that should not be forgotten. It is lighter than Projects and more action-oriented than Notes, making it useful for quick personal or team follow-ups.

Plain-language rule: If a user can explain what record they are creating, why it exists, who owns it, and what happens next, they are ready to use the module responsibly.

Who normally uses this module

Individual staff users Team leads Managers Administrators

What You Can Do Here

  • Create personal reminders and simple assigned actions.
  • Track due dates and completion status.
  • Use dashboard or topbar shortcuts to see pending work.
  • Separate small tasks from larger project plans.
  • Support daily personal productivity routines.

Core Concepts and Terms

Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.

Todo

A small action item that can be completed.

Assignee

The person responsible for completing the action.

Due date

The target date for completion.

Status

The current state, usually pending or completed.

Reminder

A scheduled prompt or visual cue to revisit the action.

Beginner Quick Start

Use this first-run path in a training database or with a supervised account before handling live records.

  1. Open Todo and create one action with a clear verb and outcome.
  2. Assign it to yourself or the responsible teammate.
  3. Add a due date when timing matters.
  4. Review pending todos at the start or end of each workday.
  5. Mark completed only when the outcome is truly done.
Before using live data: confirm the module is enabled, your role has the right permissions, required master data exists, and you know the rollback or correction process for mistakes.

Standard Operating Procedures

These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.

Actor: Any permitted user

Create a useful todo

  1. Start the title with a verb such as Call, Review, Prepare, Send, or Confirm.
  2. Add due date, assignee, and short context.
  3. Avoid combining unrelated work into one todo.
  4. Save and confirm it appears in your list or widget.
Actor: Staff user

Run a daily todo review

  1. Check overdue and due-today items.
  2. Complete items that are finished and reschedule legitimate delays.
  3. Convert large or multi-person todos into Projects or Helpdesk tickets.
  4. End the day with a short list of next-day priorities.
Actor: Manager or team lead

Delegate a small action

  1. Write the action in terms of the desired result.
  2. Assign one responsible owner.
  3. Set a reasonable due date and add context.
  4. Follow up through the todo status rather than separate chat reminders only.

Industry Notes and Good Practice

  • A todo should be small enough to complete in one action or short work session.
  • If a task needs many steps, files, deadlines, and collaboration, use Projects.
  • If there is no action, use Notes instead.
  • Daily review is the habit that makes todos useful.

Controls, Data Quality, and Review Checklist

Use this checklist during onboarding, monthly review, and process audits.

  • Todo titles start with an action verb.
  • Important todos have due dates and one owner.
  • Completed items are closed promptly.
  • Old overdue items are rescheduled, escalated, or converted into larger workflows.

Related ERPat areas

Notes for reference Projects for larger work Timeline for informal discussion Helpdesk for support issues

FAQ and Troubleshooting

Should I use Todo or Projects?

Use Todo for small actions. Use Projects for coordinated work with multiple tasks or people.

Should I use Todo or Notes?

Use Todo when something must be done. Use Notes for information you want to remember.

Why am I not seeing my assigned item?

Check filters, status, due date, permissions, and whether the module is enabled.

What is a good todo title?

Use a result-oriented action such as Send revised invoice to ABC Corp.

Report a content problem