> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/review-workflow/exports/cer-builder.md). # CER Builder Learn how to use CER Builder. Clinical Evaluation Report submissions under [EU MDR 2.7.1 Rev 4](https://ec.europa.eu/docsroom/documents/17522/attachments/1/translations/en/renditions/native) require documented evidence of how literature was identified and screened. CER Builder exports that documentation directly from your nest's Search and Screening activity, already formatted for inclusion in a [CER submission](https://eumdr.com/clinical-evaluation-process/) — so you're not manually reconstructing a search log or screening record from scratch. Download Critical Appraisal exports from [Download from Inspector.](/review-workflow/study-inspector/download-from-inspector.md) **Where this sits:** CER Builder is a toggle on the same page as [Custom Tables](/review-workflow/exports/custom-tables.md), not a separate menu item. Select **Export** from the **AutoLit** menu, then select **CER Builder**.

The CER Builder option on the Export page. — Select CER Builder on the Export page to configure a literature search or screening export.

### Literature Search Export This export documents your search strategy: the search engines used, the specific queries run, the total records returned by each, duplicates found, and the number included and excluded from each search, alongside any studies [Other Sources.](/review-workflow/literature-search/other-sources.md) Select **Literature Search** from the dropdown, choose **.docx** or **.xlsx**, and select **Download**. Searches are listed chronologically by when they were first run in your nest. The duplicate column reports, for each search, the number of records that duplicated studies already in the nest — that is, studies already returned by an earlier search. ### Screening Export This export documents your screening record: every study screened in the nest, with full citation information, links to full texts, screening status, and — where excluded — the exclusion reason. Tags can also be included as columns. Select **Screening** from the dropdown, choose **.docx** or **.xlsx**, and select **Download**. By default, the table separates citation information into **Authors**, **Title**, and **Year** columns. To consolidate these into a single **Reference** column instead, open **Advanced settings** and check **Consolidate citation columns** before downloading. **Note:** this Advanced settings panel is specific to CER Builder and only affects citation formatting — it's a different setting from Custom Table Export's Advanced toggle, which controls whether tag columns split across workbook sheets. ### FAQs

Do I need a separate menu item to find CER Builder?

No — it's a toggle on the **Export** page, alongside **Custom Table Export**. Select **Export**, then select **CER Builder**.

Can I include tags as columns in the Screening export?

Yes — tags can be added as columns the same way they're available elsewhere in export tables.

Which format should I choose, .docx or .xlsx?

Either downloads the same underlying documentation. Choose based on your CER submission's required format — a Word document for direct inclusion in a written report, or a spreadsheet for further filtering or analysis.

### Next Steps


Custom Table Export	Build a custom table from selected studies.	Custom Tables
Download from Inspector	Export data for all studies or filtered study sets.	Download from Inspector

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nested-knowledge.com/review-workflow/exports/cer-builder.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.