The creation of an RFP Response is a two-step process. In step one, you select a Public RFP, which forms the basis for the RFP Response. In step two, you actually create the new RFP Response.

Please note that Public RFP and RFP Response are two separate files that are not directly associated with each other. The RFP Response references the Public RFP via a document-interal identifier, but the Public RFP does not contain any references to RFP Responses, which is because a Public RFP is considered immutable after approval.

When you create a new RFP Response, you will see a new Document Detail tab appear. All Requirements that have not yet been assigned a Requirement Fulfillment Grade and have not been verified are clearly marked with a graphical symbol.

To assign Requirement Fulfillment Grades to Requirements, just go through the Requirement nodes in the RFP Tree and select the suitable Requirement Fulfillment Grade from the drop-down list. 

You will notice that there is a "Verified" check box, which you or some other person can tick. The "Verified" indicator helps make sure that Requirement Fulfillment Grades are consciously assigned.

It might be a policy of your organization that always two persons need to agree on Requirement Fulfillment Grades. In such case, it may be desirable to install the Evaluator's Application Suite (EAS) on multiple computers. When the first person is done with creating the RFP Response, the second person opens the RFP Response and performs verification of Requirement Fulfillment Grades.

When you save an RFP Response, you should give it a name that you can easily associate with the Public RFP.