When creating a contract derived from a Structured Documents (SD) tender, you can directly import specific bid data and documents without manually re-entering information. This is how to fetch attachments and map granular pricing data into your contract terms.
1. Importing SD Attachments
You can attach the original tender and bid documentation directly to your contract folder. This ensures the legal audit trail remains intact within the Contract Lifecycle Management (CLM) system.
Navigate to the Contract attachments section of your contract draft.
Click the Add document tool.
Select From Bid (or Pick from procurement depending on your configuration).
You will see a list of available files generated during the SD workflow. Select the files you wish to import:
Tender content: The original requirements and structure published to suppliers.
Bid content: The specific responses provided by the supplier.
Results report: The evaluation summary.
Supplier Uploads: Any specific PDFs or documents uploaded by the supplier during the bid.
Only documents originating from the Structured Documents workflow will appear in this list.
2. Fetching Price Segments and Data Fields
You can populate your contract's Terms and Conditions (T&C) with specific data points—such as unit prices, responses, or requirement descriptions—extracted directly from the supplier's structured bid.
How to fetch data:
Open the Terms and conditions editor for your contract.
Locate or create a text field (e.g., a pricing table or requirements clause).
Click Pick from procurement in the toolbar.
A search window will appear. Search for the specific data you need (e.g., type "Price" or the name of a specific section).
Select the relevant data segment to insert it into the field.
Data Fetching Rules & Criteria: To ensure data is imported correctly, the system follows specific logic based on how the tender was structured:
Source Visibility: Data can only be pushed to CLM from sections in the SD tool that were marked with the "Contract" checkbox.
Granularity: You can fetch granular data from three specific levels:
Sections: Broad categories or distinct parts of the tender.
Requirements: Specific questions or demands listed in the tender.
Responses: The actual answer or value provided by the supplier.
Formatting: When fetching multi-row text (e.g., long descriptions), the system preserves the original paragraphing from the SD source.
Data Fields Snapshot: If you fetch a data field (like a dynamic price unit), the data is inputted based on its content at the moment of fetching. Any subsequent updates to the source data field in the tender tool will not automatically update the contract text; you must re-fetch it if changes occur.
3. Important Limitations
Automated Product Lists: If your CLM contract is linked to an SD workflow, the feature to create an "Automated product list" (based on items procured) is hidden, as this specific automation is not yet supported for SD tenders.
Supported File Types: Ensure you are looking for PDF documents (Tender content.pdf, Bid content.pdf) when importing standard reports.
Article Ref: 190120261341
