From MintHCM Wiki

Name: Improvements
Tech Name: Improvements
Class Name: Improvements
Type: Standard
Template: Security_groups, Assignable, Basic
Custom Module: No
Auditable: Yes
Importable: No
Reportable: Yes
Hide module on Main Page: No

Short Description

The Improvements module facilitates performance enhancement within the workplace. It provides tools for goal-setting, skill development, and constructive feedback, fostering a conducive environment for professional growth.

  1. MintHCM - Improvements - Filters.png
  2. MintHCM - Improvements - createView.png
  3. MintHCM - Improvements - detailView.png
  4. MintHCM - Improvements - listView.png


The Improvements module in MintHCM is a space dedicated to tracking and recording enhancement initiatives within the organization. Unlike the Goals module, focused on individual employee objectives, Improvement records usually relate to a broader spectrum of organizational enhancements.

This module is designed to capture general improvements within the company, providing a flexible space adaptable to different user needs. Users can utilize it to document enhancements in processes, tools, or any area where the potential for improvement is identified. There is no particular 'correct' way to utilize this module, so users can tailor it to their needs.

The Improvements module caould be a valuable tool for monitoring and reporting on teams' enhancement efforts. Users can track the progress of improvement initiatives over time, allowing for a comprehensive view of their impact on the organization.


The Improvements module comprises several standard fields, each serving a specific purpose in capturing and organizing Improvement-related information. Here is a detailed explanation of each field:

Name The title of the improvement record.
Employee The Employee related with the improvement record. For example, it could be the person behind the idea of the improvement, or someone that is responsible for it
Description Allows users to provide some context or details related to this particular improvement. It should include some additional information that is necessary to process this improvement properly, but has no designated field. In the "Description" field you can also include any other information that seem relevant to the created record.
Assigned User The user designated to manage or handle the assigned improvement. It could also be the person in need for this particular iprovement.
Date Created The date and time when the improvement was initially created.
Date Modified The date and time when the improvement was last edited or modified.

Note: Fields marked with an asterisk are required. Saving the record without providing input to them beforehand won't be possible.


The 'Improvements' module is connected with two modules. These related modules are:

The 'Improvements' module is flexible in its associations and can be tailored to users' specific needs. Users have the freedom to establish connections with various aspects of improvement initiatives, such as the person proposing the idea or the individual responsible for its implementation.

Similarly, the relationship with the 'Conclusions' module is not rigid but adaptable. Users can connect Conclusions records with Improvements records based on their relevance or correlation. For instance, if a conclusion suggests a need for more efficient meetings, users can link this conclusion with an Improvement record focused on making meetings more productive.

Custom Actions


Related Processes

Related Process Steps

Related Features

Affected by


Related Integrations



LaftTypeRightShort DescriptionRelationship
Usersone-to-manyImprovementsSpecific Sugar user can modify many account records, but specific account record last modification was performed by specific user.Relationship: Users - Improvements
Usersone-to-manyImprovementsSpecific Sugar user can create many account records, but specific account record can be created by only one user.Relationship: Users - Improvements
Usersone-to-manyImprovementsSpecific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.Relationship: Users - Improvements

Mentioned in other articles

Technical Description

Dev Notes