> For the complete documentation index, see [llms.txt](https://guide.scribe.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.scribe.gov.sg/guides/generate-summaries/summarise-by-sections.md). # Summarise by Sections Create summaries structured around topics you care about. Best for any one-off conversation. Generate Summaries **By Sections** when you want a summary structured around specific topics. ### How do I generate a summary by sections? 1. Go to your session’s page. 2. Click `Generate Summary`, then `By Sections`.

3. Fill in your description, section headers, summary style and custom instructions.

4. Click `Generate`. ### Generating more effective summaries Every time you generate a summary by sections, you'll be able to set four things: the description, section headers, summary style and custom instructions. The more specific you are with each, the closer the summary will be to what you need.

Use the tips below to write each one. A bit of trial and error is normal! Don't be afraid to generate a couple of summaries with different configurations until you find something that works for your needs.

	Setting	What is it?	Tips & Examples
1	Description	A 1 or 2-line summary on who was in the conversation and what it was for.	Guide: How would you tell a new colleague what your last conversation was about? Tip: Multiple speakers? Specific meeting goals? Add them in to give Scribe more context Example: I am leading a meeting with two colleagues, Sarah and John, to review project A's progress. I am a social worker speaking to a client, Adam, for an intake assessment.
2	Headers	The topics you want Scribe to structure your summary around.	Guide: How would you have structured your notes if you were writing them yourself? Base your headers on those topics. Tip: Specific headers work better than general ones. For instance, “budget concerns for next quarter” would work better than just "budget". Examples: Blockers for project A's launch Feedback on the current onboarding process
3	Summary Style	Settings for your summary's format and detail level	N/A
4	Custom Instructions	Free-text instructions to further customise how you want Scribe to write your summary.	Guide: How would you ask someone to write in the style you need? Tip: You can tell Scribe to apply an instruction to the whole summary or only to specific sections. Example: When action items are mentioned in the summary, include the assigned person’s name and the agreed due date as a sub-bullet.

### Learn more


Reuse your favourite description and headers across sessions.	Save to Favourites
Start from the description and headers set up for your role.	Switch your Default

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guide.scribe.gov.sg/guides/generate-summaries/summarise-by-sections.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.