The Due Date fields are for one-time deliverables or recurring deliverables.
A one time-deliverable can have a fixed due date or due date relative to a life cycle event on the document.
With a relative due date, you can identify a date that is based on a period of time before or after a certain business document event.
For example, 5 days after the contract is signed or 2 weeks after the RFQ is published. In this case, you need to specify both the period of time and the event. For deliverables that have a relative due date, for example 30 days after award, the actual due date will be calculated when the contract on which the template is applied, is approved or signed.
You are not required to provide a fixed due date for a deliverable on a contract template. You are, however, required to provide complete due date information, if the deliverable is a one-time deliverable with a relative due date or a recurring deliverable.
All events related to business documents with the same intent as the template, are available for users to choose while defining a relative due date. Selecting a particular business document event for due date on a deliverable would also make the deliverable specific to that given business document for execution.
Take the example of a due date of 5 days after the Blanket Purchase Agreement is closed. This deliverable will be copied over and executed only on a Blanket Purchase Agreement. If the contract template containing this deliverable is applied on a Purchase Order document, the deliverable will be dropped. If the same contract template is applied on a negotiation document, for example RFQ, which will conclude in a Blanket Purchase Agreement award, then the ore related to the Blanket Purchase Agreement will be retained on the negotiation document and carried forward to the Blanket Purchase Agreement.