Monday - Friday 9AM – 6PM EST
An open-ended hire will outlast the conversation that created it, so the terms need to work years from now. Answer a few questions and the document is ready to review.
Choose the state or form type you need to start.
Answer a few simple questions to customize your form.
Download or print your custom document in PDF or Word.
A permanent employment contract hires somebody on an open-ended basis, with no agreed finish date. It covers the role, the pay, and the terms both sides expect to live with indefinitely.
Permanent describes the shape of the arrangement rather than a guarantee. How employment can end depends on your state and on what the document says, so read both together.
The real difference from short engagements is time. Terms written for a nine-month project rarely survive a nine-year career, and the document has to anticipate that.
Progression, reviews, accruing benefits, and changing policies all arrive later. None of them matter on day one, and all of them matter eventually.
Both sides also read the document differently over time. The employer looks for obligations, while the employee looks for what somebody promised.
Team size shapes the document as well. One hire needs less than a growing team on shared policies. Both still rely on terms you can update cleanly.
Most open-ended hires start with a trial stretch. Write it properly rather than mentioning it in passing.
State how long the initial period runs and what it assesses. A period nobody reviews is decoration rather than a probation.
Say whether you may extend the period, by how long, and who decides. Also say how the employee finds out.
Set clear check-in points rather than leaving everything to the final week. Feedback delivered once, at the end, helps nobody. Two short conversations beat one difficult one.
Name what shifts when the period ends: notice, benefits eligibility, or access to certain schemes. Silence here makes confirmation feel like nothing happened.
Say what notice applies while the period runs, since it often differs from the standard term. Then say when the longer notice begins.
Confirm which terms apply throughout. Pay, hours, and conduct rules normally run from day one regardless.
A permanent employment contract has to describe how things grow, not only where they start.
Say when reviews happen and who conducts them. Then make clear whether a review guarantees an increase, because most do not. Record the outcome in writing either way.
Describe how someone moves up, and what changes when they do. Vague progression promises cause more resentment than no promise at all. Name who owns that conversation.
Set out how you calculate variable pay and when it pays. Also say what happens when someone leaves partway through a period.
State how paid leave builds, whether it carries into the next year, and what happens to unused days on departure.
Name when the employee may join pension, health, or insurance schemes. Eligibility dates catch people out more often than contribution rates.
Where benefits improve with tenure, list the milestones. People forget long-service entitlements precisely because they arrive years later.
Long arrangements need a clean way to evolve. Otherwise the contract and reality drift apart quietly.
Name the handbook and policies the employee must follow. Then say whether they form part of the contract or sit alongside it, because that distinction matters later. Attach a list rather than relying on memory.
Explain how you communicate changes and when they take effect. Policies updated silently rarely bind anybody.
Set out how the contract itself changes: normally a written amendment signed by both sides. Editing an old file is not a variation.
Commit to discussing material changes before making them. Some changes also need consent, so confirm your position before assuming otherwise.
Say where the employee works and what happens if that changes. Remote arrangements agreed informally cause trouble years later.
Jobs shift over the years. A clause acknowledging reasonable changes to duties keeps the role workable without rewriting the contract annually.
The longer somebody stays, the more they know. So covenants deserve more thought here than on a short engagement.
Define what stays confidential and for how long after departure. Perpetual obligations on ordinary information rarely survive scrutiny, so separate genuine trade secrets from everyday know-how.
Say who owns work created during employment. Then carve out anything the employee brings with them or builds independently on their own time.
Where you restrict approaching clients or colleagues, keep the scope and duration proportionate to the role.
Enforceability differs considerably by state, and several have narrowed it. So confirm your position locally rather than copying wording from another jurisdiction. Ask whether a narrower confidentiality term would achieve the same protection.
A covenant written for a junior hire may not suit them as a director. Revisit these terms at the point of promotion rather than years later.
The administrative end of a long arrangement decides how smoothly it eventually closes.
State what notice each party gives. Keep the two consistent with how employment can end in your state. A fixed notice period sits awkwardly beside some arrangements.
Describe the departure process: outstanding pay, unused leave, equipment return, and knowledge transfer. Long-serving people carry more of all four than anyone expects.
File the signed contract with the employee’s records, together with every amendment. A permanent employment contract without its amendments tells only part of the story.
Revisit the terms when the role, the pay structure, or the law changes. Then sign the update rather than noting it informally.
Both parties sign and date the same version before work begins, and each keeps a copy. Electronic signatures handle this well.
Terms written carelessly on day one attract careful reading years later. Build a permanent employment contract template now, while nothing is in dispute.
One place to build, sign, and manage documents.
