---
title: "Building Screens in Astra"
canonical: "https://help.agiloft.com/space/Astra/545194000/Building%20Screens%20in%20Astra"
format: markdown
---
Use this page to design and build your own screens in Astra. 

There are four ways to build a screen in Astra:

- Build from Scratch
- Copy a Community Screen
- Generate from Contract
- Import Screen Download

> 📝 This page assumes you already have access to an Astra workspace. If you use Astra alongside Agiloft CLM, there is [additional setup required](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/570261517) before you get started using your Astra workspace.

# Building Screens from Scratch

If you know the kind of information you want to extract, you can use Astra to dive right in and build your own screen from scratch.

1. From the Astra web app, click the Screens tab, then click New Screen on the right.
2. Choose Build from Scratch.
3. Add a title and a description. You can also optionally add Labels here by clicking + Add Label.

Next, begin to add standards and questions, also called *elements*, to your screen. It’s usually best to include both types of element, but you can also build screens that use only standards, or only questions.

## Standards

First, add standards you want your screen to look for in a contract. Standards are definitive concepts that the AI can check for, where it’s easy to tell if the contract should pass or fail.

If you want to reuse existing standards from other screens in your workspace, click Browse Library, select the standard, and click Add to Screen. This can save a lot of time. However, if you want to make edits to a standard from the library, duplicate it first and make the changes to your local version; if you change the original element, your changes apply to every place that element is already being used, which might cause unexpected results for others in your workspace.

To manually create new standards for your screen:

1. Click + New Element and select Standard.
2. Optionally, add a topic by clicking + Add topic.
3. Enter your standard in the Rule field. This field is used as a text prompt for AI. For example, you might enter, "The term of the confidentiality period should not exceed 3 years." When Astra analyzes a document with this screen, it will check the confidentiality period and pass or fail this standard based on your expectation.
4. Next, choose how to handle cases where the contract doesn’t have the information you’re looking for. You can automatically mark the standard as Always Pass, Always Fail, or let Astra decide.
5. Click Create.

Now that your standard has been created, review the remaining sections. These are optional, but they improve the quality and reliability of your standard.

1. At the top of the standard, click Risk Configuration drop-down, which is how to indicate the importance this standard has to your organization. Choose High for critical issues and Low for issues that allow more flexibility.
2. Under the Rule field, you can click Add Context to give the model more information to understand your rule with.
3. Now, you can move down to the other sections. If you want to apply redlining based on this standard, fill out the Redlining Configuration section:
  1. In the Preferred Language field, you can optionally add example text showing the information you would like to see in this type of clause. Using the example above, you might enter language that sets a confidentiality period of year.
  2. In the Comment to Counterparty field, you can enter comments that are automatically added to a contract document when standards fail. You can toggle the checkbox to allow Astra to automatically tailor the language to reflect the current contract.
4. In the Reviewer Guidance section, you can optionally add clarification to help a user understand what they might be looking for when it comes to results. There is no limit to what you can add here, but keep in mind that this text will be visible anytime someone uses this screen.
5. Click Save.

### Fallback Standards

After you create a standard, you can assign fallback language to it in the case your organization has multiple points of negotiation for a standard, or you need a quick pivot if the primary terms aren’t accepted. You can add up to three fallback standards to each primary standard. To add a fallback standard:

1. In a screen, click the card of the primary standard you want to add fallbacks to.
2. Click + Add Fallback. If the button is grayed out, check to ensure you have filled out all the required fields in the primary standard.
3. The same window opens as when you create a normal standard, so input that information as usual.
4. When you’re done, click Save.

When you’ve added multiple fallbacks, you can sort the order you want them to be triggered in by clicking and dragging each fallback in the primary standard card.

