- What does Section 16 Agent do?
- It drafts Section 16(a) beneficial ownership reports (Forms 3 and 4), including footnotes, for filing with the SEC. Transactions are described in plain English; the app returns a filing-ready draft for review.
- How does it work?
- A combination of deterministic rules and AI. Issuer and filing data are pulled from SEC EDGAR where available, AI interprets the submitted plain-English description, and rule-based checks keep every field within EDGAR's formatting requirements. Nothing is exported until the filing team reviews and finalizes the draft.
- What's the main feature?
- Section 16 Agent leverages a tightly controlled, AI-powered algorithm to generate Forms 3 and Forms 4. It replaces the old, tired, and manual process by asking the user simply: What transaction(s) took place? A single click then generates a print-ready PDF or complete EDGAR submission package for the user's review. It handles multiple transactions, derivative securities, holdings rows, and even suggests transaction-specific footnotes. The goal: make Section 16 compliance effortless.
- How is customer information protected?
- All data is encrypted in transit and at rest. Every session is authenticated, and each organization's workspace is isolated so its information is visible only to its own team. During the beta, access to the application is limited to invited teams.
- Is customer data used to train AI models?
- No. AI processing runs on Amazon Bedrock within an AWS environment controlled solely by Section 16 Agent, under an enforced zero-retention configuration: inputs and outputs are never stored, never used to train any model, never shared with the model provider, and never accessible to a human operator. Every AI call in the application routes through a single enforcement point, so no stage of the pipeline can bypass that policy.
- Where do submitted transaction details reside?
- Within the filing organization's workspace, and nowhere else. Details of an insider transaction can be material non-public information before the filing is made, so the application treats them accordingly by default and keeps the retained footprint deliberately small. The submitted description is carried into the draft so that the preparer can verify the generated form against the original wording. That draft is the requested work product and remains under the organization's control. Everything surrounding it is short-lived: footnote working data clears within 24 hours, unsaved drafts within 30 days, and pipeline records retain only job status and CIKs, never the description itself. Forms saved to History persist until the organization deletes them, and deletion is complete, removing the document, its prior versions, and the underlying record. All data is encrypted in transit and at rest, and scoped so that it is visible only to the organization that created it.
- Does Section 16 Agent file with the SEC on the filer's behalf?
- Not yet. Section 16 Agent produces the EDGAR-ready submission package; the filing team submits it through EDGAR or an existing submission platform. Direct filing support is planned.
- Why use it over an existing process?
- Speed, accuracy, and less repeated work. Drafting that takes an hour of careful manual entry takes seconds, boilerplate like footnotes and reporting-person details are reused instead of retyped, and formatting rules are checked automatically.