Look at what they add by hand. Those columns are the question your meeting actually asks, and your reporting does not answer it yet. Build them into the system instead.
#RevOps
The person making the file is doing the sensible thing. A meeting needs a pipeline that sits still while people argue with it and that anyone can change in front of the others. A report shows everyone the same thing and keeps moving while you read it.
Start narrow. Pick one question your team argues about, and give one person last quarter's losses to read for that question alone, writing what they find onto the deal records in a field anyone can filter.
#RevOps
So the only summary that reaches your CRM is what a rep typed between calls, for whoever reads the deal next week. Your quarterly review runs on that while the actual conversations go unread.
A real check uses records that already exist, run by the people who will live in the system. Put your last ten closed deals through it, first contact to signature, and watch where they get stuck.
#RevOps
Skip it and nothing breaks on the Monday. People find the gaps one at a time while doing real work, and within a few months the team's opinion of the system has settled out of surprises nobody wrote down.