Chameleon-i parses CVs into candidate records automatically, but when the CV layout confuses the parser you end up with empty name fields, merged contact details, or work history in the wrong order. This guide shows you how to spot the cause and fix it before the record reaches a client.
TL;DR: Chameleon-i parsing errors come from tables in the CV header, decorative fonts, merged contact lines, and image-based PDFs. Move the name and contact block into plain text, standardise dates, and upload a text-based .docx. If you fix the same issues every week, Distill automates the cleanup before upload.
Quick diagnosis: why Chameleon-i parsing fails
| Symptom | Likely cause | Quick check |
|---|---|---|
| Candidate name not extracted | Name inside a header table | Is the name in a table or text box? |
| Contact details merged/missing | Phone + email share a line or symbol | Are they on one line, or using ☎/✉? |
| Work history out of order | Tables or inconsistent date formats | Is the experience block a table? |
| Skills lumped into one field | Bulleted list flattened to a sentence | Are skills a list or a paragraph? |
| Record created but fields empty | Scanned or image-based PDF | Can you select the PDF text? |
What causes Chameleon-i parsing errors most often
Tables in the header Designers love putting the candidate's name and contact block in a two-column table. Chameleon-i's parser reads tables unpredictably, so the most important fields come through empty or scrambled.
Decorative fonts and styled headings Unusual fonts and heavily styled section headings confuse field detection. The parser relies on recognisable headings like "Work Experience" and "Education" in a standard font.
Merged contact details Phone and email on one line — or wrapped in symbols — prevent Chameleon-i from splitting them into separate fields.
Inconsistent date formats Mixing "Jan 2024", "01/2024", and "2024" across roles causes skipped positions or wrong durations in the parsed record.
Scanned or image-based PDFs If you can't select the text in the PDF, neither can the parser. Fields stay empty.
Step-by-step fix for Chameleon-i parsing errors
- Remove the header table. Put the name and contact block in plain text at the top of 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.
- Replace decorative fonts with a standard font (Arial, Calibri) at 10–12pt.
- Confirm the file is text-based — convert scanned PDFs to .docx before upload.
- Re-upload to a test record and check that name, contact, and roles all mapped.
How to prevent Chameleon-i parsing errors
- Use one parser-friendly CV template across the team — no header tables, stacked contact details.
- Check name extraction and the contact block on every upload; those two fields fail first.
- 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 automate this
Manual cleanup makes sense for the occasional CV. Automate when:
- You submit 20+ CVs weekly through Chameleon-i.
- 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 Chameleon-i — before you import.
FAQ
Q: Why is Chameleon-i 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: Chameleon-i skipped a whole role. What happened? A: Inconsistent date formatting or a table in the experience block. Standardise dates and remove tables.
Q: Can Chameleon-i parse a scanned PDF? A: No. It needs selectable text. Use a text-based PDF or .docx.
Q: Does Distill connect to Chameleon-i directly? A: No. It cleans CVs before you import them into Chameleon-i.
If Chameleon-i parsing errors keep reaching your records, Distill cleans each CV to spec automatically. Try Distill free and stop re-keying candidate data.