LUCERIA
Free tool · runs in your browser · no account

Job application follow-up planner

Give the date you applied and whatever the employer told you: a closing date, a stated response time, an interview or decision date. The planner produces dated steps counted in working days, with the assumption behind each one shown and editable, plus short message frameworks you fill in your own words. Nothing is sent from the page; it is a schedule for your tracker or calendar.

Everything you type is processed in your browser. A draft is kept in this browser's local storage so you can come back to it, and a visible Clear control deletes it. Nothing is uploaded, stored or logged by Luceria; analytics record only that the tool was used, never its contents.

Use the tool

Required. Dates are counted in working days (Monday to Friday); adjust for public holidays yourself.

For example 'we aim to respond within 10 working days'.

With an interview date, the plan switches to a thank-you note and a decision check.

Assumptions (edit them)

These are conventions, not rules. Change any of them to match what the employer told you.

How it works

  1. Working days (Monday to Friday) are counted; public holidays are not known to the tool, so adjust by hand.
  2. With a stated response window, the first follow-up lands a short grace period after it; with a closing date, a set number of working days after it; with neither, a set period after you applied.
  3. After an interview the plan switches to a thank-you note the next working day and a decision check after the promised date plus grace.
  4. Follow-ups stop after a configurable number so the plan has an end, and the final step is to record the outcome.

What it does not do

Timing is convention, not a rule, and employers vary widely. The planner does not know the employer's process, cannot promise a reply and does not send anything. Use what the employer actually said over any default here.

Your data

Everything you type is processed in your browser. A draft is kept in this browser's local storage so you can come back to it, and a visible Clear control deletes it. Nothing is uploaded, stored or logged by Luceria; analytics record only that the tool was used, never its contents.

Worked example

Illustrative example with invented details, not a real person’s result.

A fictional application with a closing date: inputs

  • Applied on 2 November 2026 by email; the advert closes on 13 November; no stated response time.
  • Default assumptions: wait 7 working days after closing, 7 working days between follow-ups, stop after 2.

What the tool shows

  • First follow-up on Tuesday 24 November, with a short confirmation-and-interest framework.
  • Second follow-up on Thursday 3 December, shorter, asking only whether the role is still open.
  • Stop step on Monday 14 December: close the application in the tracker; a late reply can still come.

How to use it well

  1. Enter the dates exactly as the employer gave them; if they said ten working days, put ten.
  2. Change the assumptions when you know more, for example a recruiter who told you to wait two weeks.
  3. Copy the plan into your tracker's next-action dates so the follow-ups do not depend on memory.
  4. Keep each message under about 120 words and reply in the same thread as the application where possible.

Common questions

Is following up ever a bad idea?

A polite, short message after a reasonable wait is normal. Repeated messages, phone calls after being asked to wait, or contacting staff who are not involved can hurt.

What if the advert says no follow-ups?

Respect it. Use the plan only to decide when to treat the application as closed.

Should I follow up through a recruiter or the employer?

Through the recruiter if one introduced you; they usually have the employer's timeline and contacting the employer directly can undercut them.