Applicant Tracking System Contract and Renewal Checklist: Terms to Read Before You Sign

Use this applicant tracking system contract and renewal checklist before you sign or renew: confirm the real price and any increase cap, the auto-renewal and notice dates, who owns your data and how you export it, security and data protection terms, service levels, and how you exit. This is general information, not legal advice.

Why the contract matters more than the demo

A demo shows the best day of a product. The contract shows the worst day. It decides what you pay next year, whether you can leave, what happens to your candidates' data, and what the vendor owes you if the system goes down in the middle of a hiring push. Most small teams read the pricing page carefully and the contract barely at all, then discover a notice period or a data clause when they try to leave.

This checklist is built for small and mid-size hiring teams, where the person signing is often a founder, an HR lead or an office manager rather than a procurement department. It lists the terms worth reading, what good and risky wording looks like in plain language, and what to ask for. It is not legal advice. Contract law, data protection rules and employment rules differ by country, and a contract you sign may be governed by a country other than yours, so check local law and, for anything large or unusual, ask a lawyer to read it. For the buying steps that come before this, see /applicant-tracking-system and /compare.

Read the price terms, not just the price

A monthly price on a web page is a starting point. The contract tells you what is actually committed.

Check whether the price is per seat, per active job, per candidate, or flat, and what counts as a seat. Check whether the price you were quoted applies for the first term only. Look for the renewal price, and for a cap on increases, such as "no more than a stated percentage a year". If there is no cap, the vendor can raise the price at renewal by any amount, and you will find out when the invoice arrives or, worse, after the notice period has passed.

Look for extra charges. Common ones are onboarding or setup fees, charges for extra users, charges for extra storage or extra jobs, paid support tiers, paid API access, and fees for exports. Ask which features in the demo sit in a higher plan. Ask what happens to the price if your team shrinks, because some contracts commit you to a minimum number of seats. Finally, check the currency, tax treatment and payment terms. If you pay annually in advance, ask whether any part is refundable. Our own pricing is on /pricing, and every vendor should be able to give you a similar page or a written quote.

Auto-renewal, notice dates and term length

The single most expensive sentence in many software contracts is the renewal clause. It usually says the agreement renews for another full term unless you give written notice a set number of days before the end.

Find four facts and put them in a calendar the day you sign: the start date, the end date, the notice deadline, and the renewal term length. If the term is annual and notice is 60 or 90 days, the deadline falls in the second or third month before you expect it. Set the reminder for two weeks earlier than the deadline.

Ask about how notice must be given. Some contracts require a letter or an email to a named address, not a click in the product. Ask whether a cancellation in the admin screen counts. Ask what happens if you reduce seats at renewal, and whether you may switch to a monthly plan after the first term. Ask for a renewal reminder email in writing, even if the contract does not require one. If you are on a monthly plan, check that it really is monthly and that the price is not different from the annual one without telling you. Longer terms are not bad, and discounts for committing are common, but treat a multi-year term as a loan: you gain a lower price and lose the freedom to leave. If your team is still learning what it needs, an annual term is usually the better trade.

Data ownership, export and what you can take with you

Candidate data is the main asset in an ATS, and it is data about people. The contract should say that it is yours, that the vendor processes it only for your purposes, and that you can take it out.

Read for these points. Who owns the data you upload and the data the system generates, such as scores, notes and stage history? Can you export it during the term, in a standard format such as CSV, and is that included in your plan? Does the export include notes, feedback, CVs and attachments, email history and signed documents, or only a candidate list? Is there a fee for export or for a final export on exit? How long after cancellation can you still download it, and when does the vendor delete it?

Test this before signing, not after. Ask for a sample export during the trial and open it. A contract that promises export, backed by a product that exports only names and emails, is worse than one that is plain about its limits. Also check whether the vendor may use your candidate data to train models or for its own analytics, and whether you may opt out. If the system includes AI scoring, ask whether your candidates' CVs are used beyond your own account. Rules on automated decisions and training on personal data differ by country, so check local law.

Security, data protection and where data lives

Because you hold personal data, you are normally responsible for how your vendor handles it, even though the vendor does the processing. A good contract makes that relationship explicit.

Look for a data processing agreement or equivalent terms. It should say what data is processed, for what purpose, for how long, and what happens at the end. Ask where data is stored and whether that location matters for your obligations. Ask whether the vendor uses subprocessors, and whether it will tell you before adding one. Ask how a breach is reported, and how fast. Ask which security measures are committed in writing, such as encryption in transit and at rest, access controls, backups and audit logs, and whether you can see who changed what.

You do not need to be a security expert. You need the commitments in writing and a named contact. If the vendor says it holds a security certification, ask to see the current report or certificate, and do not rely on a logo. For small teams, one extra step is worth doing: ask what your own users can do. Can you control who sees salary data, can you remove a leaver quickly, and can you see an audit trail? Those features protect you more often than any certificate does. Data protection law varies by country, so confirm what applies to your candidates and where they live.

Service levels, support and what happens when it breaks

