<p>Characteristics of a "project", as per the <a href="https://www.pmi.org/about/learn-about-pmi/what-is-project-management" rel="nofollow noreferrer">Project Management Institute</a>, are that it is temporary and unique (ie. non-routine).</p>

<p>For a person employed to work on a project, the temporary nature of the work is likely to be a source of additional cost and risk, as compared with a person in a permanent job. This is because, as the project comes towards its end, the person is likely to <em>have to</em> find another job.  That involves both the <strong>transaction costs</strong> of finding a job (searching, assessing whether jobs are suitable, negotiation, etc., implying time and effort if not monetary costs) and the <strong>risk</strong> of not finding a suitable job when needed and therefore experiencing a loss of income. These factors suggest that to recruit to a project role will require somewhat higher pay than to recruit to a permanent job with a similar skill level. </p>

<p>An exception to the above is where a current staff member in a permanent job is seconded to work on a project. Provided they can be sure that at the end of the project they can return to their original job, they will not be subject to the sort of risk described above. On the other hand if a current staff member is to be asked to work on a project while also keeping their regular work going, they may decline unless offered higher pay (for reasons of workload, not risk).   </p>

<p>A further issue is how pay for project work might be structured. Suppose A is working on a project which is 90% complete. The employer will want A to stay and complete the project.  But A knows that staying until the end of the project will increase the risk that they will find themselves without a job. So they will be tempted to apply for other jobs before the project is complete. Hence there is a risk for the employer, ie that the departure of a key person will mean that completion of the project becomes problematic.  To address this, an employer might consider a pay structure consisting of a regular monthly salary plus a bonus payable on successful completion of the project.</p>

<p>But that in turn raises the issue of <strong>asymmetric information</strong>. Because of the non-routine nature of project work, it may be that only those working on the project really know how near (or far) the project is from successful completion. This is especially likely where the output of a project is not very visible or tangible, an ICT system implementation for example. So even if the project is only 90% complete, and A knows that, there is a risk for the employer that A will leave to take another job while also persuading management that the project is complete and receiving the bonus.   </p>

CC BY-SA 3.0
2017-08-21T22:42:48.843Z
2017-08-21T22:42:48.843Z
Adam Bailey
<p>Getting qualified workforce for temporary projects can be difficult. If found from within the organisation, they may have to abstain from their regular work, and this may create additional complications to their worklife. Given that the right people may be difficult to find, they may have to be paid higher than if the same post would be a year-round job (if the quality of work is the same).</p>

<p>Many factors might need to be taken into account by an employer seeking staff for such projects.  What economic factors are relevant here?</p>

CC BY-SA 3.0
2017-08-19T15:11:34.187Z
Interesting question.  But while economic analysis may be able to contribute to an answer, the question is I suggest more suitable for The Workplace SE.
Adam Bailey
CC BY-SA 3.0
2017-08-19T20:25:37.763Z
Thanks for the recommendation. :) I posted in on Workplace SE too to see if there's a response.
puslet88
CC BY-SA 3.0
2017-08-19T20:32:47.597Z
At https://workplace.stackexchange.com/questions/97463/how-much-additional-pay-should-be-given-for-temporary-project-work
Henry
CC BY-SA 3.0
2017-08-19T21:34:49.487Z
I see that The Workplace SE has put the question on hold as too broad.  I've taken the liberty of an extensive edit on this site with the aim of producing a question that is on-topic for Economics SE.  Please feel free to reverse any of my edit if you judge it inappropriate.
Adam Bailey
CC BY-SA 3.0
2017-08-20T10:52:14.720Z
Thanks a lot for the edit! Much clearer I hope indeed! Looking forward to ideas on this. :)
puslet88
<labor-economics><wages><labor-cost>
What economic factors should be considered in attracting suitable staff and determining pay for temporary project work?
puslet88
# What economic factors should be considered in attracting suitable staff and determining pay for temporary project work?

(Asked by: username_0 on 2017-08-19)

Getting qualified workforce for temporary projects can be difficult. If found from within the organisation, they may have to abstain from their regular work, and this may create additional complications to their worklife. Given that the right people may be difficult to find, they may have to be paid higher than if the same post would be a year-round job (if the quality of work is the same).

Many factors might need to be taken into account by an employer seeking staff for such projects. What economic factors are relevant here?

**Tags:** labor-economics, wages, labor-cost
> **Comments:**
> **username_1**: Interesting question.  But while economic analysis may be able to contribute to an answer, the question is I suggest more suitable for The Workplace SE.  
> **username_0**: Thanks for the recommendation. :) I posted in on Workplace SE too to see if there's a response.  
> **username_2**: At https://workplace.stackexchange.com/questions/97463/how-much-additional-pay-should-be-given-for-temporary-project-work  
> **username_1**: I see that The Workplace SE has put the question on hold as too broad.  I've taken the liberty of an extensive edit on this site with the aim of producing a question that is on-topic for Economics SE.  Please feel free to reverse any of my edit if you judge it inappropriate.  
> **username_0**: Thanks a lot for the edit! Much clearer I hope indeed! Looking forward to ideas on this. :)  

---

## 1 answers

### Answer by username_1 on 2017-08-21. Score: 1

Characteristics of a "project", as per the [Project Management Institute](https://www.pmi.org/about/learn-about-pmi/what-is-project-management), are that it is temporary and unique (ie. non-routine).

For a person employed to work on a project, the temporary nature of the work is likely to be a source of additional cost and risk, as compared with a person in a permanent job. This is because, as the project comes towards its end, the person is likely to *have to* find another job. That involves both the **transaction costs** of finding a job (searching, assessing whether jobs are suitable, negotiation, etc., implying time and effort if not monetary costs) and the **risk** of not finding a suitable job when needed and therefore experiencing a loss of income. These factors suggest that to recruit to a project role will require somewhat higher pay than to recruit to a permanent job with a similar skill level.

An exception to the above is where a current staff member in a permanent job is seconded to work on a project. Provided they can be sure that at the end of the project they can return to their original job, they will not be subject to the sort of risk described above. On the other hand if a current staff member is to be asked to work on a project while also keeping their regular work going, they may decline unless offered higher pay (for reasons of workload, not risk).

A further issue is how pay for project work might be structured. Suppose A is working on a project which is 90% complete. The employer will want A to stay and complete the project. But A knows that staying until the end of the project will increase the risk that they will find themselves without a job. So they will be tempted to apply for other jobs before the project is complete. Hence there is a risk for the employer, ie that the departure of a key person will mean that completion of the project becomes problematic. To address this, an employer might consider a pay structure consisting of a regular monthly salary plus a bonus payable on successful completion of the project.

But that in turn raises the issue of **asymmetric information**. Because of the non-routine nature of project work, it may be that only those working on the project really know how near (or far) the project is from successful completion. This is especially likely where the output of a project is not very visible or tangible, an ICT system implementation for example. So even if the project is only 90% complete, and A knows that, there is a risk for the employer that A will leave to take another job while also persuading management that the project is complete and receiving the bonus.


---

