{"component": "clause", "props": {"groups": [{"samples": [{"hash": "becl3e8UC1z", "uri": "/contracts/becl3e8UC1z#task-summary", "label": "Master Research Subaward", "score": 24.4209445585, "published": true}, {"hash": "7v2dzrZlSn6", "uri": "/contracts/7v2dzrZlSn6#task-summary", "label": "Project Agreement", "score": 24.2991101985, "published": true}], "snippet_links": [{"key": "provide-for", "type": "clause", "offset": [15, 26]}, {"key": "project-outcomes", "type": "clause", "offset": [47, 63]}, {"key": "with-respect-to", "type": "clause", "offset": [64, 79]}, {"key": "decision-points", "type": "clause", "offset": [129, 144]}, {"key": "provide-the", "type": "clause", "offset": [174, 185]}, {"key": "to-recipient", "type": "clause", "offset": [228, 240]}, {"key": "the-project-objectives", "type": "clause", "offset": [278, 300]}, {"key": "the-institute", "type": "clause", "offset": [318, 331]}], "snippet": "This task will provide for the tracking of the project outcomes with respect to the stated deliverables, milestones and go/no-go decision points. Furthermore, this task will provide the required financial and schedule reporting to Recipient and to DOE to ensure compliance with the project objectives and the goals of the Institute and the FOA.", "size": 2, "hash": "e51f60720c380990999df56affa7a729", "id": 1}, {"samples": [{"hash": "ea4AK3zMj0y", "uri": "/contracts/ea4AK3zMj0y#task-summary", "label": "Professional Services", "score": 33.1987256382, "published": true}], "snippet_links": [{"key": "task-1", "type": "clause", "offset": [0, 6]}, {"key": "traffic-signal", "type": "clause", "offset": [9, 23]}, {"key": "operational-analysis", "type": "clause", "offset": [44, 64]}, {"key": "by-june", "type": "clause", "offset": [75, 82]}, {"key": "the-study", "type": "definition", "offset": [201, 210]}, {"key": "the-town", "type": "definition", "offset": [216, 224]}, {"key": "site-visit", "type": "definition", "offset": [229, 239]}, {"key": "plan-reviews", "type": "clause", "offset": [251, 263]}, {"key": "a-site", "type": "definition", "offset": [265, 271]}, {"key": "obtain-information", "type": "clause", "offset": [316, 334]}, {"key": "operational-aspects", "type": "clause", "offset": [411, 430]}, {"key": "design-plans", "type": "definition", "offset": [432, 444]}, {"key": "the-future", "type": "clause", "offset": [525, 535]}, {"key": "location-of", "type": "definition", "offset": [587, 598]}, {"key": "pedestrian-facilities", "type": "clause", "offset": [599, 620]}, {"key": "school-zones", "type": "clause", "offset": [625, 637]}, {"key": "land-use", "type": "clause", "offset": [641, 649]}, {"key": "specific-issues", "type": "clause", "offset": [739, 754]}, {"key": "warrant-a", "type": "definition", "offset": [764, 773]}, {"key": "sight-distance", "type": "definition", "offset": [798, 812]}, {"key": "safety-considerations", "type": "clause", "offset": [817, 838]}, {"key": "operational-issues", "type": "clause", "offset": [882, 900]}, {"key": "operational-factors", "type": "clause", "offset": [913, 932]}, {"key": "data-collection", "type": "clause", "offset": [1198, 1213]}], "snippet": "Task 1 \u2013 Traffic Signal Warrant Studies and Operational Analysis (complete by June 14, 2024)\n1) Meetings: Stantec staff will attend up to one (1) meeting as part of this scope to review the results of the study with the Town.\n2) Site Visit and design plan reviews: A site visit will be conducted by Stantec staff to obtain information about the existing surrounding roadway network as well as all geometric and operational aspects. Design plans for the widening of First Street will also be reviewed to evaluate warrants for the future condition. These reviews include the following:\na) Location of pedestrian facilities and school zones\nb) Land use surrounding each intersection,\nc) Near-by traffic generators,\nd) Additional intersection specific issues that may warrant a signal,\ne) Intersection Sight distance,\nf) Safety considerations,\ng) Intersection photos needed to show any operational issues, and\nh) Any operational factors that may affect the intersection.\ni) The study intersections include the following:\n(a) First Street at Legacy Drive \u2013 Legacy Drive will be extended to the south in the near future.\n(b) Legacy Drive at Prairie Drive\n(c) First Street at Windsong Parkway\n3) Existing Data Collection:", "size": 1, "hash": "6cd1ab6cf09f696d3eceeeeadf4deebd", "id": 2}, {"samples": [{"hash": "ju98kMc5TxE", "uri": "/contracts/ju98kMc5TxE#task-summary", "label": "Scope of Services", "score": 20.9808350445, "published": true}], "snippet_links": [{"key": "key-components", "type": "definition", "offset": [0, 14]}, {"key": "this-contract", "type": "clause", "offset": [19, 32]}, {"key": "stakeholder-meetings", "type": "clause", "offset": [126, 146]}, {"key": "preliminary-design", "type": "definition", "offset": [163, 181]}, {"key": "the-project", "type": "clause", "offset": [308, 319]}, {"key": "environmental-documentation", "type": "definition", "offset": [320, 347]}, {"key": "contract-delivery", "type": "definition", "offset": [442, 459]}, {"key": "contractor-procurement", "type": "clause", "offset": [464, 486]}, {"key": "design-and-build", "type": "clause", "offset": [520, 536]}], "snippet": "Key components for this contract include: \u2022 Coordinate involvement from various public groups and agencies. \u2022 Set up and lead stakeholder meetings. \u2022 Planning and preliminary design of at least two structure types and recommendation of a single preferred alignment for the improved river crossing. \u2022 Develop the project environmental documentation for both STATE and MTO. \u2022 Foundations investigations on the MTO side. \u2022 Explore and recommend contract delivery and contractor procurement options to be used to ultimately design and build the bridge.", "size": 1, "hash": "8cb7412169d4c58f0c69f95ce4d76c5b", "id": 3}, {"samples": [{"hash": "A8sSj2SqrW", "uri": "/contracts/A8sSj2SqrW#task-summary", "label": "Professional Services", "score": 30.7429800293, "published": true}], "snippet_links": [{"key": "task-1", "type": "clause", "offset": [0, 6]}, {"key": "topographic-survey", "type": "clause", "offset": [9, 27]}, {"key": "adjacent-to", "type": "definition", "offset": [107, 118]}, {"key": "the-site", "type": "clause", "offset": [119, 127]}, {"key": "above-ground", "type": "definition", "offset": [226, 238]}, {"key": "location-and-size", "type": "clause", "offset": [293, 310]}, {"key": "preliminary-engineering", "type": "clause", "offset": [341, 364]}, {"key": "plan-sheets", "type": "clause", "offset": [381, 392]}, {"key": "the-town", "type": "definition", "offset": [397, 405]}, {"key": "review-and-approve", "type": "clause", "offset": [420, 438]}, {"key": "geometric-design", "type": "definition", "offset": [443, 459]}, {"key": "associated-infrastructure", "type": "definition", "offset": [479, 504]}, {"key": "design-engineering", "type": "clause", "offset": [562, 580]}, {"key": "subject-to-change", "type": "clause", "offset": [629, 646]}, {"key": "based-on", "type": "clause", "offset": [647, 655]}, {"key": "final-design", "type": "clause", "offset": [656, 668]}], "snippet": "Task 1 \u2013 Topographic Survey\n1. Contours at one foot intervals.\n2. Spot elevations at streets and pavements adjacent to the site along each curb and edge of pavement.\n3. Plotted locations of structures, paving and improvements above ground on or within approximately fifty feet of the site.\n4. Location and size of visible utilities. Prepare preliminary engineering exhibits and/or plan sheets for the Town of Prosper to review and approve the geometric design of the roadway and associated infrastructure. Although it will be taken into account, all preliminary design engineering is to exclude vertical design and any items are subject to change based on final design engineering.", "size": 1, "hash": "6ae6ec202bc05386661dc4bb5a0fd808", "id": 4}, {"samples": [{"hash": "j9vjAcsXSr4", "uri": "/contracts/j9vjAcsXSr4#task-summary", "label": "Professional Services", "score": 32.9879483345, "published": true}], "snippet_links": [{"key": "data-collection", "type": "clause", "offset": [9, 24]}, {"key": "base-map", "type": "definition", "offset": [27, 35]}, {"key": "task-2", "type": "clause", "offset": [88, 94]}, {"key": "complete-listing", "type": "clause", "offset": [140, 156]}, {"key": "current-inventory", "type": "definition", "offset": [160, 177]}, {"key": "task-3", "type": "definition", "offset": [178, 184]}, {"key": "demographic-data", "type": "definition", "offset": [235, 251]}, {"key": "task-4", "type": "definition", "offset": [252, 258]}, {"key": "task-5", "type": "definition", "offset": [327, 333]}, {"key": "system-data", "type": "definition", "offset": [377, 388]}, {"key": "task-6", "type": "clause", "offset": [389, 395]}, {"key": "needs-assessment", "type": "definition", "offset": [418, 434]}, {"key": "community-engagement", "type": "definition", "offset": [450, 470]}, {"key": "task-7", "type": "clause", "offset": [488, 494]}, {"key": "program-analysis", "type": "clause", "offset": [508, 524]}, {"key": "based-on", "type": "clause", "offset": [557, 565]}, {"key": "current-programs", "type": "definition", "offset": [566, 582]}, {"key": "task-8", "type": "clause", "offset": [583, 589]}, {"key": "task-9", "type": "definition", "offset": [657, 663]}, {"key": "action-plan", "type": "definition", "offset": [666, 677]}, {"key": "task-10", "type": "definition", "offset": [730, 737]}, {"key": "implementation-plan", "type": "clause", "offset": [740, 759]}, {"key": "task-11", "type": "definition", "offset": [803, 810]}, {"key": "master-plan-document", "type": "definition", "offset": [864, 884]}, {"key": "task-12", "type": "clause", "offset": [885, 892]}, {"key": "final-master-plan", "type": "clause", "offset": [895, 912]}], "snippet": "Task 1 \u2013 Data Collection & Base Map Preparation Task Details \u2013 Prepare Digital Base Map Task 2 \u2013 Inventory & Supply Analysis Task Details \u2013 Complete Listing of Current Inventory Task 3 \u2013 Population Analysis Task Details \u2013 Population & Demographic Data Task 4 \u2013 Standard Analysis Task Details \u2013 Provide Classifications for Park Task 5 \u2013 Benchmarking Task Details \u2013 Compare Park System Data Task 6 \u2013 Demand Analysis and Needs Assessment Task Details \u2013 Community Engagement & Citizen Survey Task 7 \u2013 Recreation Program Analysis Task Details \u2013 Program Analysis based on current programs Task 8 \u2013 Priority Rankings Task Details \u2013 Prepare Priority Ranking Matrix Task 9 \u2013 Action Plan Task Details \u2013 Prepare Preliminary Park Action Plan Task 10 \u2013 Implementation Plan Task Details \u2013 Prepare Implementation Plan Task 11 \u2013 Preliminary Master Plan Task Details \u2013 Preliminary Master Plan Document Task 12 \u2013 Final Master Plan Task Details \u2013 Final Master Plan Document", "size": 1, "hash": "6f0ded6f8d35ed16ecb7e1ce1a4bc82e", "id": 5}, {"samples": [{"hash": "7pp9Ukpdgc3", "uri": "/contracts/7pp9Ukpdgc3#task-summary", "label": "Professional Engineering Services Agreement", "score": 24.5099247091, "published": true}], "snippet_links": [{"key": "section-131", "type": "clause", "offset": [33, 46]}, {"key": "plan-set", "type": "clause", "offset": [75, 83]}, {"key": "listed-below", "type": "clause", "offset": [96, 108]}, {"key": "retaining-wall", "type": "clause", "offset": [112, 126]}, {"key": "water-line", "type": "clause", "offset": [288, 298]}, {"key": "main-plan", "type": "definition", "offset": [335, 344]}, {"key": "water-and-wastewater", "type": "clause", "offset": [359, 379]}, {"key": "section-31", "type": "clause", "offset": [388, 399]}, {"key": "part-3", "type": "clause", "offset": [421, 427]}], "snippet": "The following change is made for section 1.3.1 Plans to include additional plan set elements as listed below: \u2022 Retaining wall layout and elevation \u2022 Median illumination foundation and conduit layout \u2022 Median planting layout \u2022 Median irrigation layout \u2022 Planting and irrigation details \u2022 Water line plan and profile \u2022 Wastewater force main plan and profile \u2022 Water and wastewater details\nSection 3.1 Field and Laboratory part 3. Structures is revised to read as follows:", "size": 1, "hash": "bb37b4f94f6e5330ebbb5d595c412845", "id": 6}, {"samples": [{"hash": "x9gXyIQeLz", "uri": "/contracts/x9gXyIQeLz#task-summary", "label": "Professional Engineering Services Agreement", "score": 29.5607172531, "published": true}], "snippet_links": [{"key": "task-1", "type": "clause", "offset": [0, 6]}, {"key": "level-a", "type": "definition", "offset": [9, 16]}, {"key": "compliance-with", "type": "definition", "offset": [83, 98]}, {"key": "asce-38", "type": "definition", "offset": [102, 109]}, {"key": "guidelines-for", "type": "clause", "offset": [123, 137]}, {"key": "collection-and", "type": "clause", "offset": [142, 156]}, {"key": "utility-data", "type": "definition", "offset": [190, 202]}, {"key": "quality-levels", "type": "clause", "offset": [248, 262]}, {"key": "data-collection", "type": "clause", "offset": [267, 282]}, {"key": "level-d", "type": "definition", "offset": [324, 331]}, {"key": "information-collected", "type": "clause", "offset": [370, 391]}, {"key": "level-c", "type": "definition", "offset": [472, 479]}, {"key": "professional-judgment", "type": "clause", "offset": [618, 639]}, {"key": "utility-crossings", "type": "clause", "offset": [787, 804]}, {"key": "level-b", "type": "definition", "offset": [816, 823]}, {"key": "application-of", "type": "clause", "offset": [924, 938]}, {"key": "geophysical-methods", "type": "definition", "offset": [959, 978]}, {"key": "determine-the", "type": "clause", "offset": [982, 995]}, {"key": "plan-documents", "type": "clause", "offset": [1260, 1274]}, {"key": "location-of-utilities", "type": "clause", "offset": [1437, 1458]}, {"key": "actual-exposure", "type": "definition", "offset": [1475, 1490]}, {"key": "measurement-of", "type": "clause", "offset": [1569, 1583]}, {"key": "for-the-purpose-of", "type": "definition", "offset": [1698, 1716]}, {"key": "subject-project", "type": "definition", "offset": [1742, 1757]}, {"key": "providing-information", "type": "clause", "offset": [1761, 1782]}, {"key": "related-to", "type": "clause", "offset": [1783, 1793]}, {"key": "in-order-to", "type": "clause", "offset": [1815, 1826]}, {"key": "utility-conflicts", "type": "clause", "offset": [1843, 1860]}, {"key": "consultant-will-provide-services", "type": "clause", "offset": [1899, 1931]}, {"key": "standard-of-care", "type": "definition", "offset": [1946, 1962]}, {"key": "utility-location", "type": "clause", "offset": [1987, 2003]}, {"key": "due-diligence", "type": "clause", "offset": [2062, 2075]}, {"key": "with-regard-to", "type": "clause", "offset": [2076, 2090]}, {"key": "records-research", "type": "clause", "offset": [2091, 2107]}, {"key": "utility-information", "type": "clause", "offset": [2127, 2146]}, {"key": "work-area", "type": "definition", "offset": [2182, 2191]}, {"key": "evidence-of", "type": "definition", "offset": [2196, 2207]}, {"key": "information-from", "type": "clause", "offset": [2261, 2277]}, {"key": "the-consultant-makes", "type": "clause", "offset": [2315, 2335]}, {"key": "no-guarantee", "type": "clause", "offset": [2336, 2348]}, {"key": "all-utilities", "type": "clause", "offset": [2354, 2367]}, {"key": "the-project-area", "type": "clause", "offset": [2443, 2459]}, {"key": "by-the-consultant", "type": "clause", "offset": [2564, 2581]}, {"key": "plan-records", "type": "clause", "offset": [2589, 2601]}, {"key": "project-deliverables", "type": "definition", "offset": [2771, 2791]}, {"key": "field-investigation", "type": "definition", "offset": [2848, 2867]}, {"key": "initial-scope-of-work", "type": "clause", "offset": [2964, 2985]}, {"key": "the-client", "type": "definition", "offset": [3003, 3013]}, {"key": "additional-work", "type": "clause", "offset": [3038, 3053]}, {"key": "project-impacts", "type": "clause", "offset": [3081, 3096]}, {"key": "ground-penetrating-radar", "type": "clause", "offset": [3125, 3149]}, {"key": "the-project-site", "type": "clause", "offset": [3207, 3223]}, {"key": "the-scope-of-services", "type": "clause", "offset": [3277, 3298]}, {"key": "subsurface-conditions", "type": "clause", "offset": [3470, 3491]}, {"key": "completion-of", "type": "clause", "offset": [3508, 3521]}, {"key": "other-utilities", "type": "clause", "offset": [3579, 3594]}, {"key": "test-hole", "type": "definition", "offset": [3614, 3623]}, {"key": "the-plans", "type": "clause", "offset": [3714, 3723]}, {"key": "utility-will", "type": "clause", "offset": [3813, 3825]}, {"key": "field-measurements", "type": "clause", "offset": [3862, 3880]}, {"key": "outside-diameter", "type": "definition", "offset": [3888, 3904]}, {"key": "nominal-pipe-size", "type": "definition", "offset": [3984, 4001]}, {"key": "available-data", "type": "clause", "offset": [4070, 4084]}, {"key": "duct-banks", "type": "clause", "offset": [4197, 4207]}, {"key": "best-available-information", "type": "definition", "offset": [4311, 4337]}, {"key": "professional-opinion", "type": "definition", "offset": [4404, 4424]}, {"key": "affected-by", "type": "definition", "offset": [4518, 4529]}, {"key": "existing-site-conditions", "type": "clause", "offset": [4543, 4567]}, {"key": "characteristics-of-the", "type": "clause", "offset": [4665, 4687]}, {"key": "lack-of", "type": "clause", "offset": [4718, 4725]}, {"key": "for-non", "type": "clause", "offset": [4764, 4771]}, {"key": "the-successful", "type": "clause", "offset": [4841, 4855]}, {"key": "additional-field", "type": "definition", "offset": [4992, 5008]}, {"key": "record-drawings", "type": "definition", "offset": [5087, 5102]}, {"key": "not-available", "type": "definition", "offset": [5107, 5120]}, {"key": "in-such-cases", "type": "clause", "offset": [5122, 5135]}, {"key": "a-recommendation", "type": "definition", "offset": [5165, 5181]}, {"key": "to-the-town", "type": "clause", "offset": [5217, 5228]}, {"key": "other-methods", "type": "clause", "offset": [5236, 5249]}, {"key": "the-line", "type": "definition", "offset": [5318, 5326]}, {"key": "designation-of-the", "type": "clause", "offset": [5341, 5359]}, {"key": "utility-owner", "type": "definition", "offset": [5415, 5428]}, {"key": "access-to", "type": "definition", "offset": [5441, 5450]}, {"key": "condition-of-the", "type": "clause", "offset": [5461, 5477]}, {"key": "comply-with-the", "type": "clause", "offset": [5616, 5631]}, {"key": "statutory-requirements", "type": "clause", "offset": [5632, 5654]}, {"key": "in-advance", "type": "clause", "offset": [5706, 5716]}, {"key": "services-for", "type": "clause", "offset": [5895, 5907]}, {"key": "survey-services", "type": "definition", "offset": [5941, 5956]}, {"key": "in-this-contract", "type": "clause", "offset": [6095, 6111]}], "snippet": "Task 1 \u2013 Level A/B SUE\n1. These services will be conducted and provided in general compliance with CI/ASCE 38-02 (Standard Guidelines for the Collection and Depiction of Existing Subsurface Utility Data). This standard establishes and defines four quality levels for data collection that are briefly described as: \u25aa Quality Level D (QL-\u201cD\u201d) \u2013 Generally QL-\u201cD\u201d indicates information collected or derived from research of existing records and/or oral discussions. \u25aa Quality Level C ( QL-\u201cC\u201d) - Generally QL-\u201cC\u201d indicates information obtained by surveying and plotting visible above- ground utility features and by using professional judgment in correlating this information to QL-\u201cD\u201d information. Incorporates QL-\u201cD\u201d information. (Limited in this scope, this scope is to cover underground utility crossings) \u25aa Quality Level B (QL-\u201cB\u201d) \u2013 Generally QL-\u201cB\u201d, also known as \u201cdesignating\u201d indicates information obtained through the application of appropriate surface geophysical methods to determine the existence and approximate horizontal position of subsurface utilities. Quality level B data should be reproducible by surface geophysics at any point of their depiction. This information is surveyed to applicable tolerances defined by the project and reduced onto plan documents. Incorporates QL-\u201cD\u201d & QL-\u201cC\u201d information. \u25aa Quality Level A (QL-\u201cA\u201d) - Generally QL-\u201cA\u201d, also known as \u201clocating\u201d, indicates the precise horizontal and vertical location of utilities obtained by the actual exposure (or verification of previously exposed and surveyed utilities) and subsequent measurement of subsurface utilities, at a specific point. Incorporates QL-\u201cD\u201d QL-\u201cC\u201d & QL-\u201cB\u201d information.\n2. These services are for the purpose of aiding the design of the subject project by providing information related to subsurface utilities in order to allow potential utility conflicts to be minimized or eliminated.\n3. The Consultant will provide services that meet the standard of care for existing subsurface utility location and mapping as established in CI/ASCE 38-02 by exercising due diligence with regard to records research and acquisition of utility information, including visually inspecting the work area for evidence of utilities and reviewing the available utility record information from the various utility owners. However, the Consultant makes no guarantee that all utilities can or will be identified and shown as there still may be utilities within the project area that are undetectable or unknown.\n4. Facilities that are discovered through field investigative efforts by the Consultant but no plan records or ownership data can be identified will be hereafter referred to as \u201cunknown\u201d utilities. As part of these services, the Consultant will provide QL-C information in the project deliverables for all unknown utilities that may be identified in the field investigation of the project. Designating and/or locating unknown utilities will typically not be part of the initial scope of work but depending on the client\u2019s needs can be added as additional work to address concerns of the project impacts of \u201cunknown\u201d facilities.\n5. Ground penetrating radar will not be used as a part of the field investigation of the project site unless that use has been specifically addressed with the scope of services described herein.\n6. Test holes are very limited in size or diameter (typically 12 inches by 12 inches, or approximately 144 square inches). Given this limited size, some subsurface conditions may prevent the completion of test holes, including rock(s), groundwater, large roots, other utilities & structures, etc. Test hole attempts which cannot be completed due to site conditions will be documented and noted on the plans.\n7. When test holes are used to locate utilities, the nominal pipe sizes of the targeted utility will be documented and reported by using field measurements of the outside diameter (OD) of the pipe (to the nearest inch). Based upon this field measured OD, the nominal pipe size will be determined using typical pipe wall thickness data and other available data including record information. Pipe diameters that are too large for measurement, encased or non-encased conduit duct banks and other concrete encased systems which cannot be adequately measured will be reported based upon the best available information.\n8. The documented results produced by these services represent a professional opinion and interpretation based upon record information and/or field evidence. These results may be affected by a variety of existing site conditions, including soil content, depth of the utility, density of utility clusters, and electro-magnetic characteristics of the targeted utilities. Also, the lack of and/or poor condition of a trace wire for non-conductive materials such as PVC, HDPE, etc. in most cases will make the successful detection and location of the utility unlikely.\n9. The Consultant will apply professional judgment to determine which utilities require additional field effort and/or methods to properly designate and/or locate, most commonly when record drawings are not available. In such cases, the Consultant will provide a recommendation or request for additional services to the Town. Among other methods, a detectable duct rodder or other conductor may be introduced into the line to enable the designation of the utility. This method is dependent upon approval by the utility owner, as well as access to, size and condition of the utility.\n10. None of these services are intended to and should not be understood to relieve the Town or others from the responsibility to comply with the statutory requirements related to notifying the proper one-call system(s) in advance of any and all excavation, grading and/or construction within the project site. Subsurface Utility Scope of Services: The scope of subsurface utility designating and/or locating services for this project is described below. Survey services to tie utility crossing marks and/or identifiers placed during the subsurface utility designating and/or locating effort will be provided in this contract.\na) Quality Level \u2018B\u2019 through \u2018", "size": 1, "hash": "807a2a2c945d9787de155b99d1d5c4c5", "id": 7}, {"samples": [{"hash": "sjs4YBOGev", "uri": "/contracts/sjs4YBOGev#task-summary", "label": "Professional Engineering Services Agreement", "score": 23.5612594114, "published": true}], "snippet_links": [{"key": "responsible-for", "type": "clause", "offset": [14, 29]}, {"key": "associated-with", "type": "definition", "offset": [68, 83]}, {"key": "environmental-services", "type": "definition", "offset": [112, 134]}, {"key": "federal-agencies", "type": "clause", "offset": [195, 211]}, {"key": "in-accordance-with", "type": "definition", "offset": [212, 230]}, {"key": "management-guide", "type": "definition", "offset": [266, 282]}, {"key": "city-of", "type": "clause", "offset": [351, 358]}, {"key": "the-project-manager", "type": "clause", "offset": [376, 395]}, {"key": "monthly-progress-reports", "type": "definition", "offset": [409, 433]}, {"key": "meetings-with-the-city", "type": "clause", "offset": [453, 475]}, {"key": "design-and-permitting", "type": "clause", "offset": [503, 524]}, {"key": "to-discuss", "type": "definition", "offset": [623, 633]}, {"key": "presentation-materials", "type": "clause", "offset": [670, 692]}, {"key": "public-meetings", "type": "clause", "offset": [720, 735]}, {"key": "city-council", "type": "definition", "offset": [739, 751]}, {"key": "staff-attendance", "type": "clause", "offset": [771, 787]}, {"key": "project-records", "type": "definition", "offset": [826, 841]}, {"key": "quality-assurance", "type": "definition", "offset": [862, 879]}, {"key": "quality-control-reviews", "type": "clause", "offset": [880, 903]}, {"key": "final-deliverables", "type": "definition", "offset": [922, 940]}, {"key": "duration-of-the-project", "type": "definition", "offset": [956, 979]}], "snippet": "Halff will be responsible for directing and coordinating activities associated with the civil, survey, \u2587\u2587\u2587, and environmental services, including necessary coordination with local, state, and/or federal agencies in accordance with the TxDOT Local Government Project Management Guide. Appropriate communication will be maintained between Halff and the City of Sachse (\u201cCity\u201d). The project manager will prepare monthly progress reports and attend monthly meetings with the City throughout the duration of design and permitting. Halff Civil and Environmental staff will attend up to three (3) meetings with the City and TxDOT to discuss relevant project issues and prepare presentation materials for up to two (2) informal public meetings or City Council updates with Halff staff attendance. Halff will organize and maintain the project records. Halff will conduct quality assurance/quality control reviews for all draft and final deliverables throughout the duration of the project.", "size": 1, "hash": "2d7d4276d302e0c3b7b1a85ea6c9c267", "id": 8}, {"samples": [{"hash": "i5sZxd1mMDr", "uri": "/contracts/i5sZxd1mMDr#task-summary", "label": "Professional Engineering Services Agreement", "score": 32.8215299155, "published": true}], "snippet_links": [{"key": "task-5", "type": "definition", "offset": [0, 6]}, {"key": "project-management", "type": "definition", "offset": [19, 37]}, {"key": "to-discuss", "type": "definition", "offset": [85, 95]}, {"key": "review-comments", "type": "clause", "offset": [146, 161]}, {"key": "notes-as-requested", "type": "clause", "offset": [246, 264]}, {"key": "by-the-town", "type": "clause", "offset": [366, 377]}, {"key": "plan-revisions", "type": "clause", "offset": [424, 438]}, {"key": "based-on", "type": "clause", "offset": [439, 447]}, {"key": "deceleration-lane", "type": "definition", "offset": [458, 475]}, {"key": "median-opening", "type": "definition", "offset": [477, 491]}, {"key": "task-6", "type": "clause", "offset": [521, 527]}, {"key": "requested-by", "type": "definition", "offset": [615, 627]}, {"key": "construction-plans", "type": "clause", "offset": [662, 680]}, {"key": "costs-of", "type": "clause", "offset": [781, 789]}, {"key": "a-list", "type": "definition", "offset": [885, 891]}, {"key": "franchise-utilities", "type": "definition", "offset": [895, 914]}, {"key": "plans-and", "type": "definition", "offset": [1027, 1036]}, {"key": "utility-relocations", "type": "clause", "offset": [1062, 1081]}], "snippet": "Task 5 \u2013 Phase III Project Management. Meet with the Town of Prosper and TxDOT staff to discuss redesign evaluation progress, pre-final submittal review comments, and final submittal deliverables (2 meetings assumed). Prepare and provide meeting notes as requested. Evaluate pre-final submittal review comments for resolution. (*Pre- final submittal review comments by the Town of Prosper and TxDOT assumed to only apply to plan revisions based on requested deceleration lane, median opening, and driveway improvements.) Task 6 \u2013 Phase III Redesign. Add deceleration lane, median opening, and driveway improvements requested by the Town of Prosper to the US 380 construction plans. Prepare and provide plans (11x17 drawings) including quantity revisions and estimated construction costs of requested deceleration lanes, median openings, and driveways. The Town of Prosper will prepare a list of franchise utilities impacted by the requested deceleration lanes, median openings, and driveways based on the provided construction plans and coordinate any franchise utility relocations needed with TxDOT.", "size": 1, "hash": "3542e280f02d6bd8b32741b3ae30ba72", "id": 9}, {"samples": [{"hash": "IzKbJrtvaS", "uri": "/contracts/IzKbJrtvaS#task-summary", "label": "Professional Services Agreement", "score": 31.5417564526, "published": true}], "snippet_links": [{"key": "task-1", "type": "clause", "offset": [0, 6]}], "snippet": "TASK 1 -", "size": 1, "hash": "563861864bfde465927980d58fda3f74", "id": 10}], "next_curs": "ClUST2oVc35sYXdpbnNpZGVyY29udHJhY3RzcjELEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhV0YXNrLXN1bW1hcnkjMDAwMDAwMGEMogECZW4YACAA", "clause": {"parents": [["original-agreement", "Original Agreement"], ["signatories", "Signatories"], ["mutual-waiver-of-consequential-damages", "Mutual Waiver of Consequential Damages"], ["other-terms-and-conditions", "OTHER TERMS AND CONDITIONS"], ["miscellaneous", "Miscellaneous"]], "children": [["", ""], ["construction-phase-services", "Construction Phase Services"], ["data-collection", "Data Collection"], ["hydraulic-analysis", "Hydraulic Analysis"], ["quality-level-a-utility-test-holes", "Quality Level A Utility Test Holes"]], "title": "TASK SUMMARY", "size": 22, "id": "task-summary", "related": [["job-summary", "JOB SUMMARY", "JOB SUMMARY"], ["project-summary", "Project Summary", "Project Summary"], ["budget-summary", "Budget Summary", "Budget Summary"], ["task-description", "Task Description", "Task Description"], ["system-description", "System Description", "System Description"]], "related_snippets": [], "updated": "2025-07-07T12:37:53+00:00", "also_ask": [], "drafting_tip": null, "explanation": "The TASK SUMMARY clause defines the specific duties, deliverables, or objectives that a party is responsible for under the agreement. It typically outlines the scope of work, key milestones, and expected outcomes, providing a clear overview of what is to be accomplished. By summarizing the essential tasks, this clause ensures both parties have a mutual understanding of their obligations, reducing the risk of misunderstandings or disputes regarding the work to be performed."}, "json": true, "cursor": ""}}