A common worry: we have a project that will run six months or a year, so we sign a contractor for that period instead of hiring. Is that risky?
On its own, no. That is the most legitimate use of contractors there is — a defined piece of work with a defined end.
The risk comes from how those months are run, not from their number. Two companies can sign the identical twelve-month agreement and end up in completely different positions.
The clean version: The project and its deliverables are defined. The contractor works their own hours, their own way, with their own equipment. Payment follows milestones or invoiced work. They have other clients. They sit outside the company’s management chain.
The risky version: Same duration, but the person works nine to six, attends the team’s daily meetings, reports to a manager, uses a company laptop and internal systems, invoices the same amount every month, and has no other clients. Here the word “contractor” in the contract carries no weight, because the picture describes an employee.
Duration matters in two indirect ways. First, the longer a relationship runs, the more the other indicators tend to accumulate — being embedded in a team is hard to avoid over three years and easy to avoid over three months. Second, if a fixed-term contract is renewed again and again, the “defined project” framing stops being credible. A six-month agreement extended five times is an open-ended relationship in practice.
One thing worth separating out: some countries cap the duration of fixed-term employment contracts, after which they convert to permanent. That is a different rule and it does not apply to contractors. The two get confused often.
