Write, analyze, and refine

Last reviewed

Bring rough material to Gideon and ask for an output suited to its audience. Keep the facts separate from the style you want.

Turn notes into a document

Provide the notes, the intended reader, and the desired structure. Ask Gideon to preserve names and terminology. If something is missing, have it mark the gap rather than invent a detail.

Try this

Turn these notes into a decision memo for [audience]. Use: decision, evidence, alternatives, risks, next steps. Keep it under 600 words. Mark missing facts explicitly and do not invent quotations.

Analyze before summarizing

For a spreadsheet or export, start with what the file contains: date range, columns, units, missing values, and duplicated records. Then ask the analytical question. Require the figures behind any conclusion.

Iterate precisely

Quote the section you want changed. Say whether to change tone, structure, length, or substance. A request such as “make the recommendation more direct without changing the figures” is easier to evaluate than “make it better.”

Keep the output

Inspect the final artifact or file and confirm where it was saved. A proposed filename in chat is not proof that a file exists. Open the result, check formatting and contents, and download it when you need a local copy.

What to review

Verify quotations, names, dates, calculations, and any statement that is stronger than its supporting material.

Ask Learn Gideon

Answers from the documentation.

What would you like to know?

Ask a question, find a guide, or get help with your next step.

Enter to send · Shift+Enter for a new line