Resume submission guide
Name the file clearly. Send the requested format.
A strong document can still be undermined by the wrong attachment, an ambiguous filename, hidden comments, broken export, or a format the application does not accept.
Written by the Scoritly team · Published
The short answer
Use your name, the document type, and the required extension
DOL's 2026 Resume Essentials guide recommends a clear professional filename that includes the applicant's name and identifies the resume. A practical pattern is FirstnameLastname_Resume.ext. Add a target role or supplied reference number only when it helps and remains accurate.
The filename does not improve qualifications or parsing by itself. Its job is to keep a downloaded document identifiable and prevent you from attaching the wrong file. Always follow any naming convention, format, size, or upload instruction in the live application.
Filename pattern
Keep the submitted name short, identifiable, and stable
| Use | Fictional filename | Pattern |
|---|---|---|
| General application | JordanLee_Resume.pdf | Name + document type |
| Targeted copy | JordanLee_ProductAnalyst_Resume.docx | Name + target + document type |
| Reference number requested | JordanLee_Resume_Ref12345.pdf | Name + document type + supplied reference |
| Cover letter | JordanLee_CoverLetter.pdf | Separate, unmistakable document type |
Every person, role, reference number, and filename above is fictional. Match the application's accepted characters. When none are specified, a conservative filename uses ordinary letters or numbers and a simple separator such as an underscore.
What to avoid
Remove ambiguity, private data, and internal drafting clutter
Avoid names such as resume.pdf, document1.docx, newresumeFINAL2.pdf, or another employer's name. Do not include a Social Security number, birth date, account identifier, medical detail, full street address, password, or other sensitive data in the filename.
Keep internal version details in your own folder or tracking system. Before submission, create a clean outward-facing name and confirm that changing the filename did not change or corrupt the extension.
PDF or Word
The application decides before general preferences do
| Instruction | Choice | Verification |
|---|---|---|
| Posting requests PDF | Submit PDF | Export from the editable source, then inspect the exported pages and selectable text. |
| Posting requests Word | Submit the permitted Word type | Use the exact extension requested and re-open it in a compatible viewer. |
| Portal lists allowed types | Choose only from that list | Also obey size, page, encryption, signature, and upload-field restrictions. |
| No preference stated | Choose after testing the actual file | PDF usually preserves layout; a plain DOCX may be useful where Word compatibility is preferred. |
DOL says to submit PDF or Word as requested. It notes that PDF preserves formatting, while Word compatibility and rendering can vary. Neither extension guarantees successful parsing; the file must contain readable text and a structure the receiving system can process.
Build the files
Keep one editable source and export a fresh submission copy
- 01
Tailor the source
Update the content for the actual posting and preserve an editable working document.
- 02
Clean the document
Accept or reject tracked changes, remove comments, inspect links, and review document properties.
- 03
Export or save as
Create only the requested type; do not change an extension to imitate a conversion.
- 04
Open independently
Re-open the saved file, inspect every page, and confirm text can be selected or copied when text is expected.
- 05
Name the submission
Apply the clear outward-facing filename after the correct version and format are confirmed.
Privacy and cleanup
Visible pages are not the only place a document can carry information
Review comments, tracked changes, hidden text, headers, footers, document properties, author fields, embedded objects, links, and filenames. Remove information that the application does not request and that should not be shared.
A PDF export can preserve annotations, links, metadata, or hidden layers; a Word file can retain revision history, comments, properties, or embedded content. Use the application's security rules and do not submit encrypted, signed, macro-enabled, password-protected, or portfolio files unless explicitly accepted.
Email attachments
Keep the subject, body, and attachments consistent
DOL recommends following the posting's email instructions, identifying the applicant and target in the subject when appropriate, and attaching the resume and cover letter as separate, clearly named files. Paste content into the message body only when requested.
After attaching, open each attachment from the draft message. Confirm the displayed filename, document type, employer or role targeting, and cover-letter recipient before sending. A polished email cannot correct the wrong file. Use the cover letter versus resume guide to review what each attachment should contain.
Portal uploads
Verify the platform-specific copy after upload
Upload limits are not universal. Check the live portal for accepted extensions, maximum size, page limits, encryption rules, and whether it renames or converts the document. Preview or download the stored copy when that option exists.
Current USAJOBS guidance, for example, sets its own page and size limits, recommends PDF for its workflow, lists additional accepted types, and excludes encrypted, digitally signed, and PDF portfolio files. Those rules apply to USAJOBS, not every employer.
Application tracking
Record which exact file went to which employer
Store the submitted filename, target role, employer, source version, date, and posting copy with the application record. This makes follow-up and interview preparation more reliable and reduces the chance of overwriting a targeted resume.
The application tracking guide provides a practical record structure. Keep local version detail there instead of making the employer-facing filename unreadable.
AI boundaries
AI cannot prove that the exported or uploaded file is correct
AI can suggest a filename from supplied facts or review extracted resume text. It cannot know which file you selected, whether the extension matches its contents, how a portal transformed it, whether hidden metadata remains, or whether the rendered pages changed after export.
Do not rely on a filename or AI summary as proof. Open the exact attachment or uploaded copy and compare it with the posting and intended final version.
Final review
Check the name, contents, format, and destination together
- The filename contains your name and the correct document type without private identifiers.
- The extension and file contents match the format requested by the posting or portal.
- The submitted copy is the targeted final version, not a template, draft, or different employer's version.
- Comments, tracked changes, hidden text, document properties, and embedded private data have been reviewed.
- The file opens, displays every page correctly, contains readable text, and stays within current upload limits.
- The uploaded or attached file is downloaded or previewed once more before final submission.