Map, Compare, Comply

Three steps onto Reg42.

The three steps

  1. Map

    Connect your policies, controls and evidence from Google Drive, Confluence, Jira and Outlook. Solon builds your compliance graph.

    Communications standards v5Document store
    Chat transcripts, archived dailySupport platform
    Approvals in team chatTeam chat archive
  2. Compare

    Add the rules that apply, in CLHEAR. See what is covered and what is missing.

    Content standards for AI output 2210(d)(1)(A)Covered
    Principal approval of AI-drafted ads 2210(b)(1)(A)Mismatch
    Why: approved in chat by marketing, not by a registered principal
  3. Comply

    Close each gap with a task and an owner. Every approval is kept as proof.

    Route every AI-drafted ad to a registered principalDone
    Approver and date archivedSocial media archive, 22 Oct 2026
    Principal approval of AI-drafted adsCovered

Example data on a fictional firm. The rule references are real.

Ask SolonSee how Solon answers, on a fictional US broker-dealer.

The same steps in the product

Real screens. A fictional firm with synthetic records.

See the product, screen by screen

The Actual program screen: each item the firm runs, the requirement it fulfils, the clause it follows, its status and its evidence.
The Reference blueprint screen: a table of requirements, each with its rule reference, its kind, the policy clause that addresses it, what is in place and its status.
The Gaps and actions screen: each gap with what is required, what the policy says, what happens in practice, and a Fix button.

See it on your own domain

Tell us your domain. We will show you Solon on it.