Quick answer: Maintaining a recruitment website means testing more than WordPress updates. Open roles, search filters, application buttons, CV uploads, confirmation messages and delivery to the right HR owner must work as one journey. A careers page that loads but loses applications is not operationally healthy.
Candidates often apply from a phone. They find a role, read the details, upload a CV and expect a clear acknowledgement. Recruiters need a traceable record rather than relying on a single email that may be filtered or sent to a former employee. Test both ends after changes to the theme, form, mail setup or applicant tracking system (ATS).
Could your careers site be losing applications?
IT Systems can review the application flow, CV upload, email delivery and handoff to HR before defining a maintenance scope.
Why careers sites need their own maintenance checklist
Recruitment content changes frequently: new vacancies, closed roles, deadlines, location, seniority and the hiring contact. If the job listing, detail page and application form disagree, candidates waste time and HR receives misrouted submissions. A generic website uptime check will not catch that mismatch.
Common hidden failures include a success screen despite failed email delivery, a CV file-size rejection with no useful message, an application sent to a departed employee, and an old campaign form reused for a new role. The full candidate-to-HR journey needs a repeatable test.
Nine checks to run regularly
- Open roles: compare status, deadlines, location, work arrangement and department with HR-approved data.
- Job details: check requirements, responsibilities, benefits, location and apply button; remove misleading legacy copy.
- Search and filters: try role, department and location filters, including a no-results state and a link to the correct job.
- Mobile journey: follow a listing through the application form on a narrow screen; check blocked buttons, overflowing inputs and keyboard behavior.
- Form validation: confirm required fields, clear error messages, duplicate-submit handling and the message after submission.
- CV attachment: test accepted file types and sizes, visible errors, restricted access and the storage location; avoid a predictable public file URL.
- Candidate acknowledgement: say the application was received without implying a hiring decision or interview invitation.
- HR handoff: confirm the form/ATS record, notification email, backup recipient and ability to identify the vacancy.
- Access and recovery: review former HR users, backups, plugin/theme updates and the ability to restore the application flow.
Run one application test end to end
Choose an active vacancy and agree on a clearly labeled TEST application with HR. Do not use a real candidate’s personal data. As a public visitor, open the listing on phone and desktop, read the role, complete the required fields and upload a valid sample file. Record the time, URL, device, resulting screen and submission ID if available.
HR then checks that the record reached the correct inbox or ATS, belongs to the correct vacancy and includes an accessible file. Repeat with missing required fields, an unsupported file, an oversized file and a double click. Review the acknowledgement, stored record, mail delivery and spam folder. Remove the TEST record according to the company’s process so it cannot be mistaken for a real candidate.
Where a third-party ATS is involved, the website team can verify the outbound handoff and coordinate with the ATS owner. New API mapping, complex synchronization and a redesigned hiring workflow are separate project work unless explicitly included in the maintenance agreement.
What if the form says success but HR sees no CV?
First determine whether the issue affects every role or one listing, every device or mobile only. Look for a saved form entry if that feature is enabled. Then inspect mail logs, recipients, spam filtering and forwarding rules. If a record exists but the email failed, restore the notification path and let authorized HR staff access the saved application. Avoid immediately asking candidates to resubmit when the original record’s status is unknown.
If no record exists, inspect validation, file limits, captcha, blocked scripts and update-related errors. If the ATS reports receipt, compare transaction identifiers on both sides and involve its owner. HR should approve any temporary fallback channel and public notice. The technical team should not move candidate CVs into personal chat or email accounts on its own.
Who owns each part of the flow?
| Situation | Business owner | Website team check |
|---|---|---|
| Publish or close a role | HR approves content and effective date | Display, links, form and status |
| Candidate cannot upload a CV | HR sets priority and fallback channel | Form, file handling, scripts and logs |
| Application absent from ATS | HR and ATS owner investigate receipt | Outbound event and error evidence |
| Retain or delete applications | HR and data owner decide policy | Execute only within approved access and process |
Candidate privacy belongs in the maintenance process
A CV may include a phone number, email, employment history and other personal information. The business should identify who can view it, where it is stored, how long it is kept and how candidate requests are handled under its applicable policy. Technical controls should include role-based individual accounts, access removal when staff leave, restricted file access and incident records. This article is operational guidance, not legal advice.
Backups containing CVs also need appropriate protection. At a provider handoff, document user permissions, attachment storage, receiving addresses, backup copies and access revocation. The website maintenance handover checklist covers the broader access and form inventory; verify your specific setup during the review.
What should a recurring report contain?
A useful report says more than “plugins updated.” For a careers site it should list the date tested, role used, submission outcome, HR destination, mail/ATS result, stale vacancies, mobile issues, backup state and items awaiting a business decision. Mark each item as tested, awaiting HR confirmation or outside the current scope.
Retest after changes to forms, plugins, mail, theme or ATS, and before a major hiring campaign. The right cadence depends on application volume, open roles, recruitment schedule and the agreed service level. The website maintenance SLA guide explains why application-form failure can be a high-priority incident during hiring.
When does maintenance become a separate project?
Routine maintenance covers agreed checks, updates, backups and repairs to an existing handed-over flow. A new careers portal, multi-level approval, two-way ATS integration, automated candidate scoring or historical data migration changes the product. It needs requirements, access planning, acceptance tests and its own estimate. A clear boundary prevents a complex data project from being mistaken for a simple toggle.
Frequently asked questions
Why test if the careers page still loads?
The failure may be in the apply button, file upload, recipient email or ATS. A TEST application verifies the full journey.
Should expired vacancies remain visible?
Only by HR’s deliberate choice and with a clear closed status. Do not leave an active application button on a role that no longer accepts CVs.
Does the maintenance team need access to real CVs?
Not by default. Use sample data for tests; access to real applications should be granted only for an approved role and purpose.
Is an ATS outage part of website maintenance?
The website team can inspect the handoff and provide evidence. Fixing the ATS or integration depends on the contract and system owner.
Review the application flow before the next hiring drive
Share the careers URL, the form in use and how HR receives applications. IT Systems can identify the test points and suitable support scope.