A service level agreement states how available the product will be and what you receive if it is not. Many small-business plans have none, and that is fine if you know it. What is not fine is assuming one exists.

Ask for the uptime commitment, how it is measured, and the remedy for missing it. Remedies are usually small credits, not compensation, so treat them as a signal of seriousness rather than protection. Ask where the vendor publishes status and incidents. Ask about support: hours, channels, response targets and which plans include them. A hiring tool that goes down on the morning of ten interviews hurts differently from one that goes down on a quiet Saturday.

Ask about backups and recovery. How often is data backed up, and how long would restoring take? Ask about planned maintenance and notice. Ask about product change: can the vendor remove a feature you rely on during your term, and what notice must it give? That last question matters for integrations. If you depend on a connection to your calendar, email or HR system, ask for a written statement of what is included today, because a roadmap promise is not a contract term. Our integrations guide at /blog/applicant-tracking-system-integrations-to-require-before-you-buy lists the connections worth confirming.

Exit terms: how you leave, and what it costs

Everyone reads how they get in. Few read how they get out. The exit clauses decide whether leaving is an inconvenience or a project.

Look for termination rights. Can you end the contract early, and if so, with what notice and what refund, if any? Can you end it for cause, such as a serious outage or breach, without paying the rest of the term? Can the vendor end it, and on what notice? What happens on cancellation: do you keep access for a period to export, and is that stated in days?

Check for exit fees, data return fees and minimum commitments that continue after you stop using the product. Check what happens to your data after the end: deletion timelines, whether you receive written confirmation of deletion, and whether backups are included. Check whether there is a transition help clause, even if paid.

If you are planning an exit, our guide at /blog/how-to-switch-applicant-tracking-systems-export-migration-cutover covers the export and cutover steps. The best time to ask exit questions is before signing, when the vendor wants your business. Ask them out loud: if we leave in a year, what exactly do we receive, in what format, within how many days? Write down the answer and ask for it in the contract.

The checklist as a scoring table

Use this table when you read a draft contract or a renewal. Mark each row green, amber or red, and negotiate or walk away from the reds.

You will rarely find a vendor that is green on every row, and small vendors may have standard terms they cannot change. The aim is to know where you are red and to decide with open eyes. Ask for what is cheap for the vendor to give: a renewal reminder, an increase cap, a longer export window, a short notice period. Many will agree to one or two of these for a signed order.

A worked example

Here is an example with made-up numbers. A 30-person company is offered an annual plan quoted at 2,400 a year for 5 recruiter seats, with a 20 percent first-year discount, so the first year costs 1,920. The contract renews for another 12 months with 90 days notice, no cap on increases, and an export fee on exit.

The team reads the draft, notes that the first-year discount hides a 480 jump at renewal, and sees that missing the notice date commits them to 2,400 or more. They ask for three changes: a cap on renewal increases at 5 percent, a 30-day notice period, and a free full export on exit. The vendor accepts the first and third, offers 60 days for the second, and the team signs, putting a reminder in the calendar for month 9. Without reading, they would have signed an agreement where one missed email cost a year. All numbers here are examples, and your vendor's terms will differ.

Common mistakes when you sign or renew

Signing the first draft. Standard terms are a starting position. Ask for the small changes that cost the vendor nothing.

Trusting the sales email over the document. Promises made in a call or chat do not bind the vendor unless they are in the contract or an order form. Get them written in.

Missing the renewal. Put the notice deadline in a shared calendar, not a personal one, so it survives staff changes.

Ignoring the order form. The main agreement may be generic, while the order form sets the price, seats and term. Read both.

Not testing the export. A promise to export is only worth the file you can open.

Forgetting who the signer is. If a manager without authority signs, or the company name is wrong, you may have trouble later. Check the legal entity on both sides.

Assuming monthly means flexible. Some monthly plans carry a minimum term or a cancellation window. Read the cancellation steps.

Treating this as the whole picture. This checklist is a prompt for your own review, not a substitute for a lawyer on a large or unusual deal.

Where Rezumz fits

Rezumz is an AI hiring workspace for small and mid-size hiring teams. Its pricing is public so you can compare terms against any vendor on your list: a free plan with 2 free candidate analyses, $29 a month, $199 a year, a limited $499 lifetime plan, and Team at $79 a month or $699 a year for up to 10 teammates. See /pricing for the current detail and the terms at checkout.

Rezumz suits small and mid-size hiring teams, and Team suits four or more recruiters. It does not suit large enterprises that need negotiated enterprise terms, deep HRIS or payroll connections, or teams that need one-click multiposting to job boards. If you need bespoke contract terms, ask before you buy. Try the product in the live /demo.

When this checklist is too much

If you are on a free plan or a month-to-month plan with no commitment, you do not need a long review. Read the price, the cancellation steps and the export, then move on. If you are signing a multi-year, high-value or enterprise agreement, this checklist is not enough, and a lawyer should read the draft. For everyone between, an hour with this list and a calendar reminder is the best value you will get from any piece of paperwork.