linesOfBusiness field inside the PolicyOperationalProfile carries ACORD LOB codes extracted alongside every other policy fact — in the same bounded, source-cited generation call that produces coverage units, dates, and premium. This means classification evidence is traceable to specific source nodes just like any other extracted value.
How Classification Works
The extraction pipeline populateslinesOfBusiness as an array of AcordLobCode values. A single policy can return multiple codes when the document covers a package program.
linesOfBusiness intentionally accepts multiple codes. A commercial package policy covering general liability and business auto will return ["CGL", "AUTOB"] — do not reduce it to a single value in your application unless you have a specific reason to do so.Legacy-to-ACORD Code Mapping
If you are migrating from an earlier version of the SDK, the table below maps every legacypolicyType string to its corresponding ACORD code or codes.
Exported Utilities
Import all classification utilities from thepolicy-taxonomy subpath:
AcordLobCodeSchema
A Zod enum containing all 107 ACORD LOB codes. Use it to validate user input or parse external data before passing it into your application logic.
ACORD_LOB_CODES
A plain array of all 107 ACORD LOB code strings. Useful for populating dropdowns or building filter sets.
ACORD_LOB_LABELS
A
Record<AcordLobCode, string> map from code to human-readable label. Use this to display friendly names in your UI.LEGACY_POLICY_TYPE_TO_LOB
Maps every legacy
policyType string to one or more ACORD codes. Use this during a migration to translate stored legacy values.Utility Functions
- normalizeOperationalLinesOfBusiness
- resolveOperationalProfileLinesOfBusiness
- PERSONAL_LOB_CODES
Accepts an array of raw LOB strings — which may be legacy values, ACORD codes, or mixed — and returns a deduplicated array of valid
AcordLobCode values.