Eploy doesn't flag parsing errors clearly — you only notice once a field is empty or jumbled. If candidate names go missing, contact details merge, or roles get skipped, this guide helps you find the cause and fix it before it reaches the client.
TL;DR: Eploy parsing errors come from tables in the header, merged contact lines, inconsistent dates, and scanned PDFs. Clean the CV first: remove tables, stack contact details, standardise dates, and use text-based .docx. If you fix the same issues weekly, Distill automates it.
Quick diagnosis: why Eploy parsing fails
| Symptom | Likely cause | Quick check |
|---|---|---|
| Candidate name not extracted | Table or unusual font in header | Is the name inside a table? |
| Contact details missing/merged | Phone + email share a line or symbol | Are they on one line, or using ☎/✉? |
| Work experience misaligned | Tables or inconsistent date formats | Is the experience block a table? |
| Skills lumped together | Bullets replaced by commas/paragraph | Are skills a list or a sentence? |
| Duplicate entries | Repeated sections or odd spacing | Does the CV repeat any section? |
| Fields empty after upload | Scanned/image-based PDF | Can you select the PDF text? |
What causes Eploy parsing errors most often
Tables in the header The name and contact block are often laid out in a table. Eploy ignores or scrambles table content, so the most important fields come through empty.
Merged contact details Phone and email on one line, or wrapped in symbols, prevent Eploy from splitting them into the right fields.
Inconsistent date formats Mixed date styles cause Eploy to skip roles or assign the wrong duration.
Bullets converted to commas or paragraphs When a skills list loses its bullets, Eploy reads it as one block and can't separate the entries.
Repeated sections and inconsistent spacing Duplicate headings or erratic spacing make Eploy create duplicate or partial entries.
Scanned or image-based PDFs Without selectable text there's nothing to parse, so fields stay empty.
Step-by-step fix for Eploy parsing errors
- Remove the header table. Put the name and contact block in plain text in the body.
- Stack contact details. Phone and email on separate lines, no symbols.
- Standardise every date to one format across all roles.
- Restore bullet points for skills and responsibilities — no comma lists.
- Delete duplicate sections and normalise spacing between roles.
- Confirm the PDF is text-based, or convert to .docx before upload.
- Re-upload to a test record and confirm name, contact, and roles all mapped.
How to prevent Eploy parsing errors
- Use one parser-friendly template across the team — no header tables, stacked contact details.
- Train recruiters to check name extraction and the contact block on every upload.
- Batch-clean high volumes with Distill instead of fixing records by hand.
- Keep a 30-second pre-upload check: tables, contact lines, dates, bullets, file type.
When to escalate to Distill
Use Distill when the same Eploy errors keep recurring:
- You submit 20+ CVs weekly to Eploy.
- Names and contact details routinely fail to parse.
- You also need to anonymise candidate data before client submission.
Distill removes tables, relocates and splits contact details, normalises dates, and outputs a clean .docx tuned for Eploy — before you import.
FAQ
Q: Why is Eploy missing the candidate's name? A: It's in a header table or styled font. Move it to plain text in the body.
Q: Phone and email came through as one field. Why? A: They shared a line or used symbols. Put each on its own line in plain text.
Q: Eploy skipped a whole role. What happened? A: Inconsistent date formatting or a table in the experience block. Standardise dates and remove tables.
Q: Can Eploy parse a scanned PDF? A: No. It needs selectable text. Use a text-based PDF or .docx.
Q: Does Distill connect to Eploy directly? A: No. It cleans CVs before you import them into Eploy.
If Eploy parsing errors keep reaching your records, Distill cleans each CV to spec automatically. Try Distill free and stop re-keying candidate data.