A family of Microsoft word processing software products for creating web, email, and print documents.
I agree with Femi's general outline. I'll try to describe some of the details that it's likely to involve, and some of the issues that will need to be resolved, preferably before you make any concrete effort.
One of the first questions to settle is whether the system for generating the final documents will be used only on one computer or on several or more. If it's only one, then the documents that hold the option paragraphs can be stored in any folder, as long as the code has the path to that folder. If the setup needs to be on multiple computers, especially if some are Windows PCs and others are Macs, it will be simpler to put everything into a single folder -- then the code can just look in "the same folder as the file that contains the code".
You may see some suggestion that the option paragraphs should be stored in Quick Parts (building blocks) in the report template. Although that could make the programming simpler, it would make it more difficult to edit, add, or delete paragraphs. Separate documents, either per option or per paragraph, will make maintenance easier. If you choose to have a document per paragraph, then each option must be identifiable, most likely by being enclosed in a bookmark.
The user interface that Femi mentioned should be a userform, which is a custom dialog box created by VBA code (https://gregmaxey.com/word_tip_pages/create_employ_userform.html). There are a couple of ways to design the userform. One way is to display one dropdown list for each section of the report; each dropdown contains the list of options for that section. Another way is to have one dropdown containing a list of sections; when a section is selected in that dropdown, the list of its options is loaded into a second dropdown. The first way has the advantage that all of the choices of options can be seen at once, but the drawback that a dialog with 10 or 12 dropdowns and a couple of buttons will be rather cluttered. The second way is less imposing, but you'd be able to see the chosen option for only one section at a time; that may require adding a summary display.
Another usability question is how you would know which option to choose for a given section of a report. Each entry in a dropdown is limited to a single line, which may make describing the paragraphs difficult. The userform could have a text area (technically, a label control) that displays some or all of the paragraph that corresponds to the current selection in the dropdown. Alternatively, a "Show" button could call a message box containing the paragraph.
I'll keep an eye on this thread in case you have other questions about the design and the code to implement it.