Before you follow up on a job application, check submission records, existing messages and the stated process. Decide whether you need to establish receipt or ask about progress. Use the designated contact, identify the role and submission date, add a reference if available and ask a brief specific question. Respect stated timelines and contact instructions. Silence alone proves neither rejection nor a failed submission.
Check what you actually submitted and received
Open the application you sent rather than a similar draft. Check the recipient, role and submission date. Is there a failure notice, a completed portal status or an automatic acknowledgement? Review the usual message folders, including spam. A file saved on your computer only shows that documents exist. It does not demonstrate that an application was successfully submitted through the required channel.
The jobs.ac.uk guidance recommends checking stated timelines, keeping records and identifying the vacancy clearly. We use those principles here. Its suggested intervals are guidance in context, not universal deadlines for every employer. The worked messages below are fictional editorial examples and cannot guarantee a reply or interview.
Make a short record of what is known: what was submitted, what was acknowledged and which information remains missing. Our guide to organising applications helps separate those stages. This prevents an enquiry about receipt when an existing message already confirms it, or a request for a decision while the employer's announced review period is still running.
Follow up on a job application: receipt or progress?
A receipt enquiry asks whether the documents arrived. A progress enquiry asks about the next stage or current processing position. Those are different questions. Acknowledgement does not establish that a person has assessed the application. Equally, a pending decision does not show that the submission failed. Decide which uncertainty you need to resolve before writing a message that asks several unrelated things at once.
Set one main purpose. If only receipt is unclear, you do not also need to demand an immediate selection decision. If receipt is already confirmed, do not repeat the full application. Identify the known context and ask for information that would actually help planning, such as an updated timeframe. The organiser may be able to answer a process question without being ready to make an individual decision.
This article concerns the stage before a first interview. After an interview, the conversation may have established a specific next step or expected response. Do not mix those stages in a template. A rejection is another distinct status: asking a general progress question does not reopen a decision already communicated. Check the latest reliable exchange before choosing the purpose of your contact.

Use the stated process rather than a universal day count
Read the advert and any acknowledgement. The employer may review applications after a closing date, provide a response window or ask applicants not to request updates. Those specific details matter more for this application than a generic recommendation. Asking immediately after a successful submission may yield little new information if the review stage has not even started.
When no timeframe is given, examine the reason for the enquiry. An explicit technical failure is different from impatience after a short wait. A missing automatic message does not by itself prove that anything was lost. Check the expected submission route first. If uncertainty remains, describe what you observed without presenting a suspected technical problem as an established fact.
This guide does not impose a single number of days. Processes differ by role, organisation and announced schedule. When a stated period has passed, refer to that period and ask whether an updated timeframe is available. Do not invent an agreed deadline or insist that the employer already promised an immediate decision. Your own planning can matter without turning an uncertain process into a commitment that was never made.
Worked example: ask about receipt without alleging a failure
In this fictional example, Nora submitted an application on 12 November 2026 through the requested route. She cannot find an acknowledgement and first wants to establish whether the documents are held. She has checked the recipient, submission record and message folders. A technical problem remains possible, but it has not been established. Her enquiry should reflect that distinction.
Before: uncertainty becomes an accusation
“You have obviously lost my application. Please decide immediately and confirm everything.”
After: a specific receipt question
“Hello, I submitted an application for the advertised administrative assistant position on 12 November 2026. I have not been able to find an acknowledgement. Could you please let me know whether my application has been received? I would be happy to provide any further identifying information needed to check. Kind regards, …”
Nora states her observation and asks for one piece of information. She neither alleges an error nor demands a decision at the same time. Replace the role and date with your actual details. Avoid sending complete duplicate application packs to several contacts as a precaution. Multiple submissions may make identification harder rather than resolve the original uncertainty about receipt.

