Rejecting an Application: Should Your Recruitment App Also Send an Email?

Closing an application and telling the applicant are two decisions. A recruitment app should make their relationship explicit, rather than hiding an outbound message behind a status change. Before commissioning the workflow, decide who may close a case, what reason is recorded and whether a message should leave the system.

This guide concerns software behaviour. It does not prescribe lawful selection criteria, required notices or retention periods. Have the appropriate HR and legal reviewers establish those policies.

Close the right application, not every relationship

A fictional applicant has applied for a receptionist role and a warehouse role. Rejecting one application should not silently reject the other. Include the vacancy and application reference in the confirmation, not merely the person's name.

The Odoo 19 refusal documentation describes refusing duplicate applications for the same job position together, with one email. That is a specific duplicate-handling scope. It is not evidence that every application belonging to the same person should share an outcome.

In your brief, define how staff recognise duplicates and review the affected list. Two records with similar names are not enough to establish that they represent the same person. If identity is uncertain, route the case for review rather than offering a broad close-all shortcut.

Separate a useful reason from the outgoing wording

Odoo documents refusal reasons associated with email templates. For your tool, decide which reason categories help authorised staff understand the outcome and which wording is suitable for the applicant. An internal reason is not automatically an approved message.

Keep the categories meaningful. A filled vacancy, applicant withdrawal and duplicate submission explain different events. Avoid making staff select a negative assessment when the actual reason is that the vacancy no longer exists. Let the responsible reviewers approve the categories and any explanatory wording.

Free-text interview notes should not be inserted into an email merely because they are stored beside the application. Ask for a preview of the actual recipient, vacancy, subject and body before the permitted sending action. These are proposed controls, not verified default safeguards of the cited product.

Make no-email closure deliberate

The Odoo guide explicitly permits disabling Send Email when refusing an application, giving spam as an example. Your app needs a clear policy for this choice: when is notification required by your approved process, when is it inappropriate and who may override the default?

Show the result honestly. Application closed, message not requested is different from application closed, message awaiting delivery. A failed or uncertain send should not silently reopen the recruitment decision, nor should staff assume a closed record proves the applicant received anything.

If the delivery outcome is uncertain, preserve the attempted communication and reconcile it before resending. Do not promise that changing the application status and delivering external email form one indivisible operation.

Hidden is not deleted

Odoo states that refused applicants are hidden by default but remain viewable through refused-record views. Specify the same distinction clearly if your commissioned tool removes closed cases from the active board.

Agree who can retrieve those records and what appears in authorised reports. Retention and deletion need a separately reviewed policy; a refusal action is not proof that personal information has been erased. Conversely, a closed case should not remain visible to every staff member simply because history is useful.

Test the closure and communication separately

Use fictional records in your acceptance criteria. Reject one of two different applications for a person, close reviewed duplicates for one vacancy, refuse without email under the agreed policy and simulate an uncertain delivery. Inspect the affected records, reason, recipient and communication state after each action.

Bring your approved reason list and sample applicant message to a recruitment workflow discussion. The deliverable is a controlled case closure, not just a red label and an assumed email.