An additional-document request usually means the reviewer cannot complete the next check with the current file. It is not automatically a rejection or an admission decision. The safest response is accurate, limited to the request and sent through the verified application route.
Do not let urgency remove basic security. A convincing email can still be fraudulent, and an authentic request can still be misunderstood. Verify first, then respond once with a clear record.
Read the whole request
Identify the application, programme, requested item, reason, deadline, file format and submission route. Look for whether the university wants a replacement, an additional page, a certified version or a simple explanation. These are different actions.
Verify the sender independently
Check the sending domain, application reference and portal message. If the email contains a new payment account, login link or unusual request for identity data, contact the institution using details you already know or its official website. The UK National Cyber Security Centre advises using independently verified contact details rather than those inside a suspicious message.
Check the application status without overinterpreting it
A status such as Pending, Admission Process Started or Application Submitted describes a processing stage, not a final outcome. Read the application tracking guide and use the actual message to understand the requested action.
Define exactly what is missing
Compare the request with the file already submitted. The issue may be a missing page, unreadable scan, expired passport, absent translation, incorrect document type or unmatched name. Do not assume the reviewer wants the entire application again.
Ask one focused question when necessary
If the request is ambiguous, reply with the application reference and a concise choice: for example, whether the university needs the original-language transcript, the certified translation or both. Avoid a long narrative and keep the reply with the tracked application message.
Prepare the replacement carefully
Use the correct original, include all required pages and check the requested certification or translation. Name the file neutrally. Do not edit the official information. If obtaining the document will take time, explain the realistic date and ask whether interim evidence is accepted.
Use the stated secure route
Upload through the portal or official mechanism where available. Follow the Univs student portal guide so the new version remains connected to the application. Do not send the same sensitive file to several staff addresses “just in case”.
Meet the deadline and timezone
Record the date, local time and timezone. Leave enough time for a failed upload or clarification. If the deadline cannot be met, contact the responsible team before it passes. Do not invent a submission confirmation or backdate a file.
Confirm receipt without repeated chasing
Save the upload confirmation or sent message. If no acknowledgement appears within the stated review period, send one follow-up with the date and exact file name. Repeated messages can split the history and do not necessarily speed up review.
Watch for requests that should pause the process
Stop if someone asks for passwords, one-time codes, control of your email account, payment to an unrelated individual, altered academic evidence or sensitive files with no clear purpose. Verify through a separate official channel and report suspected fraud.
Handle several requests in one organised reply
If the admissions team lists multiple missing items, copy them into a private checklist and answer in the same order. State which files are attached or uploaded and which item needs clarification. Do not combine unrelated records into one image. A structured response lets the reviewer close each requirement without searching through a long explanation or guessing which attachment belongs to which request.
What if the document is controlled by another person?
A referee, school, testing body or government office may need to send evidence directly. Confirm the correct recipient and deadline, then monitor the status without impersonating the sender. If the invitation or official transmission fails, ask the responsible organisation to resend or verify it. Keep your own follow-up factual; do not create a substitute letter or upload confidential evidence that was meant to remain independent.
Response checklist
- Sender and application reference verified.
- Exact missing item and deadline identified.
- Correct document prepared without alteration.
- Secure official route used.
- Submission and any clarification saved.
Write a reply that closes the request
Use the application reference and state the requested item in the first sentence. Explain whether it was uploaded or attached, give the exact file name and submission date, then ask for confirmation only if the process does not provide it automatically. Do not repeat the full application history or include unrelated documents. Compare the action with the current application sequence so the reply closes the right requirement.
A request is part of the evidence trail
Keep the original message, submitted version and response together in the student portal record. That record protects the student and the admissions team from guessing which document was requested, which version was supplied and when the action was completed.
Editorial note
Requirements can change and may differ by institution, programme and applicant. Recheck current university and government guidance before paying or travelling.
