Eploy's parser populates candidate fields automatically, but only if the CV is clean. Tables, graphics, and merged contact lines are the usual reasons data lands in the wrong field — or not at all. This guide gives you the formatting rules that keep Eploy happy.
TL;DR: Eploy struggles with tables, unusual fonts, merged contact details, and graphics. Use single-column paragraph formatting, standard fonts at 10–12pt, contact details on separate lines, and a text-based .docx. If you process CVs at volume, Distill applies these rules automatically.
Quick diagnosis: Is this an Eploy formatting problem?
| Symptom | Likely cause | Quick check |
|---|---|---|
| Candidate name not extracted | Table or unusual font in header | Is the name inside a table or styled font? |
| Phone and email merged or missing | Contact details share a line/symbol | Are phone and email on the same line? |
| Work experience misaligned | Tables or inconsistent dates | Is the experience block in a table? |
| Skills run together | Bullets replaced with commas | Are skills a paragraph instead of a list? |
| Upload looks fine but fields empty | Scanned or image-based PDF | Can you select text in the PDF? |
Why Eploy fails on CVs: root causes ranked by frequency
Tables Eploy's parser routinely ignores or scrambles content inside tables. Names and contact blocks placed in a header table are the most common casualties.
Merged contact details When phone and email share a line, or use symbols like "☎" or "✉", Eploy fails to split them into the right fields.
Non-standard fonts and heading styles Unusual fonts or inconsistent heading styles confuse field detection, so sections map to the wrong place.
Graphics and photos Logos and candidate photos aren't parsed and can cause misalignment or upload errors.
Wrong file format Older .doc files and scanned images parse poorly. Eploy prefers .docx and text-based PDFs.
Inconsistent date formats Mixed date styles cause roles to be skipped or misdated.
Step-by-step fix for Eploy CV formatting
- Remove all tables. Use standard paragraph formatting and spacing for every section.
- Put contact details on separate lines. Name, phone, and email each on their own line at the top, in plain text — no symbols.
- Use standard fonts. Arial, Calibri, or Times New Roman at 10–12pt.
- Use consistent headings. "Work Experience", "Education", "Skills" in a consistent bold style.
- Use plain bullets. Standard bullet characters, not images or special symbols.
- Standardise dates. "Jan 2020 – Dec 2022" or "01/2020 – 12/2022", applied consistently.
- Remove graphics. Strip logos and candidate photos before upload.
- Save as text-based .docx. Avoid older .doc and scanned PDFs.
How to prevent Eploy formatting errors on future submittals
- Standardise an Eploy-friendly template: single column, no tables, contact details stacked.
- Train recruiters to check the contact block and remove tables before upload.
- Automate cleanup with Distill when volume makes manual edits impractical.
- Keep a quick pre-upload checklist: tables, contact lines, fonts, dates, file type.
When to escalate to Distill
Use Distill if:
- You submit 20+ CVs weekly to Eploy.
- Names or contact details routinely fail to extract.
- You need to anonymise name, email, phone, photo, and graduation year as well.
Distill strips photos and logos, removes tables, splits contact details onto clean lines, and outputs a text-free, single-column .docx tuned for Eploy's parser.
FAQ
Q: Why won't Eploy extract the candidate's name? A: It's usually inside a table or styled with an unusual font in the header. Move it to plain text in the body.
Q: Phone and email keep merging. How do I fix it? A: Put them on separate lines with no symbols. Eploy splits fields by line.
Q: Can I use a PDF with Eploy? A: Yes, if it's text-based. Scanned PDFs and older .doc files parse poorly — prefer .docx.
Q: What font size works best? A: 10–12pt in Arial, Calibri, or Times New Roman.
Q: Does removing tables lose information? A: Only if skills or contact details live in tables. Reformat them as separate lines or bullets first.
If you process CVs at volume for Eploy, Distill formats each one to the spec above automatically. Try Distill free and cut your prep time to seconds.