5 ms·

why do company need all remote people on payroll, instead they can keep them as contractors

by senthilnayagam 14y ago

daliusd 14y ago
This way you lose control what they are working on.
- Luyt 14y ago
  No, that's not true. Communication is all. For example, you can have the repository send off commit messages to every team member, so they can see what everyone is working on.
  - deleted 14y ago
    [deleted]
  - PakG1 14y ago
    I don't think you understand. You really do lose control. Look at the legal implications. http://www.entrepreneur.com/article/177992 http://www.entrepreneur.com/article/177992 The most important paragraph: So what are the differences between an employee and an independent contractor? There are a number of factors that determine which category a worker falls into. The most important of these is called the right of control. Does the employer have the right to exercise control over the worker? Basically, this means that the employer has the right to hire and fire the worker. But it also means the employer has the right to dictate both the means and the manner in which the worker performs the job. If this is the case, then the relationship is that of an employer and an employee. However, if the employer can control only the final results of the work, then the parties have an employer-independent contractor relationship.
bobwaycott 14y ago
There is the matter of work control--i.e., the company, by virtue of having each remote worker on the payroll, exercises an employer-employee relationship, as opposed to a client-consultant relationship. However, the company further benefits because the remote workers are/become experts in the software--they are going to know the code better than constantly bringing in contractors--and may see measurable quality improvements by having the same people working consistently on the codebase. I'd imagine companies also appreciate knowing they don't have to worry about conflicting schedules and the like, which can arise with frequency among people who are contracting full-time. And, just maybe, the company actually values the remote workers enough that they want to make sure they keep them around with a good salary, generous time off, and an intrinsic work relationship that shows value to their workers' personal time and needs.

why do company need all remote people on payroll, instead they can keep them as contractors

daliusd 14y ago

This way you lose control what they are working on.

Luyt 14y ago
No, that's not true. Communication is all. For example, you can have the repository send off commit messages to every team member, so they can see what everyone is working on.
- deleted 14y ago
  [deleted]
- PakG1 14y ago
  I don't think you understand. You really do lose control. Look at the legal implications. http://www.entrepreneur.com/article/177992 http://www.entrepreneur.com/article/177992 The most important paragraph: So what are the differences between an employee and an independent contractor? There are a number of factors that determine which category a worker falls into. The most important of these is called the right of control. Does the employer have the right to exercise control over the worker? Basically, this means that the employer has the right to hire and fire the worker. But it also means the employer has the right to dictate both the means and the manner in which the worker performs the job. If this is the case, then the relationship is that of an employer and an employee. However, if the employer can control only the final results of the work, then the parties have an employer-independent contractor relationship.

bobwaycott 14y ago

There is the matter of work control--i.e., the company, by virtue of having each remote worker on the payroll, exercises an employer-employee relationship, as opposed to a client-consultant relationship. However, the company further benefits because the remote workers are/become experts in the software--they are going to know the code better than constantly bringing in contractors--and may see measurable quality improvements by having the same people working consistently on the codebase. I'd imagine companies also appreciate knowing they don't have to worry about conflicting schedules and the like, which can arise with frequency among people who are contracting full-time. And, just maybe, the company actually values the remote workers enough that they want to make sure they keep them around with a good salary, generous time off, and an intrinsic work relationship that shows value to their workers' personal time and needs.