Awamer
Task paths

Turn documents into a deck and executive report

Extract evidence, frame a decision, then prepare a report and presentation for review.

Final deliverable: An evidence log, executive summary, slide content, and source and number checks.

4 steps · Content reviewed:

Ad Meqyas AI

Meqyas AI helps individuals and organizations measure AI readiness, then move from diagnosis to a practical adoption roadmap.

Measure your AI readiness

Copy the prompt to a tool of your choice, then paste its result here. This path does not run an AI model automatically. Saved only in this browser on this device, with no account sync. Download a backup before clearing browser data or moving devices.

1. Extract evidence

Ready prompt

Extract facts into a table: fact, number and unit, source and page, and conflicts or gaps. Do not add facts outside the text. Separate actual numbers from forecasts.
Example result

Examples are editorial illustrations using fictional data, not published tool benchmarks or actual client results.

Example inputs

Operations report, p2: 120 tickets handled in week 1 and 150 in week 2. Page 3: response time was not measured.

Expected example output

Week 1 tickets | 120 tickets | Operations report p2 | Actual. Week 2 tickets | 150 tickets | Operations report p2 | Actual. Response time | Not measured | Operations report p3 | No speed improvement can be inferred.

Success criteria

Editing a step sends later steps back for review while keeping their results.

2. Write the executive summary

Ready prompt

Write an executive summary from the evidence log: context, key facts, implications, limitations, and required decision. Show the formula for derived percentages and do not claim unproven causes. Keep source references.
Example result

Examples are editorial illustrations using fictional data, not published tool benchmarks or actual client results.

Example inputs

Audience: operations manager. Decision: do we need another support employee? At most 100 words.

Expected example output

Handled tickets rose from 120 to 150 between the weeks (operations report, p2): a 25% increase = (150−120)÷120×100. Response-time data is unavailable (p3), so volume alone cannot justify hiring. Measure workload, backlog, and response time before deciding on team size.

Success criteria

Editing a step sends later steps back for review while keeping their results.

3. Prepare slide content

Ready prompt

Turn the summary and evidence into a slide outline: takeaway title, a few points, suggested visual, speaker notes, and sources for each slide. Keep facts distinct from proposed decisions.
Example result

Examples are editorial illustrations using fictional data, not published tool benchmarks or actual client results.

Example inputs

Four slides in five minutes for the operations manager.

Expected example output

1. Handled volume increased: 120 then 150 tickets; two-bar chart; p2. Notes: compare equal one-week periods (1 minute). 2. A 25% increase does not establish speed: show the formula; p2–3. Notes: distinguish volume from response time (1 minute). 3. Measurement gaps: response time is unmeasured (p3); backlog data was not supplied. Notes: explain the missing evidence (1 minute). 4. Proposed decision: measure workload before choosing team size; inference based on p2–3. Notes: request approval for measurement, not immediate hiring (2 minutes).

Success criteria

Editing a step sends later steps back for review while keeping their results.

4. Audit the report and deck

Ready prompt

Compare the report and slides to the evidence log. Check numbers, units, periods, sources, and language. Provide corrections, final report text, and a slide formatting checklist. Do not claim visual readiness without checking the deck in a presentation tool.
Example result

Examples are editorial illustrations using fictional data, not published tool benchmarks or actual client results.

Example inputs

Slide 1 was changed to “Support speed improved 25%”. Deliver report text and slide content.

Expected example output

Correction: replace “Support speed improved 25%” with “Handled ticket volume increased 25%”; response time was not measured. Final report: tickets handled rose from 120 to 150 (p2), an increase of 25%. Response time is unmeasured (p3). Collect workload and backlog data before a hiring decision. Before delivery: move content into the presentation tool; inspect text direction, chart clarity, and sources on each slide.

Success criteria

Editing a step sends later steps back for review while keeping their results.

You have completed the path. Download your results and review them before final use.

Helpful resources