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

# Get a cited answer from your files

> A saved answer with a source for every row and unclear terms marked for review.

<Frame caption="Athena 101 · Lesson 03 · Get a cited answer from your files">
  <iframe src="https://player.vimeo.com/video/1233480916?h=7ccc29d035&title=0&byline=0&portrait=0&dnt=1" className="w-full aspect-video rounded-xl" frameBorder="0" allow="autoplay; fullscreen; picture-in-picture" allowFullScreen title="Athena 101 · 03 · Get a cited answer from your files" />
</Frame>

<Accordion title="Transcript">
  Ask about your own contracts, and get a table where every row points to its page. Here's what you'll learn.

  First, a chat that can read and save documents. Click New chat. Then open Tools, and turn on Document. The Tools count goes up. Athena can now read your contracts and save what it finds. If Document is already on, skip this step.

  Name the exact files, and you know which ones the answer comes from. Type @ and the start of a name, then pick the Harbor Line contract. It becomes a chip. Add the other two the same way. Then say exactly what you want back: which contracts auto-renew, the notice period, and the clause behind each. Ask it to flag anything unclear, and not to fill gaps. Send it. Athena reads each contract before it answers.

  You get a table, and every row shows the page it came from. Harbor Line renews, with sixty days' notice. Summit Haulage doesn't renew. One row is marked unclear. Lakeside's contract renews, but the notice period isn't where you'd expect. That flag is the useful part. It tells you exactly where a person needs to look.

  When a row matters, you can check it against the contract in seconds. Hover the chip to preview the page. Click it, and the contract opens right where Athena found it. Read the clause yourself. Here, the notice period is in section 9.4. Tell Athena, and it updates the row with both pages cited. A citation shows you where to look. Whether it's right is your call.

  Keep the table as a document, and keep the chat for next time. Ask Athena to save the table as a document. It opens beside the chat, with its citations, so anyone you share it with can check the same clauses. The conversation stays under Sessions. Open it next quarter, and ask what changed.

  Quick check. A row is cited to page four. Does that prove the term is correct? No. It shows where to look. Open the page, and check.

  Here's how a legal team uses this. They check renewal and termination terms across a set of agreements. Athena returns a cited table and flags the clauses that don't say what you'd expect, so a lawyer reviews those first.

  Now try it with two of your own files. When it works, every row has a chip, and you've opened at least one to check it.
</Accordion>

## Before you start

Upload these files from the [Northwind starter kit](/docs/athena-101/starter-kit): The three PDFs in **Contracts**.

File upload and citations are enough for this lesson.

## Steps

<Steps>
  <Step title="Start a chat">
    Start a new conversation ready to read files and save a document. Skip any setup already completed in your workspace.
  </Step>

  <Step title="Name the files">
    Type @ and select each contract. Ask which contracts renew automatically, what notice they need, and which clause says so; ask Athena to flag unclear terms.
  </Step>

  <Step title="Read the cited answer">
    Check that each row links to its source. Start your review with any terms marked unclear.
  </Step>

  <Step title="Check a clause">
    Open a citation and read the clause yourself. If another clause supplies the missing term, ask Athena to update the row and cite both passages.
  </Step>

  <Step title="Save and return">
    Ask Athena to save the answer as a document with its citations. Reopen the conversation under **Sessions** when you need to review it again.
  </Step>
</Steps>

## Try it

> From @\[file] and @\[file], list \[term] with the clause that states it. Cite each row, flag anything ambiguous, and don't guess.

Look for a citation on every row, and a source you have opened and checked.

## Next

[Work as a team in a Project](/docs/athena-101/04-team-project)


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