How Compliance Mapping Works — Krono User Guide | Krono

[KRONO](/)

Courses

[Map your product](/platform/new)[Services](/services)[Guides](/resources)[Pricing](/pricing)

Free tools

About

User Guide

[Overview](/docs)[Getting started](/docs/getting-started)[How compliance mapping works](/docs/compliance-mapping)[Your documents](/docs/generating-documents)[Tracking certificates, testing & deadlines](/docs/tracking-compliance)[Team & workspace](/docs/team-collaboration)[Pricing & your account](/docs/pricing-and-account)

User Guide

# How compliance mapping works

Figuring out which legislation, standards, and documents apply to your product is a lookup against a structured regulatory database — the same result every time, for every user, with the same inputs.

## A structured, sourced dataset

Product types, markets, legislation, harmonised standards, and document requirements are all stored in a structured regulatory dataset, built from official sources across all nine markets we cover — EU (EUR-Lex), UK (legislation.gov.uk), US (eCFR/FCC/FDA/CPSC), India (BIS/CDSCO/WPC), Japan (METI/PMDA/ TELEC), UAE (TDRA/MOHAP/MOIAT), Hong Kong (OFCA and other regulators), Canada (ISED/Health Canada), and Australia. When you search for your product and market, Krono's reasoning engine resolves every applicable legislation, standard, and document requirement for that specific combination — no questionnaire in between.

## What's in your plan

The regulatory citations, standard references, and document requirements on your plan come directly from the dataset. Every applicable standard and regulation also has its own read-focused view — the Rules tab on your project — where you can browse them at your own pace without them getting in the way of the action plan. See [your documents](/docs/generating-documents) for how you actually produce what's required, in the built-in editor.

## Where this doesn't replace judgment

The reasoning engine tells you what applies structurally — it doesn't replace engineering evidence, test lab results, or a qualified person's sign-off. See [Trust & Methodology](/trust) for the full boundary between what Krono automates and what your team still owns.

[Krono](/)

Courses and books that teach hardware teams EU CE, UK UKCA, US FCC/FDA, and India BIS/CDSCO compliance, plus coverage for Canada, UAE, Hong Kong, Japan, and Australia — with CertifiOS, our compliance platform, and a growing library of guides.

Not legal advice. Always consult a qualified professional for product certification decisions.

### Courses

*   [Browse all courses](/courses)
*   [Course bundles — 50% off](/bundles)
*   [CE Marking Course for Electronics Engineers](/courses/01-ce-marking-for-electronics-engineers)
*   [FCC Certification Course for Hardware Startups](/courses/02-fcc-authorization-for-hardware-startups)

### Books

*   [Browse all books](/books)

### Platform

*   [CertifiOS — Free Compliance Roadmap](/platform/new)
*   [Free Compliance Tools](/free-tools)
*   [Pricing](/pricing)
*   [Consulting Services](/services)
*   [Guides & Resources](/resources)

### Company

*   [About Krono](/about)
*   [For Consultants](/for-consultants)
*   [Trust & Methodology](/trust)
*   [Docs](/docs)

### Legal

*   [Privacy Policy](/privacy)
*   [Terms of Service](/terms)
*   [contact@krono-labs.com](mailto:contact@krono-labs.com)

Supported frameworks

REDEMCLVDRoHSMachineryMDRPPEToysFCCUKCAIC RSSISO 13485\+ more

© 2026 Krono. All rights reserved.

Data sourced from EUR-Lex, European Commission, FCC, legislation.gov.uk, India BIS/CDSCO, and official government publications across all nine markets we cover.