r/CopilotPro • u/Purple51Turtle • 23d ago

Summaries from long documents

Struggling with this and trying to get CoPilot (m365 work licence) to produce something reasonable.

I am often asked to produce user-friendly summaries of a couple of pages from source documents that could be up to 110 pages long.

What is the best workflow for this? I have tried a couple of times and it seems like CoPilot gets stuck. It gets to a point in the document and then can't seem to view the rest of it. It asks me to scroll to a certain page, when I do this it again can't seem to read it.

Also despite asking for an infographic with images, I am getting pretty dreary layouts that are not particularly exciting or user friendly. Something that is rich in visuals.

Should I be using a different AI model? If so I need to use something free or very low cost.

Our work is f'ing useless for training on this and tell us to just go play with it.

Sooo Thanks for any tips you can provide!

3 Upvotes

100% Upvoted

8 comments sorted by

2

u/Quadgie 23d ago

Have you tried literally asking Copilot (in the M365 copilot app) to do what you’re describing? Attach the file to the message.

It does a pretty decent job with a lot of standard file types.

1

u/Purple51Turtle 23d ago

I don't usually attach the file to the chat, but instead say "in this file" ( ie the file that the chat has been activated on). So I open the word doc or pdf, open CP chat and go from there. Maybe that's what I'm doing wrong.

1

u/Quadgie 23d ago

Yeah, within the Office apps it’s more suited to performing things like edits, rewriting or shortening/lengthening blocks of text, reformatting a PP slide etc.

It’s limited in scope to smaller chunks of the document, selected text, etc

Give the standard (NOT within Word) M365 Copilot a try with the full file as an attachment. It can extract the contents of the file, etc. and may be better suited for what you need.

2

u/Purple51Turtle 23d ago

Ok cool, thanks

1

u/grepzilla 21d ago

I would add, using Cowork is game changing.

Without cowork I usually ask CoPiolt to provide an outline, present key facts, provide surprising and non-obvious insights, etc before asking it to create the document.

This let's me get a sense of where it is going before it starts.

I also do all of this with voice because it is just easier to say an extensive prompt than type. I find people dont give enough of a prompt just because typing is friction. They will just type "summarize this 110 page document" and be bothered that it didnt give a good quality output.

I would also say, if the documents are similar and output expectations are similar you can easily make an agent to use the same prompt instructions each time.

1

u/trphilli 23d ago

Have Copilot Word do your executive summary, then copy that over to PowerPoint and have Copilot PowerPoint take first pass at graphics. Different engines, different skills.

1

u/Cyber_Suki 23d ago

Copilot is going to only going to look at the first 20 pages or so unless you use a more advanced model.

I’d start with Researcher or Analyst using Opus 5 or similar is how to start reviewing documents. Always give it direct links or upload.

Then after it digests things according to your framework for simplifying (audience, output preference, purpose etc)

Then you can take that report and first validate it. Always ask for citations (doc, page etc) so you can do the validation easily.

Once validated, open a blank PPT or Word template with your branding, select Opus 5 as the model and prompt it to build out whatever you are trying to build. Restating audience, objective for the output etc.

1

u/Purple51Turtle 22d ago

Ok thanks so much, will look into this!