Requests for tender (RFTs) sometimes ask for large and/or complex projects to be delivered. In these circumstances many providers will only be able to tender for part of the work. One option to receive many and varied tenders (which often results in better value for money), is to break the request up into multiple parts. For example, instead of one RFT to build a road, you might break it up into landscaping, road surfacing, and road lighting. 360 supports multi-part tenders with Hierarchical Requests (previously called Parent - Child Jobs). With a hierarchical request, all providers respond to the leading part but only the providers who are capable of delivering the requested goods and services respond to each subordinate parts. The evaluation of the leading part influences the evaluation of the subordinate parts to a configurable extent. For example, if the provider receives 100% for all criteria in the leading part, they may have automatically achieved 20% of the total attainable score for a subordinate part whereas another organisation who received a 50% score the leading part can, at best, only achieve 90% for the same subordinate part. |
There are two types of hierarchical requests:
|
Step-by-step guide
To create a standard hierarchical request:
Amend the Request Name for the subordinate request
The name of a subordinate part must start with the leading part's name |
At this point, the hierarchy has been created and each part is ready for further configuration.
All parts need to be fully configured before a hierarchical request can be published |
|