Tool
Forms Recognition template library analyzer
Paste a list of Forms Recognition templates with supplier, author and last-modified date. Get counts, ownership concentration, stale templates, coverage gaps.
What this tells you
A Forms Recognition template library is years of supplier-specific knowledge: which supplier sends which layout, where the fields sit, what validation applies. Before that knowledge is carried into a 14c estate or re-expressed in a different extraction approach, you need to know what is there, who maintains it, what has gone stale and where coverage has gaps. Paste the template list, and the active supplier list if you have it, and this tells you. Nothing leaves the browser.
The template library
One per line: template, supplier, author, last modified. Comma, tab or semicolon separated; a header row is recognised.
One per line, from the ERP supplier master. Enables the coverage check.
Templates last modified before this are listed as stale.
How to read the result
Top author share is the key-person figure
A library where one author holds most of the templates is a library that one departure can strand. Above about half is the point to start pairing and documenting.Stale plus not-active is the retirement list
A template that is old and belongs to a supplier no longer on the master is a candidate to drop before the migration, not carry through it.Missing coverage is where the verifier queue comes from
Active suppliers with no template are being handled by a generic template or by hand. That is the work an extraction change would remove first.Several templates for one supplier deserve a look
Header and line templates are normal. Three variants for one supplier usually means layouts changed and the old ones were never retired.
The full project analysis
The list tells you the shape of the library. The project export tells you what the templates do. Reading it adds the field coverage matrix (which fields each template extracts, confidence thresholds, validation rules, and inconsistencies between templates that look alike), a per-template estimate of verifier review load, a supplier-master cross-reference, and a rating of how cleanly each template’s rules carry forward, whether into a 14c Forms Recognition estate or a different extraction approach.
Background: Forms Recognition explained · Forms Recognition options at the 12c boundary · WFR versus OCI Document Understanding
Questions
What do I paste?
One template per line with the template name, supplier, author and last-modified date, separated by commas, tabs or semicolons. A header row is recognised (template, supplier, author, last modified) and the columns are matched by name; without a header the columns are read in that order. Dates in ISO form (2024-06-18) are safest. The active supplier list is one supplier per line.
Does anything leave the browser?
No. The lists are parsed in the page and nothing is stored or transmitted. The analysis of a full project export, described below, is a separate request handled under a written engagement.
What counts as a stale template?
One whose last-modified date is older than the threshold you set, three years by default. Stale is a prompt to check, not a verdict: a template for a supplier whose invoice layout has not changed can be old and correct. A stale template for a supplier that is no longer active is the one to retire.
What does the full analysis add?
The project export itself is read: field definitions, confidence thresholds, validation rules and sample-document references per template. That gives a field coverage matrix, a per-template estimate of verifier review load, and a rating of how cleanly each template’s rules carry forward into either a 14c Forms Recognition estate or a different extraction approach. It is available by request; use the contact form and mention Forms Recognition.
Put the estate in front of an engineer.
Tell us the versions, the components and the integrations. You get a straight answer on what the estate needs, what it does not, and what order to do it in.