![image-20260902-224414.png](media://1256c0ce-8951-4bfa-84b4-898fc465667b)

## Questions

Next, add Questions you want your screen to answer. Questions should help give you context about the agreement as you are reviewing it.

If you want to reuse existing questions from other screens in your workspace, click Browse Library, select the question, and click Add to Screen. This can save a lot of time. However, if you want to make edits to a question from the library, duplicate it first and make the changes to your local version; if you change the original element, your changes apply to every place that element is already being used, which might cause unexpected results for others in your workspace.

1. Click + New element and select Question.
2. In the Question Text field, enter your Question. This box is used as a text prompt for AI. For example, you might enter, "What is the stated purpose of the agreement?"
3. Click Create.

Now that your question has been created, review the remaining sections. These are optional, but they improve the quality and reliability of your question.

1. At the top of the question, you can click + Add Context to add clarification to help the model provide you with more accurate information. An example might be: "Look for the clause that describes the purpose of the agreement. If one exists, copy the purpose verbatim. If the contract is silent on this question, state the following: There is no defined purpose."
2. Now, you can move down to the other sections. Under Answer Format, choose the amount of data points you want the question to return, along with your preferred output type. If you select a single String data point, you can choose whether the text in your answer is long or short using the conditional option that appears. Selecting multiple data points opens an area where you can add information about each data point individually.
3. In the Reviewer Guidance section, you can optionally add clarification to help a user understand what they might be looking for when it comes to results. There is no limit to what you can add here, but keep in mind that this text will be visible anytime someone uses this screen.
4. Click Save.

The video below shows you the process of creating a screen from scratch.

# Building Screens with Community

You can use standards and questions from the Astra community in your own screens, or copy full screens from the community to your workspace. You can find the community library at screens.ai/community to look for screens you might want to borrow from. 

Before any Community Screen is published, Agiloft subject matter experts validate the accuracy by thoroughly testing it across a diverse set of relevant contracts. Community Screens can be updated at the request of the author, but it’s much easier to copy the screen and make the changes yourself.

> 📝 Although this provides significant flexibility, some parts of community Screens are not viewable or editable, even when added to your Screen.

To copy a whole screen from the community into your workspace:

1. Go to [screens.ai/community](https://www.screens.ai/community).
2. Choose the screen you want to import and click Get Screen. This screen is now available for selection in the Screens tab of Astra.

To borrow standards or questions from the community and add them to your own screens:

1. First, create or open a screen:
  - If you want to build a whole new screen, first use New Screen on the Screens tab to start building a new screen from scratch.
  - Otherwise, go to Screens and open the screen you want to edit.
2. Now, with the screen still open, go to [screens.ai/community](https://www.screens.ai/community).
3. Browse the community page or search for specific contract types or other legal concepts to find a suitable screen. When you find a screen you want to borrow from, click it to view details about who it was designed for, its purpose, and any known limitations and assumptions.
4. When you've made your decision, click Get Screen.
5. Select standards and questions from the community screen and add them to your own screen:
  1. Choose a standard or question.
  2. Click the three-dot menu to the right of the element.
  3. Click Copy to Screen.
  4. Select your screen and click Copy to Screen.
6. Continue adding data until you've finished building your screen.

The video below walks you through how to use Community screens.

# Building Screens from Documents

Sometimes, the quickest way to build a Screen is using an example document to indicate what you’re looking for.

1. Open the contract document you want to use as the template.
2. In the text body of the contract, add double brackets before and after any text information you'd like to be turned into a standard or question.
3. Save the document.
4. Log in to Astra and go to the Screens tab.
5. Near the top of the page, click New Screen and select Generate from contract. The playbook generator currently caps at 50 standards per generation. For contracts with more than 50 standards, the recommended workaround is to either:
  - Reduce the number of bracketed clauses
  - Split the document in two, generate two screens separately, and then combine them. You can combine them manually by copying standards between screens, or use ChatGPT to merge the downloaded ZIP files.
6. Click Upload Document. Add the file you just bracketed and wait for it to upload. Then, click Continue.
7. The next modal gives you some options, such as whether you want to designate which party you represent in the contract, such as Vendor, Supplier, etc. You can also add custom instructions.
8. Click Generate Screen. This may take up to a few minutes.
9. Once the Screen is done generating, review the generated title and description, as well as the standards created from your bracketed sections. Make any modifications to add specificity or guidance.
10. Click Save.

The video below shows you how to generate screens from a document.

# Prompt Best Practices

Every screen uses prompts to tell Astra what information to look for. Creating prompts for AI can be difficult, but the prompts determine the quality of your results.

Your Astra prompts are built in two parts: the main standard or question you enter, and then the details you add. The main element is the core of the prompt being sent to Astra, and the details you add are offered as context to support that prompt. Both fields have very high character limits, but unnecessarily long prompts can also negatively impact model results, so experiment to find the right balance.

Poor examples are vague, while strong examples are designed to break important contextual information into clear chunks of data that can be easily processed by the model. When it comes to AI prompts, remember the four *C*s: Clear, Context, Concise, and Chunky.

| **Poor Example** | **Strong Example** |
| --- | --- |
| Make sure the vendor's liability falls within our usual parameters. | The vendor's liability fees should be capped at ≥ 12 months fees. Damages or claims related to confidential information and the customer's IP should be excluded from the cap. The vendor should indemnify the customer for third-party IP infringement. |

The video below demonstrates some best practices for drafting prompts.