I Put Together Prompts for Summarizing Internal Documents

I shared with my team the prompts I use to summarize meeting notes and planning documents, and the response was good, so I'm posting them here too. It worked well regardless of whether the model was GPT or Claude.

The basic framework is as follows.

  • Role: You are a PM with 10 years of experience.
  • Goal: Summarize the document below into 3 categories (key decisions / issues under discussion / next actions).
  • Constraints: Never add anything not in the original text. If uncertain, write "not specified in the document."
  • Format: Within 2 lines per item, as bullets.

The most effective part was the single line "Do not add content that isn't in the original text." Without it, the model makes up plausible action items on its own.

Also, if the document is long, don't just put it in all at once; splitting it by chapter, summarizing, and then re-summarizing the summaries was much more accurate. Once it goes over 30 pages, it tends to forget the earlier parts.

One caveat: never upload documents containing personal information or HR-related documents. Make sure to check your company's internal policies.

by 데이터덕후296

5 answers

This is all great, but the personal information point needs more emphasis. If you just say that checking internal company policy is mandatory, people can easily skip past it. Our team made it a rule to only circulate masked copies for summarization and never upload the originals. For documents containing names, salaries, or review comments, no matter how good the summarization prompt is, uploading them is game over.

by 알고리즘고수938 · ▲0

Agreed. Without the "don't add anything that isn't in the source" rule, it literally writes fiction lol. It even makes up a point person who wasn't in the meeting minutes.

by 프롬프트장인156 · ▲0

Well, saying it 'worked fine no matter the model' is a bit... Even with the same prompt, summarization styles differ quite a bit from model to model. Especially in the number of bullets or how polite speech is handled, there were differences. What's your take on that?

by 월급루팡399 · ▲0

I agree with splitting it by chapter. I go one step further: when summarizing each chapter, I have it extract only 'items decided in this chapter,' then aggregate everything at the end, and that approach missed the fewest action items. Because things can get blurred again during re-summarization, I paste the intermediate summaries as-is and add one more constraint: 'Only remove duplicates; do not add anything new.' It's a bit cumbersome, but for planning docs longer than 30 pages, this turned out to be the answer.

by 밤샘코더566 · ▲0

Role assignment is actually surprisingly important. Swap '10-year PM' for 'newbie' and it suddenly starts summarizing everything vaguely lol. It's fascinating how perspective shows up in the output.

by 취준생김씨938 · ▲0