Patent Application
20100106541
The present disclosure describes embodiments generally related to managing employee compensation information. More particularly, the present disclosure relates to determining the readiness of a template for communicating compensation changes to an employee.
Many of the same types of tasks within an organization are repeated over the course of time by a number of employees in some way or another. With respect to the task of creating similar type documents, an organization may wish to standardize the documents in order to create a consistent product. In order to minimize the redundancy involved with generating the same letters and forms, organizations often create templates that can be used as a starting point for letters, forms, etc., that are used frequently within the organization. Therefore, instead of requiring each employee to generate a letter or form from scratch, the employees can begin with a previously created template and fill in the necessary information as needed. In this manner, much time can be saved within a corporation by allowing employees to access templates to complete the task of creating standard documents.
The present disclosure describes systems and methods for managing templates. In one embodiment, among others, a method comprises applying information into a proposed template, wherein the information is received for the purpose of filling blank portions of the proposed template. The method also comprises performing a readiness analysis on the proposed template to determine whether or not the proposed template is ready to be used by one or more users. The readiness analysis is based on the application of the information into the proposed template.
Other features, advantages, and implementations of the present disclosure, not expressly disclosed herein, will be apparent to one of ordinary skill in the art upon examination of the following detailed description and accompanying drawings. It is intended that such implied implementations of the present disclosure be included herein.
The components of the following figures are illustrated to emphasize the general principles of the present disclosure. Reference characters designating corresponding components are repeated as necessary throughout the figures for the sake of consistency and clarity.
Organizations often create document templates that can be used by a number of employees to generate specific standard documents. The purpose of templates is to reduce the redundancy of work that has already been done by someone else in the organization. Instead, employees can access a particular template from the organization's network and fill in the pertinent information for the specific situation.
However, it is known that the use of some templates do not always produce acceptable results. For instance, some templates include information that is not necessary for the particular situation in which the template is being used. Occasionally, a template will apply to one group of people but not to another. Another problem that often results from the use of templates is poor grammar, such as the disagreement between nouns, which are entered into the template, and the corresponding verbs. These and other problems are common when templates are used.
To overcome many of these problems, a person using a template often needs to check the resulting letter or form to see if any of these common problems have occurred. Consequently, the person can lose confidence in the effectiveness of the template. Also, the person may be required to spend valuable time checking how the entered information is handled in the template and if any of the above problems or other problems arise. If problems are detected, the person usually must edit the document to correct the discovered errors. Otherwise, if a letter or form that is created by a template inherently includes errors, then the letter or form can give a negative impression of the organization and may not be taken seriously by people reading the improperly formed letters or forms.
According to the embodiments described in the present disclosure, templates can be created and then automatically analyzed to detect common errors that occur with respect to many templates. After the template is checked for readiness, the systems and methods described herein can avow that the template is ready for use. Once avowed, the template can be accessed and used by the employees as needed. Furthermore, the employees can use the templates with the confidence that the template will not produce an unacceptable product, which can be common with other unchecked templates.
In particular, the embodiments of the present disclosure relate to systems and method for managing the compensation information for the employees of an organization. When a compensation change is planned to go into effect for an employee, any number of managers, administrators, etc., may get involved to determine the details of the compensation change. Some changes may need to be sent up the chain of hierarchy for approval. With respect to one example, if an employee works for an organization for a certain number of years, the organization may have systems in place to reward the employee by paying the employee a bonus and/or increasing the employee's pay. When these or other types of changes are planned, organizations usually communicate the changes to the employee.
The compensation management systems described herein can be configured, for example, to produce a communication letter or statement that is intended to be given to an employee when a change in compensation, e.g., raise, bonus, stock options, etc., is going into effect. The communication is usually given to the employee for the employee's own information and records. Each organization may contain their own wording for these types of letters to communicate information to the employees as the management deems to be appropriate.
It should be noted, however, that although the embodiments described herein pertain particularly to communicating compensation changes to an employee, these embodiments can also pertain to the creation of any type of document, communication, statement, letter, etc., from a template. A non-limiting list of other applications may include letters regarding other types of personnel actions, confirmation of a change in the employee's address or contact information, confirmation of a change of a client's contact information, information about a client's account, a letter communicating one or more pieces of information to a client, etc.
In the embodiment of
Memory device 14 can also store program code that enables processing device 12 to execute procedures related to the management of compensation information for one or more employees. The embodiments of employee compensation module 22 described in the present disclosure can be implemented in hardware, software, firmware, or a combination thereof. When implemented in software or firmware, employee compensation module 22 is stored in memory device 14, as illustrated, and executed by processing device 12. Alternatively, when implemented in hardware, an employee compensation system can be implemented in processing device 12 using discrete logic circuitry, an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), other suitable logic circuit, or any combination thereof.
Employee compensation module 22 may include similar logic stored on a number of different systems in communication over the network and may be capable of communicating with each other via their respective network interfaces, such as network interface 18. In some embodiments, certain employees, such as compensation administrators, can include authorization to perform certain functions of employee compensation module 22 that are not authorized to other employees. In this respect, employee compensation module 22 can be stored partially or fully in memory device 14 in each respective employee compensation managing system 10.
In addition, other software, programs, or computer code including executable logical instructions as described herein, can be embodied in computer-readable media for execution by any suitable processing device, such as processing device 12. The computer-readable media as described herein can include one or more suitable physical media components that can store the software, programs, or computer code for a measurable length of time.
Input/output devices 16 may include input mechanisms such as keyboards, keypads, cursor control devices, or other data entry devices. The input mechanisms enable a user to enter information for creating templates, information regarding compensation plans, information to be added to a template, requests for creating a statement, etc. The applicable entries may depend on the employee's roles in the organization. Input/output devices 16 also include output mechanisms, such as computer monitors, audio output devices, printers, or other peripheral devices for communicating information to the user.
One or more people of a group of users, such as compensation administrators in charge of handling compensation matters for employees of an organization, can use template creating module 30 for creating one or more templates to be used within the organization. Template creating module 30 allows the users to enter text that is intended to be included in a particular template. Templates can be entered using any suitable format, such as, for example, portable document format (“PDF”), rich text format (“RTF”), etc. Also, the templates can be defined using any suitable editor that supports the particular format.
Also, template creating module 30 allows the users to enter conditional text that is included in the statement or letter when certain conditions are met. In this way, only the applicable phrases, sentences, paragraphs, etc. will be entered in the statement or letter. Furthermore, template creating module 30 allows the users to enter locations in the statement or letter where variable information is inserted. For example, the variable information may include the employee's name, employee's contact information, employee's job, current date, effective date of compensation change, prior salary, new salary, bonus amount, stock option amount, or other compensation type information. When the templates are created with template creating module 30, templates 32 are stored for later editing or use. Before being used, however, templates 32 can be applied to statement set-up module 34 for validation of the adequacy of templates 32.
The users can then enter one or more compensation plans to statement set-up module 34. The compensation plans may include various hypothetical conditions of compensation changes. In other embodiments, the compensation plans may represent actual compensation changes proposed for one or more employees. With the entered compensation plans, statement set-up module 34 applies the compensation plans to the appropriate template 32 and forms the statement, letter, form, etc., resulting in a combination of the template and the information of the compensation plan.
When the statement is set-up by statement set-up module 34, template readiness analyzing module 36 is configured to analyze the resulting statement to see if the template properly handled the compensation information. If it is determined that the statement meets certain conditions that are checked by template readiness analyzing module 36, a message is sent from template readiness analyzing module 36 to the user, who entered the compensation plan, avowing or indicating that the template is ready. Template readiness analyzing module 36 can be used to check for the most common errors or oversights that are found in templates. By checking for these errors before validation of the template, the errors can be corrected prior to use by other users within the organization.
One example of a common error in templates includes the use of an incorrect template format. For example, if the template is created in one format and is later renamed or edited using another format, then a corrupted output can occur. Another example of a possible error is the inclusion of phrases, sentences, or paragraphs of the letter or statement that are not applicable to the employee's situation. For example, if an employee is due to receive a salary increase but not a year-end bonus, then it may be inappropriate to include a sentence or paragraph stating that the employee's bonus is $0. Generally, conditional logic is inserted in the template to handle such a scenario. In this case, template readiness analyzing module 36 may be used to validate the conditional logic in order to correct the syntax as needed and to avoid the conditions like the one mentioned above.
Template readiness analyzing module 36 is also capable of detecting other errors, such as errors in syntax regarding conditional logic, errors in grammar, etc. In response to discovering these and/or other errors, template readiness analyzing module 36 can report the errors to the person who created the template to avoid usage of a template that would require much re-work by each user thereafter. If the template does not meet all the criteria, then an error message is sent to indicate that the template is not ready and must be changed. In some embodiments, template readiness analyzing module 36 can provide helpful suggestions explaining how the template can fixed.
As illustrated in
In response to an indication that the template is not ready, the user can access the template creating module 30 to make appropriate modifications to the template to overcome the errors that were reported by template readiness analyzing module 36. After modifications are made, the user can again run compensation plans through statement set-up module 34 for creating the statement from the combination of the compensation information and the modified template. Again, template readiness analyzing module 36 checks the statement for the particular list of errors and determines whether the template is ready for use or if further modifications are needed.
When templates 32 are eventually avowed by template readiness analyzing module 36 as being ready for use, another group of users, such as managers, line managers, or other employees, can use templates 32 as needed. A user of this group can enter a request to access the statement that was created from the compensation information and corresponding template in response to the compensation administrator entering and verifying the templates and statements. In other embodiments, the line manager or other user can enter a request to access a selected template and enter new compensation information to be applied to the template. This information is applied to statement set-up module 34, which sets up the statement or letter according to the design of the template. Once the statement is generated, statement set-up module 34 sends a copy to the user. This statement can then be printed by the user or communicated to the specific employee as necessary.
Near the bottom of user interface 46 is a table allowing the user to select or create templates. The compensation administrator can use any of multiple templates to create a Statement Group, which can give the user, e.g., manager, flexibility to use different templates for different employees if needed. In some embodiments, the table includes a readiness column, allowing the user to initiate a readiness check on a selected template when desired. In other embodiments, the readiness check can be performed automatically.
In the embodiment of
As indicated in block 64, compensation plans are received. The compensation plans can be received, for example, from a compensation administrator or any other qualified user. As indicated in block 66, the compensation plans are applied to the template, which is created with respect to block 62 as mentioned above. In some embodiments, the compensation plans may be hypothetical plans for the purpose of checking the operability of the template under certain conditions. After applying the compensation plans to the template, a template readiness analysis is performed as indicated in block 68. Particularly, the template readiness analysis is performed on the template with the compensation plans applied thereto to check the readiness of the template.
As indicated in decision block 70, it is determined whether or not the template is acceptable. The acceptable may be based on the template readiness analysis mentioned with respect to block 68. If it is determined that the template is not acceptable, then the method proceeds to block 72. According to block 72, the user is enabled to modify the template. Based on errors detected, suggestions can be presented to the user to allow the user to make appropriate changes to fix the template. After further modification by the user, the flow returns back to block 66 where the compensation plans are applied to the template again. The processes are repeated until it is determine in decision block 70 that the template is acceptable. At this point, the method proceeds to block 74, which indicates that it is avowed that the template is ready for use.
According to the embodiment of
It should be understood that the steps, processes, or operations described herein may represent any module or code sequence that can be implemented in software or firmware. In this regard, these modules and code sequences can include commands or instructions for executing specific logical steps, processes, or operations within physical components. It should further be understood that one or more of the steps, processes, and/or operations described herein may be executed substantially simultaneously or in a different order than explicitly described, as would be understood by one of ordinary skill in the art.
The embodiments described herein represent a number of implementations and examples and are not intended to necessarily limit the present disclosure to any specific embodiments. Instead, various modifications can be made to these embodiments as would be understood by one of ordinary skill in the art. Any such modifications are intended to be included within the spirit and scope of the present disclosure and protected by the following claims.
