Characteristics of Stipends and Their Value-Adding Potential in Design-Build US Highway Construction
Bibliographic record
Abstract
A best practice tool to enhance design-build best-value procurements is stipends, yet there is very little literature dedicated to this topic. Cited benefits of stipends include incentivizing the level of effort put forth by proposers in preparing their technical proposal, encouraging the number of proposers and thereby increasing competition, and mitigating risk. This paper presents cross-validated findings from the literature, agency policies, a survey of 53 US design-build projects, six agency representative interviews, and 13 design-build industry professional interviews. This paper investigates four aspects of stipends: (1) stipend value and calculation processes; (2) impact on a contractor’s decision to propose; (3) impact of stipend amount on an offeror’s proposal development, and (4) stipends’ ability to aid agencies in achieving best value for highway construction projects. Stipends were found to be a necessary process to achieve best value because they increase competition and often can increase the quality of a proposal based on the stipend amount. Stipends typically cover one-third to one-half of a contractor’s proposal costs. Agencies should use stipends when proposal costs are expected to be high and should estimate the stipend amount on a project-by-project basis. Properly valued stipends demonstrate that an agency is serious about going forward with the project, and understands both the work required and the design-build process. Finally, stipends were found to promote a fair procurement process, building trust with contractors leading to a more collaborative and innovative project execution.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.016 | 0.074 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.005 | 0.003 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.006 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".