As it stands, CentriQS automatically calculates the percentage complete only based upon time or you can show the column which will show the percentage complete. This is based solely on time that has elapsed and in no way indicates the physical work done. In other words it just like a watch.

Now, let's assume that you have allocated 10 days on a task and 6 days have elapsed. this would translate to 60% which could erroneously imply, to the owner of the task (not the assignee), that progress on the task is 60 %. However, the assignee may have done literaly nothing at 60 % time elapsed. If, at 60 % time elapsed, the assignee had progressed to 90 %, that would indicate couple of things amongst which could be: (i) the assignee is extremely efficient, (ii) the estimated time was too long, (iii) the task was too easy, etc. The first one (i) would ordinarily indicate high performance on the side of the assignee and the owner could consider a bonus or something.

The reverse of the argument would most probably indicate the reverse of Items (i) to etc.

Also if the owner of the task say at 60 % in accordance with CentriQS requests the assignee to brief him about the progress attained, a lot of embarrassment or excitement may occur depending whether the assignee is ahead or behind.

In summary, it is a known and established fact that time and physical performance cannot lie on the same line. That is why in a management software, you have to allow the user to indicate the physical progress and such would be compared with the time elapsed and in CentriQS case, the percentage complete.

I therefore suggest that you allow a user to input Percentage Complete manually but also keep the time tracking progress (percentage) as it is currently. This would indicate, to the task owner as well as the assignee, that either the task is or is not at risk. At the present moment, risk is only based upon time.

On the General Tab of Task, there is a parameter named On Schedule. This parameter could be ticked or left. As a new user of CentriQS, I thought that the meaning or intent of the parameter was to check if the task was on schedule. In a program, variable naming is extremely crucial in terms of making the program more user friendly.

Now, let's get into the matter.

The parameter, as it turns out, will cause the Remaining argument to be recalculated. In other words, it will cause the program to indicate the time remaining till the Due Date.

In order to keep the intent of the developers in place as well as to simplify the easy of understanding, I would suggest that the parameter be renamed to Recalculate Time Remaining. If the user wants to recalculate the remaining time, then the box would have to be ticked which will satisfy the vision of the developers.

Sometimes fields and field labels do not the give user enough information on what or how to fill in that particular field when entering data. First, I see this as a checkbox "option" when creating/editing the field in the Configurator. This would add a small "?" icon next to that field. When the user clicks the "?" next to the field, a small "notes" box would popup giving the user further details about that field.

Moreover, there could be two types of notes: One for "entering" data and one for "viewing" data. The "viewing" notes would appear if the user clicks on the column header for that field when using the Main View.

Originally, the idea came to me for use with analytics only - but after more thought, I see many uses for color text.

For example: in financial view, set conditional logic for text to display RED if Accounts Receivable is past due 30 days - or display GREEN text if balance is over a specific dollar amount (say $1,000).

Another usage method may be to add a "color" selection feature to the "filter" portion of layouts. This way, when you add a new filter to the layout, you could also set a text color for that individual filter.

For example: 2 filters for task layout:
Filter ONE: Display all tasks assigned to "John" (no color)
Filter TWO: Display all tasks scheduled for "next week". (Red)

When a Time log is added 'Actual' time will increase its value but 'Remain' will be left unchanged. You need to manually enter the remaining time you still need on a task. It would be more logical if 'Remain' would be decreased automatically and only manually adjusted when you need more time then it automatically calculated.

Example:
You have a project for constructing a building your calculation team made a Qoutation that estimates 10 days of work.

The employee's make time logs as they work on the project. The time logs will automatically decrease the 'Remaining' work time.

If this number would become negative we can see that either
- Something is wrong on this project
- The employee is not working on it fast enough
- The estimated time was incorrect.

For task sheduling/planning we could add Extra remaining time manually at any given point.
This will edit deviation as it does now.

PROCESS
1. If assigned resource is logged in or online, there should be a status and chat button.
2. If user is on line chat session can be initiated from owner or assigned resource.
3. Any such text chat will be saved as comments and will become part of task history
4. Additionally if voice chat can be initiated as well and such video or audio chat will be saved as audio or video file and will become part of task history
5. If user is offline still text message can be sent via sms gate way service, still this message will be saved in history.

BENEFITS
• Huge saving in cost and time and improvement in quick response and effectiveness of business tasks
• This feature will enable task manager as best collaborating software for companies with multiple offices connected through VPN.
• This way user will not be depended on phone calls to discuss anything about any task.
• While posting comments this will not be uncertain that the respondent is logged in or not and when response will be received.
• Any cellular or PABX call can’t be linked and saved with task history conventionally but if audio call, video call and text message is feature of task manager then such audio or video calls can be saved in files and can be linked to the task and text message can be saved as well.

PROCESS

1. Each time user makes any change a new file version should be saved
2. Original file still remains the same
3. Each version is saved with detail of user and should highlight the change to track the change
4. Once any file is debated, amended, agreed and saved then it should be approved and sealed by digital signatures.

BENEFITS

• Will save a hassle of shifting lot of files and documents among companies scattered offices for approval, authorization and archives
• A step forward to paperless office
• Quick approvals and authorizations and files always remains retrievable
• Cost and time saving