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

# Turn a long report into a summary for the board

> Upload the report and get a one-page summary, with the numbers behind each conclusion and the points to watch.

**You need:** the report as a file (.pdf or .docx) · **Last updated:** August 16, 2026

## What you'll get

A summary of about one page, written for someone with five minutes: the main points, the numbers behind each conclusion, and a short list of what deserves attention. No jargon, and none of that opening paragraph nobody reads.

<img src="https://mintcdn.com/moradaai-f7bfc739/Jw7bl2COfA6DU5qM/images/morada-os/casos-de-uso/resuma-um-relatorio.png?fit=max&auto=format&n=Jw7bl2COfA6DU5qM&q=85&s=409fbdcea70e70a5ea4d9786ec08457a" alt="Executive summary of a monthly report generated by Morada OS, with numbers and points of attention" width="1280" height="577" data-path="images/morada-os/casos-de-uso/resuma-um-relatorio.png" />

***

## Step by step

<Steps>
  <Step title="Upload the report to the chat">
    A 60-page report just landed and the board meeting is right after lunch. You need to understand the essentials and be able to explain them in five minutes. You open Morada OS, drag the file into the chat, and type:

    Don't have one handy? Any internal report in PDF or Word works for a test run.
  </Step>

  <Step title="Paste the request and adjust the brackets">
    With the file attached, paste the request below and adjust whatever doesn't fit your case.

    ```text wrap theme={null}
    Summarize the report I uploaded. The audience is [audience, e.g. the sales leadership] and the goal is [goal, e.g. deciding whether we move ahead with the project]. Give me a summary of about one page with the main points, the numbers that back each conclusion, and a short list of points to watch. Use plain language, no jargon.
    ```
  </Step>

  <Step title="Get the one-page summary">
    The assistant reads the whole file and returns the summary in the format you asked for, with the numbers carried over and interpreted rather than just listed. Read the points to watch first, since they're usually what the board will ask about. If a number surprises you, ask for the page it came from before repeating it in public: the summary is a reading shortcut, not a pass on checking.
  </Step>
</Steps>

***

## Keep the conversation going

> "Show me which page of the report each of these numbers is on."

> "Rewrite this summary as five bullets for a slide."

> "List the questions the board is likely to ask about this material."

***

## Tips and common problems

* **Say who it's for and what for.** The same report becomes a different summary for the board and for the construction team.
* **Ask for the length you want.** "One page", "ten lines", or "five bullets" changes the result completely.
* **If the file is scanned, mention it.** A photographed or scanned document doesn't always have readable text, and in that case it's worth uploading the original.

***

## Similar cases

* [Analyze a development's feasibility from the spreadsheet](/morada-os/en/use-cases/feasibility-analysis). Also starts from a file uploaded to the chat.
* [Write the announcement copy for a launch](/morada-os/en/use-cases/launch-announcement-copy). Also turns long material into short text.
* **Summarize a document that's already in the Brain** (coming soon). This one needs the document published to the organization's library.