What needs to be specified in the abbreviated version of the TOR (user requirements) in order to be understood by all parties?

Question

JavaScript

Created TOR (user requirements) on 20 sheets for the development of new software. They asked me to make a short version of the document on 1 sheet. The short version will be used during the discussion of the software (customer, programmer, analyst), after reading it, everyone should understand what kind of system, what problems, and what will need to be implemented.
In principle, I understand that the text should be simple so that both programmers and the customer can understand it. The main problem for me is what should be indicated in the document so that it is understood by both the programmer and the customer?
So I thought, and wrote a sample brief description. An example of a large TK is attached.
Purpose: Development of a system for accounting for companies, key persons, marketing work, as well as analytics
Main users: Director, Head of sales and marketing department, employees of the sales and marketing department
Problem: there is no possibility to keep records of customers, view relationship history, analyze historical and current data
Proposal:
1. Implement the possibility of accounting for companies
2. Implement the possibility of accounting for key persons of companies
3 Implement accounting of marketing data
4. Implement the ability to analyze data
5. Implement the ability to configure access rights for certain officials to the functionality:
Clients
of the Company
Marketing events
History of relationships with clients
Analytics
I will leave a link to the sample TK in the form of a separate comment

Answer 1

"Purpose: Development of a company accounting system..." -> Company accounting...
Proposal: Implement the possibility of company accounting, ... -> Implement: company accounting, ...
Implement the ability to configure access rights for certain officials to the functionality: - > [Implement: ] Setting up different rights for different positions....
The language in which the TOR is written is bureaucratic and inhumane, no matter how you shorten it, you still lose the thread by half the sentence. It is necessary to reformulate it into simple, precise and humane phrases.

Answer 2

Requirements can be functional, non-functional, custom, and so on. In the abbreviated version, only functional ones should be left. How to rank requirements by type, this is an hour for you to Wikipedia.

Answer 3

https://drive.google.com/file/d/0B93s4XWkZ-wEck41O...
link to sample TOR

Answer 4

So I thought, and wrote a sample brief description.

Well, add 3-7 lines of description to each of these items and you will have a short version sheet. If the people who will be discussing this understand the subject area and understand what they want, then such a brief description will be more than enough.