Projects

End-user documentation

Projects

Project management for projects, tasks, milestones, gantt views, timesheets, files, comments, members, settings, statuses, and widgets.

Purpose and What Problem This Solves

The Projects module turns work into assigned tasks, milestones, deadlines, files, comments, and time entries. It gives teams a shared plan and helps managers see what is late, blocked, or ready for review.

Who normally uses this module

What You Can Do Here

• Create projects with members, deadlines, milestones, files, and comments.
• Assign tasks, checklist items, priorities, labels, and statuses.
• Track time through project timesheets.
• Review schedules through gantt and project dashboards.
• Use project settings to control statuses, custom fields, and team workflows.

Core Concepts and Terms

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

Beginner Quick Start

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

1. Create the project with a clear objective, owner, dates, and members.
2. Add milestones that match real phases or deliverables.
3. Create tasks with assignees, due dates, priorities, and acceptance notes.
4. Have team members update status and log time regularly.
5. Review gantt, task lists, comments, and timesheets in the weekly project routine.

Standard Operating Procedures

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

Start a new project

1. Define goal, success criteria, owner, team, stakeholders, due dates, and constraints.
2. Create the project record and invite the correct members.
3. Add milestones, initial tasks, files, and communication expectations.
4. Review the plan with the team before execution begins.

Run a weekly project review

1. Check overdue tasks, blocked tasks, upcoming milestones, and recent comments.
2. Update priorities and due dates based on real progress.
3. Confirm owners for next actions and risks.
4. Share a concise status update with stakeholders.

Close a project

1. Confirm all deliverables are accepted or documented as out of scope.
2. Close or archive remaining tasks and collect final files.
3. Review timesheets and final notes.
4. Record lessons learned and mark the project complete.

Industry Notes and Good Practice

• A task without an owner and due date is a reminder, not a managed commitment.
• Milestones should describe outcomes, not just calendar dates.
• Use comments for decisions and context that future teammates need to understand.
• Time tracking is most accurate when entered daily or shortly after work is completed.

Controls, Data Quality, and Review Checklist

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

• Every active project has an owner, members, dates, and clear status.
• Every active task has an assignee, due date, and expected outcome.
• Overdue and blocked tasks are reviewed regularly.
• Project files and final decisions are stored in the project, not only in chat.

Related ERPat areas

FAQ and Troubleshooting

Should I use Projects or Todo?

Use Projects for coordinated work with multiple tasks, members, dates, files, or reporting. Use Todo for simple personal actions.

Why does the gantt look wrong?

Check task start dates, due dates, dependencies if used, and milestone dates.

Can clients see project data?

Only if customer/client visibility and permissions are configured for that project workflow.

What should beginners update daily?

Task status, comments for blockers, and timesheet entries if time tracking is required.

ERPat Projects user guide. This static HTML page is documentation-only and does not change module routing, permissions, or runtime behavior.