Understanding the “Collect Progress” feature in ERPNext – Purpose and Default Workflow

ERPNext Project Management
, ,
1

I am trying to understand the exact purpose and default behavior of the “Collect Progress” feature in the ERPNext Project module.

From my testing, my understanding is that Collect Progress is primarily a reminder mechanism for the project team to provide regular project updates. It does not automatically calculate the actual project progress and send that calculated progress to the customer.

I would like to confirm whether my understanding is correct, particularly regarding the term “stakeholders” used in the documentation. Does “stakeholders” refer to:

  • Customers/external stakeholders, or

  • Internal team members/users working on the project?

My understanding of the default lifecycle

Is the following flow correct for the Collect Progress feature?

Project configuration
↓
Scheduler checks project
↓
ERPNext creates a Project Update record
↓
ERPNext emails Project Users asking for an update
↓
Users reply to that email
↓
Frappe stores the replies as Communications
↓
ERPNext reads those replies
↓
Replies are added to the Project Update
↓
Daily scheduler generates Project Summary
↓
Summary is emailed to Project Users

I would particularly like confirmation on these points:

  1. Is Collect Progress essentially intended for internal project progress collection/reminders?

  2. Does it automatically calculate project progress based on Tasks, completion percentage, timesheets, etc., or does it depend on users manually providing their status?

  3. Does the default feature send the progress summary to the Customer, or is it sent to the Project Users?

  4. Is the above lifecycle the default behavior of Collect Progress in ERPNext, without any customizations?

I would appreciate clarification from someone familiar with the Project module regarding the intended use and default behavior of this feature.

2

Try this.