Skip to main content
Treat generated work as a starting point for review. Athena can organize ideas quickly, but you remain responsible for deciding whether the result is accurate and appropriate for your Project.

​
Review an answer

Before acting on an answer:
  1. Check that Athena understood the question.
  2. Compare important claims with the relevant Project Sources or artifacts.
  3. Look for assumptions, missing information, and overly broad conclusions.
  4. Ask a follow-up question if you need a different level of detail or a different audience.
When a claim matters, ask Athena to show the reasoning, identify the assumption, or point to the supporting Source.

​
Review a proposed Project change

When Athena suggests changing Project content, the chat shows the proposed update separately from the conversation. Before accepting it:
  1. Read the explanation for why the change was suggested.
  2. Compare the proposed wording with the current Project content.
  3. Edit the proposed fields when the review card allows it.
  4. Select Accept only when the change is ready to apply.
  5. Select Reject or cancel the proposal when it should not change the Project.
Do not assume that asking for advice changed the Project. A Project change happens when an authorized member accepts the proposed update.

​
Review newly generated work

For a new artifact, document, presentation, or other output:
  • Confirm that it answers the request you made
  • Check names, numbers, dates, and audience assumptions
  • Remove claims that are unsupported by the Project context
  • Compare the result with existing Project artifacts so you do not create conflicting versions
  • Rename or refine the output if the purpose has changed
If the result is not right, explain what to keep and what to change in a follow-up prompt. Use update or revise when you want Athena to work from the existing result.

​
Review shared work with your team

In a Group chat, make the review visible to the people who will use the result. Ask teammates to challenge assumptions or identify missing context before an Editor accepts a proposed Project change. Archived Group chats remain available for reference, even though they cannot receive new messages. Private chats can be reopened from your own chat history.

​
Keep reusable evidence in the right place

If a generated result depends on a document the team will use again, add that document to the appropriate Project or Workspace Source rather than relying only on a chat attachment. See Upload and organize Sources. For the difference between an answer and a Project change, see Asking, creating, and modifying.