Policies

Importing what you already have

If your firm already keeps its rules somewhere, import them rather than retyping them. Ciev takes an uploaded file, a Google Docs or Sheets link, or pasted text.

A spreadsheet with Name and Rule columns, and optionally severity, keywords, examples and harmless uses, is read as it stands. Anything else, such as your written supervisory procedures, is read for the rules a call or screen share can break, so you can point Ciev at the document you already maintain instead of a list built for a keyword tool. PDF, Word, text, CSV and Excel are accepted, up to 10 MB.

Importing policies

The spreadsheet format

Only two columns are required.

ColumnRequiredWhat goes in it
nameYesThe policy's name, for example Guarantees and promises of results
ruleYesThe rule in plain words, as you would explain it to a new reviewer
severityNohigh, medium or low. Defaults to medium
termsNoKeywords matched exactly, separated by commas
examplesNoExample quotes that should be flagged
exclusionsNoHarmless uses that should not be flagged
omissionNotrue where the policy flags something missing rather than something said
enabledNofalse to import a policy switched off

Headings are matched loosely, so you rarely have to rename anything. name also accepts policy, policy name, title or rule name; rule accepts description, requirement, what to flag or policy text; terms accepts keywords, phrases, red flags or search terms; exclusions accepts harmless uses, exceptions or not when.

A table without a recognisable name and rule column is not treated as a table at all. It is read as a document instead, for the rules it describes.

Example: a spreadsheet

This is a valid import, using headings Ciev recognises without renaming:

Policy NameDescriptionRisk levelKey wordsHarmless usesExamplesOmission?
GuaranteesNever promise returns.Criticalguarantee, risk free; can't lose*guarantee periodYou can't lose.<br>It's guaranteed.
Missing risk disclosurePerformance without risks.yes

What Ciev makes of it:

A sheet with only a keyword column and no rule is not a table Ciev can read column by column. It gets read as a document instead, which usually still works.

Example: a policy document

You can equally import the procedures you already maintain. A clause like:

3.1 Communications. Registered representatives shall not guarantee a customer against loss.

drafts a policy named Guarantees against loss, with the rule "Don't guarantee a customer against loss", high severity, and guarantee as a keyword.

Two things make this safe to trust:

Where a draft overlaps a policy you already have, it is shown as an update to that policy rather than a new one, so importing a manual twice doesn't leave you with duplicates.

Nothing is saved until you have been through the drafts. Each one is added, updates the policy it matches, or is skipped, and you decide which.