Most organisations arrive with a policy set that already exists: a folder of Word and PDF files named like "POL-007_access-control_v3_final (2).docx". Import policies takes that folder as it is. Your own AI reads every document, gives it a clean title, sorts it into a category, works out which framework it serves and which controls it satisfies, and shows you the result in one table before anything is created.
What you need
- A plan that includes Policies: the Basic plan and above. Policies, and with it this import, is not part of the Free plan.
- The Edit permission for Policies. Administrators always have it and the Editor role has it by default. A viewer can open the page and look at an import, but cannot start one, create the policies or cancel.
- Your documents as PDF (.pdf), Word (.docx), text (.txt) or Markdown (.md), up to 40 files of 25 MB each per import. Older Word files (.doc), spreadsheets, images and ZIP archives are refused, as are empty files and files that are not really the format their name says; save a .doc as .docx or PDF first. A scanned PDF without a text layer is accepted but cannot be read: it is named from its file name and gets no control mapping, so use the Word original or a PDF that contains text where you can. For a larger set, run several imports; one person can start up to ten in ten minutes.
- Optionally, an AI connected under Settings, AI (Claude, ChatGPT or DeepSeek, with your own key). Connecting one needs the Manage permission for Settings and, by default, the Professional plan or above, so on the Basic plan the import normally runs without AI. Without it the import still works: titles come from file names, categories from a keyword heuristic, and the control mapping from the deterministic passes (keywords and the crosswalk). In that case there is no summary, language, stated version, date or owner, and no document is unticked for you. With an AI connected, the text of each document is sent to that provider and the usage is billed to your own key; Venvera's own key is never used for this import.
How it works
Open Policies in the sidebar and click Import policies in the page header. A line under the page title tells you whether the documents will be read with your configured AI or, with none connected, from file names and keywords. In the card Add policy documents, click Choose files or drop the files onto the area. Each file is listed with its size; the cross on a row removes that file and Clear empties the list. The list holds 40 files at most and a file already in it is not added a second time, so check the count above it (N documents selected) before you go on. Then click Analyse N documents. Each file uploads on its own, so a slow connection or one bad file never blocks the rest.
The card Reading your documents shows the progress and a status for each document: Waiting, Reading, Ready or Failed. Each document is read in turn. The AI proposes the formal title, a category, the framework the document most directly serves, the language, a two-sentence summary and, where the document states them, its version, effective date and owner. The policy-to-control matcher then runs for that framework: an AI pass, a keyword pass and the crosswalk fan-out to equivalent controls in other frameworks, whether or not your organisation has enabled them. You can leave the page; a notification in Venvera (Policy import ready for review) tells the person who started the import when the batch is ready and opens it. No e-mail is sent. Cancel import stops the import and removes the uploaded files.
The card Review before creating has one row per document, with the columns Document, Category, Framework and Mapped controls: edit the title, change the category or framework, and untick anything that should not become a policy. The Framework list holds the frameworks your organisation has enabled. Under Mapped controls, click N controls to open the list of mapped controls; each one shows where the match came from (AI, keyword or crosswalk), and AI matches also show their confidence as a percentage. The list cannot be changed at this stage; add, remove or move mappings on the policy afterwards. A document the AI considers not to be a governing document (an invoice, a contract) is unticked by default. Titles, categories and ticks you change here are saved only when you create the policies; if you leave the page first, the review starts again from the proposals.
Choose whether the imported policies are created as approved and in force (the default, since these are your existing documents) or as drafts for review: leave Mark these policies as approved and in force ticked, or untick it for drafts. Then click Create N policies; Discard abandons the import instead and removes the uploaded files. The original file is attached to each policy, the control mappings are saved, and the batch is closed. The result card lists the policies created, the number of documents left out and any document that could not be created, with the reason (import that document again). Open policies takes you to the Policies page and Import more starts a new import.
Warnings at review
| Message | What it means |
|---|---|
| Does not look like a policy. Left out by default. | The AI judged that the document is not a governing document. It is unticked; tick it if it is a policy after all. |
| No readable text was found (scanned document?). Named from the file name. | The file has no text to read, typically a scanned PDF. The title comes from the file name, the AI does not read it and no controls are mapped (No controls). Import the Word original or a PDF that contains text instead, or add the controls by hand on the policy afterwards. |
| The AI could not read this document; the mapping is keyword-based. | The AI did not answer for this document. Its title comes from the file name, its category from keywords and its mapping from the keyword and crosswalk passes. Check the row with extra care. |
| Could not be read | A list under the table of the documents whose analysis failed, each with the reason. They are not created; import them again. If no document at all could be analysed, the card says None of the documents could be read: click Discard and start again. |
Recent imports
Under the upload card, Recent imports lists the imports that are still open and those started in the last seven days, ten at most, each with its date, a status and a summary such as "12 documents, 10 created, 0 failed". The statuses are Waiting and Reading (the analysis has not finished), Ready for review, Creating, Created and Cancelled. Open takes you back to an import that is being read, is ready for review or has been created. An import that is ready for review waits in the list until you create its policies or discard it. An import you no longer need is closed by opening it and clicking Cancel import or Discard; it then shows as Cancelled.
Where the import lands
| Result | Where to find it |
|---|---|
| The policy record with its category chip | Policies; the uploaded file is in the policy's Documents panel, and a Word or PDF original is also shown on the page under Policy Document. Imported policies have no Download .docx icon on their row; download the original from Documents |
| The mapped controls | The Mapped Controls section of the expanded policy, where mappings can be added, removed or moved, and the Policies tab of each control, where each policy listed opens that policy on the Policies page |
| Evidence on the mapped controls | An approved policy mapped to a control fills that control's policy-type evidence slot through detected evidence; the refresh is queued at once and otherwise runs daily |
What a created policy contains
- The title, category and framework as you left them at review, and the language the AI detected (English when it is not known).
- Version 1, with the note Imported document in the version history.
- As its text, a short import note rather than the document itself: the date and file name of the import, the AI's summary and, where the document states them, its version, effective date and owner. The policy itself is the attached file.
- The status Approved or Draft, as chosen at creation. For an approved policy the approval date is the date of the import and the person who ran the import is recorded as having approved it.
The version, effective date and owner stated in a document are recorded in the import note only. They do not set the policy's version, its approval date, its Approver or its review date. The next review date of an approved policy is filled in by Venvera within a day: the approval date plus the policy's review frequency (twelve months unless you change it), and never less than 30 days ahead.
Categories
Governance, Risk management, Access control, People and HR security, Asset management, Cryptography, Physical security, Operations security, Network security, Secure development, Suppliers and third parties, Incident management, Business continuity, Compliance and privacy, AI governance, Other. The category is a sorting aid for your library; it does not change how controls are mapped.
Good to know
- If you change a document's framework at review, the note Mapping will be recomputed for this framework without AI. appears. The new mapping is worked out when the policies are created, with the keyword and crosswalk passes only, so the list under Mapped controls on the review screen still shows the controls found for the framework first proposed. Check the result on the policy afterwards, and click Run matcher in its Mapped Controls section to add the AI pass for the new framework.
- Run matcher on a policy, and Map controls in the Policies page header for all policies at once, read the newest Word (.docx), PDF, text or Markdown document attached to the policy. Re-running the matcher on an imported policy therefore works from the document itself. A scanned PDF without a text layer still gives the matcher nothing to read.
- Mappings you confirmed or dismissed by hand on a policy are never overwritten by a later re-match.
- Documents left out at review are deleted from storage. Cancelling an import removes every staged file.
- To undo an import before the policies exist, click Cancel import during the analysis or Discard at review. Once the policies are created there is no undo: delete the unwanted policies one by one on the Policies page, which needs the Manage permission for Policies (administrators have it by default).
- The import does not look for duplicates and never updates an existing policy. Every ticked document becomes a new policy, even when a policy with the same title already exists, and importing the same document twice gives two policies. Untick at review anything you already have in Venvera.
- The AI reads the document text only. It never follows instructions found inside a document.
- For a long document the AI reads the beginning and the end to name and sort it, and the first 24,000 characters to map it to controls. The keyword pass reads the whole text. Controls that a long document covers only towards its end may therefore be missed by the AI pass; add any that are missing on the policy afterwards.
- Import from another platform can also take a ZIP of policy documents, but that is a simpler route: each file becomes a plain draft named after the file, with no AI title, category, control mapping or approved status. Use Import policies when the documents should be named, sorted and mapped. See Import from another platform.