Meaning over keywords
Every section is turned into a 384-dimension embedding. Two sections that say the same thing in different words end up close together.
AI document gap analysis
Upload the old and new version of a policy, contract or standard. GapexAI pairs every section with its counterpart, even after renumbering, and explains each change with quotes from both files.
Passwords now need 12 characters instead of 8, the 90-day expiry rule is gone and MFA is required for every account. Update the identity provider settings.
of sections appear in the report, including the ones that were removed
agreement with an expert reviewer on our best benchmark document
of section matching before any language model is called
spending cap per comparison, and repeat runs use the cache
Why it matters
A new version can move, rename and reword dozens of sections. Reading both versions side by side takes days, and small changes to a number or a deadline are easy to miss.
Manual review
With GapexAI
How it works
Add the old and the new version as Word or PDF files.
Both files are broken into numbered sections. Cover pages and empty headings are left out.
Each new section is paired with its old counterpart, even if it was renumbered or renamed.
A language model compares each pair and describes the change using the values from both files.
Download the report as Word, Excel, PDF, CSV or JSON.
Inside the engine
Embeddings and fixed rules decide which sections belong together. The language model only writes the findings, and it sees one pair of sections at a time.
Every section is turned into a 384-dimension embedding. Two sections that say the same thing in different words end up close together.
Candidate pairs are scored with cosine similarity. If a pair scores too low, the sections are reported as new or removed instead of being forced together.
Exact section number, exact heading, renumbered chapters, split sections and finally semantic similarity. Each stage follows fixed rules, so the result is repeatable.
Cover pages, informative annexes, heading-only lines and stray table text are dropped before anything is compared.
When a section says “see 5.3”, section 5.3 is added to the analysis for both versions of the document.
Findings quote both documents. Section numbers come from the parser rather than the model, and every model response is checked against a fixed schema.
A small, fast model handles most pairs. Long or uncertain pairs go to a larger model. Each run has a cost cap and a cache.
Figures, tables and images are marked as not analysed, so a reviewer knows exactly where to look.
Below this score, two sections are not paired.
Stops unrelated sections being paired just because they share a number.
Every new and every removed section gets its own row.
Example findings
Choose a document, then a finding, to see the text from both versions next to what GapexAI reported.
Passwords shall be at least eight (8) characters long and shall be changed every ninety (90) days. Passwords shall not be shared.
Passwords shall be at least twelve (12) characters long and shall not be shared. Multi-factor authentication is mandatory for all accounts. Periodic password expiry is no longer required.
2025 (4) raises the minimum password length to 12 characters from 2023's 8 characters and makes multi-factor authentication mandatory, while 2023 required passwords to be changed every 90 days; the password policy and training materials must be updated accordingly.
Renamed section, matched by meaning.
Use cases
It works best on documents with numbered sections or clear headings.
Security policies, HR handbooks and operating procedures.
Changed obligations, fees, notice periods and liability caps.
A revised standard compared with the edition you follow today.
ISO 27001, SOC 2 and internal control updates.
A proposal checked against the requirements it has to meet.
API and product specs across releases.
Changes to cover, exclusions and limits.
Quality manuals and work instructions after a rule change.
How we built it
Each part of GapexAI was developed with its own coding agent, responsible for that area's code, tests and quality checks.
Reads Word and PDF files and splits them into sections
Embeddings, similarity scores and the five matching stages
Prompts, structured output and model routing
Finds references between sections and resolves them
Word, Excel, PDF, CSV and JSON exports
Samples findings and checks them against the source
Sign-in, background jobs and the database
The dashboard, uploads and charts
The dashboard
Security and privacy
FAQ
It is a side-by-side review of two versions of the same document to find what changed, what was added and what was removed. GapexAI does the matching for you and writes a short finding for every section, with quotes from both versions.
Each section is converted into an embedding that represents its meaning. A five-stage matcher then pairs sections by exact number, exact heading, renumbered chapters, split sections and finally by similarity. Pairs with a low score are not forced together.
Yes. Matching looks at what a section says, and one stage is dedicated to chapters that changed number. A section that moved from 6 to 5 is still paired with its original.
The model has to quote both documents, it never chooses section numbers, and its answers are checked against a fixed format. Figures and tables it cannot read are flagged for a person to review.
You can upload Word (.docx) and PDF files. Reports can be downloaded as Word, Excel, PDF, CSV or JSON.
No. Matching runs on the GapexAI server with a local embedding model. Only matched pairs of sections are sent to the language model, one pair at a time.
Full means the section is unchanged or only reworded. Part means something specific changed, such as a number, a deadline or who is responsible. Not means the section is new in the latest version or was removed from it.