Compliance frameworks
How Banco Central rules arrive on the platform broken down into controls, requirements and evidence, and how your team works each one through to completion.
What it is for
A framework is a regulation turned into a work list. Clav takes a Banco Central rule and breaks it down into the evidence the regulator expects to see, each with an owner, a deadline and a history. The legal content of the frameworks is produced by Paiva Gomes Advogados.
On the platform, frameworks live under the Frameworks menu.
From the rule to the task
Each evidence carries its description, its legal basis and, when there is one, a document template to download.
An owner and a deadline on every item
Assign users or teams at any level, set an internal deadline and follow everything in My work.
Everything recorded
Every upload, completion and assignment becomes an event you can look up by framework and by evidence.
Available frameworks
| Framework | Rule |
|---|---|
| SPSAV: authorization under Resolution 520 | BCB Resolution 520/2025 |
| Authorized institutions under Resolution 520 | BCB Resolution 520/2025 |
| Art. 88: SPSAVs already in operation | BCB Resolution 520/2025 |
| Technical certification | BCB Normative Instruction 701/2026 |
| Reasonable assurance report on AML controls | BCB Normative Instruction 739/2026 |
Who adds a framework
Frameworks are added to your organization by the Clav team. If your organization doesn’t have one yet, or needs another one from the list, get in touch. Each framework can be added only once per organization.
When Clav updates a framework’s content, the change reaches your organization’s copy without any action on your side.
How a framework is organized
| Level | What it is |
|---|---|
| Framework | The whole regulation, with a due date and overall progress. |
| Control | A topic of the regulation, usually a group of articles. |
| Requirement | A concrete obligation within the control. |
| Evidence | What proves the requirement: a document, a list of documents or a form. |
Status rolls up the hierarchy on its own. A requirement is completed when its evidences are, and a control when its requirements are. Each level’s completion rule says whether every item must be completed or one is enough. The framework is completed when all its controls are.
Evidence types
Document
Upload a file with Upload file or attach an HTTPS link, such as a Google document. Uploading a file completes the evidence. A link alone doesn’t: the platform treats it as a reference to work still in progress.
Document checklist
A list of items, each with its own file. In Manage Checklist, you attach a file, a link or a description to each item, and you can add or remove items.
An item counts as resolved when it has a file, a link or a description. If all of them are resolved, the evidence can be completed straight away. If not, the platform asks for a completion reason.
The list is guidance
The recommended items are examples. They don’t cover everything the regulator may ask for and don’t replace your team’s own analysis.
Document annotation list
A single document, checked point by point. First you upload the document. Then you mark each item as complete, with an optional annotation. The evidence can only be completed once the document is uploaded and every item is marked. Progress is saved automatically.
This type can be copied with Duplicate, which asks for a suffix to tell the copy apart from the original.
Information
A form your team fills in on the platform itself, under Fill Information. Fields can be short text, long text, a list of options or a date. Submitting the form completes the evidence, and the answers can be downloaded as a PDF.
The Document and Document annotation list types also accept complementary documents, for attachments that aren’t the main document.
Working on an evidence
Assign owners
At any level, from the framework down to a checklist item, you can assign users or teams. On the framework’s Team and responsibles card, click Manage to choose the owners and set the internal deadline. Whoever is assigned gets an email.
Produce the content
Download the document template, when there is one, then upload the file or fill in the checklist or the form. While you work, set the progress on the slider, which goes up to 99%.
Complete it
100% only comes with completion. Some types complete on their own, such as uploading a file to a Document. For the others, click Mark as completed. If the evidence doesn’t meet everything its type requires, the platform asks for a reason.
If you need to change it again
A completed evidence is locked. To edit it, use Reset status: progress goes back to zero and the work done is kept as a draft.
File versions
Uploading a new file creates a new version, and Version History shows the earlier ones. Restoring an old version creates one more version without deleting the others. Only the two most recent versions are kept, and older ones are removed about 24 hours after being replaced. The file policy guide covers these rules in detail.
Deadlines and risk
Each framework has two dates. The due date comes from the regulation and can’t be edited. The internal deadline is your team’s target and is set together with the owners.
The framework Overview shows progress, the submission deadline and a risk level calculated from both:
| Risk | When |
|---|---|
| High | The deadline has passed, or fewer than 90 days are left and progress is below 50%. |
| Medium | Fewer than 180 days are left and progress is below 70%. |
| Low | In every other case, or when no deadline is set. |
Framework progress is the average progress of its evidences, with completed ones counting as 100%.
Day-to-day tracking
- My work gathers the controls, requirements and evidences assigned to you or your teams, grouped by framework.
- My tasks, on each framework’s Overview, shows only what is yours in that framework.
- In the Annotations tab you comment on a control, requirement or evidence and use @ to mention users or teams. Whoever is mentioned is notified and gets an item in their personal Checklist.
- The Events tab lists everything that happened in the framework, with filters by item, user and team. Each evidence also has its own History.
Reports
Under Reports, you can generate:
| Report | What it contains |
|---|---|
| Framework reports | A PDF covering one framework’s week. |
| Organization reports | A PDF covering the week across all active frameworks. |
| My tasks report | The tasks assigned to you. |
| Review exports | A spreadsheet with one row per attached document. |
| Framework dossier | A zip with one folder per evidence, its files and a PDF with the review history. |
Weekly reports are also generated automatically every Monday. Only organization administrators can generate the dossier, which stays available for 30 days and leaves out files stored with client-side encryption.
Review by a certifier
When the organization goes through certification, evidences can be sent to a certifier with Request review. The certifier approves or requests changes, and you answer with Mark ready for review once you’ve made the adjustments. This flow runs separately from the evidence’s status and requires certification to be enabled for your organization.
If your organization prefers, an administrator can turn on Admin-only evidence review in the settings. Then only administrators and owners can send evidences to review.
Frequently asked questions
Can I create my own framework?
Not on the platform. Frameworks are prepared and added by the Clav team. Get in touch if you need one that isn’t on the list.
What happens to the assignments of someone who leaves the organization?
When a member is removed, they stop being the owner of every framework item and leave every team. Reassign their work first.
Who can delete an evidence?
Only owners and administrators can delete an original evidence. A copy made with Duplicate can also be deleted by whoever created it.
Can AI check my documents?
Yes, if the feature is enabled. AI document review compares an evidence’s files with the requirement and points out the gaps.