> ## Documentation Index
> Fetch the complete documentation index at: https://openlayer.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Define intake and risk forms

> Define the intake questions and risk dimensions that projects use across your workspace

This page covers two workspace governance definitions:

* The **intake form** organizes questions into sections. Each project answers
  those questions during registration or from its **Lifecycle** page.
* The **risk template** defines the categories and dimensions used to assess
  each project's risk.

Project name, description, owner, and tags remain project properties. They
appear in a fixed **Project details** card before the workspace-defined intake
sections and cannot be added as intake fields.

## Define workspace forms

Open **Settings › Governance**, which includes **Intake**, **Risk**, and
**Lifecycle stages** tabs. This page covers the first two; see
[Project lifecycle](/docs/governance/project-lifecycle) to configure stages,
requirements, and reviewers.

Workspace admins can start from the **Openlayer template** or from scratch,
organize intake fields into sections, and define risk dimensions and their
descriptions. Workspace members can view these definitions but cannot edit
them.

Openlayer warns you before leaving a tab or page with unsaved changes. A
workspace has no form until an admin defines one; until then, projects show an
empty state on **Lifecycle**.

## Example: Low / High / Prohibited pattern

You can use these surfaces to configure a three-tier risk-classification
pattern. This is one possible workspace configuration, not a built-in
classification or legal advice.

| Pattern element | Configure in Openlayer |
| - | - |
| Intake and risk dimensions | Add screening questions to the intake form. In the risk template, add **Use Case**, **Enterprise**, and **Model** categories with your criteria as dimensions. Projects answer the form during registration or from **Lifecycle**, where the risk scorecard also appears. |
| Low, High, and Prohibited tiers | Define how your team applies the project risk level—for example, scores 1–2 as Low, 3 as High, and 4 as Prohibited, based on the highest dimension score. |
| Requirements and approval | [Scope governance frameworks by risk level](/docs/governance/overview#how-it-works) to apply additional requirements to High projects. Use [lifecycle stages and reviewers](/docs/governance/project-lifecycle#define-the-workspace-lifecycle) for review and approval. |
| Prohibited use cases | Add a workspace-level [evidence-based rule](/docs/governance/evidence-based-rules), such as **Banned AI use cases**, and attach the approved list with the renewal cadence your policy requires. |
| Oversight and documentation | Openlayer has no dedicated HITL, HOTL, or HOOTL field. Record the oversight model in an intake field or evidence-based rule. Use evidence-based rules for model cards, DPIAs, and other required documents. |
| HOTL monitoring | Use [platform rules](/docs/governance/platform-rules) for production tracing, monitoring tests, and alert notifications. |
| Re-classification | Use **Send back** to return a project to an earlier stage, **Lifecycle history** to preserve stage changes, and **Retire** when the project leaves the active lifecycle. |

## Edit forms after projects respond

Removing a field or risk dimension does not erase recorded data. Openlayer
retains historical answers and scores so they remain resolvable.

See [Project lifecycle](/docs/governance/project-lifecycle) to learn where project
teams answer intake questions, assess risk, and use the AI Assistant to draft
responses.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.