Worked example: ask after an announced review period
In this second fictional situation, Amir received an acknowledgement that mentioned a response after a review phase. The stated period has passed, but no further message has reached him. He wants to know whether an updated timeframe can be given. Receipt is already established, so he does not need to cast doubt on the submission again or repeat every qualification.
Before: pressure and an invented explanation
“Your silence shows that you are ignoring me. I expect a job offer today.”
After: context and one practical question
“Hello, thank you for acknowledging my application for the administrative assistant position. Your message mentioned a response following the review phase. As I have not yet received a further update, could you please let me know whether an updated timeframe for the next stage is available? I remain interested in the role. Kind regards, …”
Amir asks about the process without attributing an intention to the silence. He does not claim an entitlement to an offer or an agreement to reply immediately. An existing reference can make the application easier to identify. A brief concrete connection is more useful here than a second long argument about his suitability. Any timeframe subsequently supplied should be recorded as the new information, not a guaranteed selection outcome.

Use a suitable contact and prepare a phone enquiry
Use the contact provided for the recruitment process. A portal may have status information or a messaging function. A named person may handle queries, while a general distribution list or a private profile found elsewhere may not. Respect instructions that exclude progress enquiries or specify a channel. Going around those instructions does not create a more reliable route to an answer.
For a phone call, keep the role, date, reference and main question ready. First check that you have reached the appropriate person, then explain the reason briefly. If they do not know the status, ask for the designated method where appropriate. Do not try to force an assessment during the call. Afterwards, record the information accurately, including any next step actually mentioned.
For a written enquiry, use an informative subject and check the greeting, recipient and template details. Attach documents again only when requested or necessary for a clarified technical issue. Our application documents guide covers choosing supporting material. A status question does not automatically need every certificate and resume version. Keep personal information limited to what is necessary for identifying and addressing the enquiry.

Work with an open answer without inventing certainty
If the employer provides a new timeframe, record it and use that information when considering further contact. “Still being reviewed” is neither an offer nor a rejection. If something is missing, clarify which document and submission route are required. Do not send an indiscriminate bundle when the actual issue concerns a reference, a particular file or identifying the right application.
If the enquiry receives no response, avoid a rapid sequence of identical messages across multiple channels. Check whether the message used the stated contact and whether new information has appeared. Continue other suitable applications without treating the unresolved one as either a success or a failure. An uncertain position does not need to be replaced with a conclusion unsupported by the available information.
You can prepare for a possible next stage without assuming it will happen. Our interview preparation guide can help if an invitation arrives. A plain notebook or spreadsheet is enough to track the process. The enquiry aims to clarify information; it is not a substitute for continuing the search and cannot ensure a response, an interview or a hiring decision.
Read the question from the recipient’s perspective
Can the recipient identify which application you mean and what information you need? Remove guesses about motives, accusations and deadlines that were never agreed. Retain the details needed for a practical identification. A courteous tone does not require a lengthy apology for raising a reasonable question. It requires a clear purpose and respect for the actual instructions governing the process.
Final enquiry review
- Submission records and existing messages were checked.
- Receipt and progress are different questions.
- Stated timelines and contact rules were considered.
- The role, date and reference are accurate.
- The main question is specific.
- No decision or motive is inferred from silence.
- Documents are not duplicated unnecessarily.
- The next reliable information will be recorded.
A useful enquiry may enable clarification but cannot force an answer. State what you know and ask for what is genuinely missing. That makes the contact understandable and helps you maintain an accurate record even when the process stays open longer than you hoped. Clear record keeping also supports sensible decisions about other opportunities rather than repeated speculative contact.
Frequently asked questions
When can I ask about an application?
Check explicit deadlines, announced response periods and contact instructions first. This guide does not impose a universal day count. An elapsed stated period or a genuine submission uncertainty can provide a specific reason to enquire.
Does no acknowledgement mean nothing arrived?
No. Check submission records, portal status and message folders. A missing automatic message alone proves neither a failed submission nor successful receipt. Ask a factual question if uncertainty remains.
Should I call or write?
Use the method provided for the process. Check portal instructions and responsibility. If progress queries are excluded, switching to another channel does not make that instruction disappear.
Should I attach the application again?
Not automatically. Complete duplicates can complicate identification. Supply a specific file or repeat submission when that action has been requested or the technical issue has been clarified.
Does silence mean rejection?
Without further information it does not establish a decision. Record the status as open and continue other suitable applications. An enquiry guarantees neither an answer nor an interview.
