TOPIC 05 OF 08

Output format

Shape the result for its use

PLAIN-LANGUAGE IDEA

Specify the form that makes the output easy to inspect and use: a table, email, checklist, JSON object, meeting brief, comparison, or questions-first conversation. Include useful headings, fields, length, and ordering.

SEE IT IN A SITUATION

Return a table with columns for claim, supporting source, source date, confidence, and follow-up needed. Put unsupported claims at the top.

DO NOT MISS THIS

A polished format can make weak information look trustworthy. Structure improves inspection; it does not validate the contents.

TRY THIS NOW

Choose a format that exposes uncertainty and evidence instead of hiding them in fluent prose.

CONNECTED LANDMARKS

a-useful-requestA useful request meetings-and-summariesMeetings and summaries

← PreviousNext idea →

TAKEAWAY TOOL

The Request Brief

Use this when a task deserves more than a quick question. Leave a field empty when it does not help; never add sensitive information merely to complete the template.

01Goal
What should the work help you create or decide?
02Audience & perspective
Who is it for, and which viewpoint reveals useful criteria?
03Context
What minimum background and sources change the answer?
04Boundaries
What must it use, avoid, protect, or leave to a person?
05Output
Which structure makes the result easy to inspect?
06Example & tone
What does good look and sound like?
07Evidence
How should uncertainty, sources, and missing facts appear?
08Human checkpoint
Who verifies, edits, approves, or acts?

◉

Important topics change.

Environmental impact, copyright, privacy, security, and EU obligations require dated sources and context. The Atlas teaches durable decision habits and clearly separates them from legal or professional advice.