There is no ATS score here, and that is deliberate
Nobody outside a given company can tell you what its applicant tracking system will do with your file. A number claiming otherwise is a guess with a progress bar around it.
What actually goes wrong
Parsing failures are structural, not lexical. A file fails because of how it was built, and that part is knowable.
Columns
A parser reads a document linearly, so a document cut into two flowing columns interleaves into nonsense — your job titles land inside your skills.
Tables
Cell order is not reading order, so dates drift away from the roles they belong to.
Text inside graphics
A name set as an image is invisible to a parser and to a screen reader alike.
So the exports avoid all three
Not as an option to switch on — every template is built this way. The one two-column template keeps each section whole in one track and puts the work ahead of the rail in the file, so a parser reads it in order; the trade is named on its own card rather than hidden.
Classic
Conventional single column. The safest choice when you do not know what will parse the file.
Modern
Same structure with more open spacing and a stronger name treatment.
Compact
Tighter leading and spacing, for when a long history has to fit one page.
Editorial
Centred masthead and serif headings, for the resume a person opens before software does.
Technical
Ruled headings, dashed bullets and figures on a fixed width, so a column of dates lines up.
Minimal
No rules and no colour. Type and space carry the structure on their own.
Executive
A large name over generous space, headings in wide small capitals. For a short senior history that can afford the room.
Academic
Dates in their own column with entries hanging beside them. For a long list-shaped history: degrees, posts, publications.
Two column
Skills, education and certifications in a narrow rail; the work beside it. Usually shorter than one column, but not when the rail is the longer half — the page count beside the preview is the one to trust. Software reading the file reaches the rail after the work.
Banner
Centred colour masthead with a clean single-column body.
Ribbon
Colour header, outlined skill tags and a slim edge stripe.
Sidebar
A coloured left rail for your name and credentials, with work alongside it.
Panel
A colour masthead over a softly tinted right credential rail.
Ruled
A right credential rail, fine accent rules and shaded section labels.
Ledger
Section titles in a left gutter beside the detail, under a colour masthead.
Monogram
An initial badge and softly tinted introduction. A photo replaces the badge.
Contrast
An accent name and strong contact strip over a single column.
Compare them on the templates page.
The part a checker could not fix anyway
Most rejections are not about parsing. They are about a resume that does not answer the posting. That is what the coverage view is for: it lists each requirement beside the confirmed fact that supports it, and leaves the ones nothing supports empty rather than writing something to fill them.