{"component": "clause", "props": {"groups": [{"size": 6, "snippet_links": [{"key": "evaluation-tool", "type": "definition", "offset": [29, 44]}, {"key": "regional-service-center", "type": "definition", "offset": [74, 97]}, {"key": "teacher-evaluation", "type": "definition", "offset": [111, 129]}, {"key": "effectiveness-of-the", "type": "clause", "offset": [271, 291]}, {"key": "areas-for-improvement", "type": "clause", "offset": [330, 351]}, {"key": "continued-evaluation", "type": "clause", "offset": [363, 383]}, {"key": "personnel-decisions", "type": "clause", "offset": [541, 560]}, {"key": "state-goals", "type": "clause", "offset": [673, 684]}, {"key": "comprised-of", "type": "clause", "offset": [745, 757]}, {"key": "the-learner", "type": "definition", "offset": [776, 787]}, {"key": "knowledge-base", "type": "definition", "offset": [795, 809]}, {"key": "the-professional", "type": "clause", "offset": [832, 848]}, {"key": "student-learning", "type": "definition", "offset": [959, 975]}, {"key": "the-criteria", "type": "clause", "offset": [1028, 1040]}, {"key": "teacher-assessment", "type": "clause", "offset": [1072, 1090]}, {"key": "and-support", "type": "clause", "offset": [1091, 1102]}, {"key": "four-levels", "type": "clause", "offset": [1475, 1486]}, {"key": "developing-educator", "type": "clause", "offset": [1525, 1544]}, {"key": "distinguished-educator", "type": "clause", "offset": [1571, 1593]}, {"key": "our-goal", "type": "clause", "offset": [1705, 1713]}], "snippet": "USD 489 will utilize the e4E Evaluation Tool designed by Southwest Plains Regional Service Center (SWPRSC) for teacher evaluation. *See forms in Appendix.\n1. Purpose: The four (4) Elements of an Effective Educator\u2019s Evaluation toolwill\na. Serve as a means to improve the effectiveness of the Educator by identifying strengths and areas for improvement\nb. Provide continued evaluation of an Educator\u2019s teaching practice\nc. Assist educators in self-reflection to improve teaching practices\nd. Provide Administrators with information to aid in personnel decisions\ne. Serve as a process for Educator development and Administrator professional growthand\nf. Align with local and state goals or improved Educatorperformance.\n2. Design: The e4E tool is comprised of four elements:\na. The Learner\nb. The Knowledge Base\nc. The Instruction\nd. The Professional\n3. All four elements are intertwined and are critical for effective Educator performance leading to increased student learning. Standards aligned with each element help implement the criteria listed in each. The Interstate Teacher Assessment and Support Consortium (InTASC) helped provide guidance on those areas to be measured by the Educator evaluationprocess.\n4. The four elements represent the four main areas considered for evaluation. Within each element are standards specific to that element. Each standard has a set of rubrics identifying the criteria of that standard. The criteria in each rubric are separated into four levels so performance:\na. Novice Educator\nb. Developing Educator\nc. Proficient Educator\nd. Distinguished Educator\n5. The \u2018Distinguished Educator\u2019 level represents the peak performance of an Educator in a classroom, and it is our goal that all Educators aspire to reach this highest level of professionalaccomplishment.\n6. Four (4)", "samples": [{"hash": "8SoFwIezdfX", "uri": "/contracts/8SoFwIezdfX#evaluation-design", "label": "Collective Bargaining Agreement", "score": 33.3328566496, "published": true}, {"hash": "9UIgMHgKnQt", "uri": "/contracts/9UIgMHgKnQt#evaluation-design", "label": "Collective Bargaining Agreement", "score": 25.8459958932, "published": true}, {"hash": "64C5YQ9Qk8V", "uri": "/contracts/64C5YQ9Qk8V#evaluation-design", "label": "Collective Bargaining Agreement", "score": 25.7994524298, "published": true}], "hash": "beae3fb90f58b1a4ec861aa839c41207", "id": 1}, {"size": 3, "snippet_links": [{"key": "the-evaluation", "type": "clause", "offset": [0, 14]}, {"key": "core-components", "type": "clause", "offset": [50, 65]}, {"key": "approved-by", "type": "definition", "offset": [72, 83]}], "snippet": "The Evaluation Design shall include the following core components to be approved by CMS:", "samples": [{"hash": "17kDAdyoEYD", "uri": "/contracts/17kDAdyoEYD#evaluation-design", "label": "Special Terms & Conditions", "score": 25.2422997947, "published": true}, {"hash": "h3aglRfLgTI", "uri": "/contracts/h3aglRfLgTI#evaluation-design", "label": "Special Terms and Conditions", "score": 24.6947296372, "published": true}, {"hash": "9AEQgS2X3pJ", "uri": "/contracts/9AEQgS2X3pJ#evaluation-design", "label": "Special Terms & Conditions", "score": 23.5174537988, "published": true}], "hash": "e1de7b13019745deef37b4b5d953808c", "id": 2}, {"size": 3, "snippet_links": [{"key": "the-evaluation", "type": "clause", "offset": [0, 14]}, {"key": "comparison-group", "type": "clause", "offset": [65, 81]}, {"key": "the-post", "type": "clause", "offset": [101, 109]}, {"key": "the-current", "type": "clause", "offset": [138, 149]}, {"key": "demonstration-period", "type": "definition", "offset": [150, 170]}], "snippet": "The evaluation design will utilize a post-only assessment with a comparison group. The timeframe for the post-only period will begin when the current demonstration period begins, and ends when the current demonstration period ends.", "samples": [{"hash": "8lODO1ByrN4", "uri": "/contracts/8lODO1ByrN4#evaluation-design", "label": "Special Terms and Conditions", "score": 26.290625567, "published": true}, {"hash": "cmVvvrdGp5o", "uri": "/contracts/cmVvvrdGp5o#evaluation-design", "label": "Special Terms and Conditions", "score": 22.279945243, "published": true}, {"hash": "iv3RpNkLljA", "uri": "/contracts/iv3RpNkLljA#evaluation-design", "label": "Special Terms and Conditions", "score": 21.6461327858, "published": true}], "hash": "f940ef124a734002d300fbea2b565409", "id": 3}, {"size": 2, "snippet_links": [{"key": "information-on", "type": "clause", "offset": [8, 22]}, {"key": "the-evaluation", "type": "clause", "offset": [27, 41]}, {"key": "for-example", "type": "definition", "offset": [60, 71]}, {"key": "comparison-group", "type": "clause", "offset": [155, 171]}], "snippet": "Provide information on how the evaluation will be designed. For example, will the evaluation utilize a pre/post comparison? A post-only assessment? Will a comparison group be included?", "samples": [{"hash": "adr8qtmEghR", "uri": "/contracts/adr8qtmEghR#evaluation-design", "label": "Special Terms and Conditions", "score": 31.6242321539, "published": true}, {"hash": "k9PHmy9orES", "uri": "/contracts/k9PHmy9orES#evaluation-design", "label": "Special Terms and Conditions", "score": 21.5229295003, "published": true}], "hash": "f41cc93e5858ad56935af5c4e62a4062", "id": 4}, {"size": 2, "snippet_links": [{"key": "evaluation-tool", "type": "definition", "offset": [29, 44]}, {"key": "regional-service-center", "type": "definition", "offset": [74, 97]}, {"key": "teacher-evaluation", "type": "definition", "offset": [111, 129]}], "snippet": "USD 489 will utilize the e4E Evaluation Tool designed by Southwest Plains Regional Service Center (SWPRSC) for teacher evaluation. *See forms in Appendix.", "samples": [{"hash": "910U0gHxWTV", "uri": "/contracts/910U0gHxWTV#evaluation-design", "label": "Collective Bargaining Agreement", "score": 29.3061889392, "published": true}, {"hash": "9Lv4JhmVmZh", "uri": "/contracts/9Lv4JhmVmZh#evaluation-design", "label": "Collective Bargaining Agreement", "score": 26.0634240579, "published": true}], "hash": "ec57aee5c530db01c6afd8f33f42cf2c", "id": 5}, {"size": 1, "snippet_links": [{"key": "the-majority", "type": "clause", "offset": [143, 155]}, {"key": "given-year", "type": "definition", "offset": [213, 223]}, {"key": "comparison-group", "type": "clause", "offset": [268, 284]}, {"key": "evaluation-questions", "type": "clause", "offset": [304, 324]}, {"key": "control-group", "type": "definition", "offset": [458, 471]}, {"key": "consist-of", "type": "clause", "offset": [483, 493]}, {"key": "the-program", "type": "clause", "offset": [543, 554]}], "snippet": "This evaluation employs post-only analyses. Because the FPW program was initiated over 20 years ago, a pre-post approach is not ideal. Because the majority of women eligible for the FPW program do not enroll in a given year, this creates an opportunity for a relevant comparison group for several of the evaluation questions. Thus, this will be a post-only analysis with a comparison group where outcomes for FPW enrollees will be compared to outcomes for a control group which will consist of women eligible for FPW but that do not enroll in the program.", "samples": [{"hash": "cmVvvrdGp5o", "uri": "/contracts/cmVvvrdGp5o#evaluation-design", "label": "Special Terms and Conditions", "score": 22.279945243, "published": true}], "hash": "ed67ba898fa83a90aa7b3cdf029013af", "id": 6}, {"size": 1, "snippet_links": [{"key": "the-study", "type": "definition", "offset": [0, 9]}, {"key": "experimental-design", "type": "clause", "offset": [21, 40]}, {"key": "program-group", "type": "definition", "offset": [105, 118]}, {"key": "fair-market-rent", "type": "clause", "offset": [145, 161]}, {"key": "cash-assistance", "type": "definition", "offset": [176, 191]}, {"key": "hope-center", "type": "definition", "offset": [241, 252]}, {"key": "control-group", "type": "definition", "offset": [308, 321]}, {"key": "state-housing-authority", "type": "definition", "offset": [404, 427]}, {"key": "new-castle", "type": "definition", "offset": [473, 483]}, {"key": "public-housing", "type": "clause", "offset": [491, 505]}, {"key": "housing-choice-voucher-program", "type": "definition", "offset": [510, 540]}, {"key": "housing-program", "type": "definition", "offset": [585, 600]}, {"key": "emergency-shelters", "type": "clause", "offset": [608, 626]}, {"key": "temporary-housing", "type": "clause", "offset": [628, 645]}, {"key": "inclusion-period", "type": "definition", "offset": [688, 704]}, {"key": "family-unit", "type": "definition", "offset": [750, 761]}, {"key": "individual-participant", "type": "definition", "offset": [795, 817]}, {"key": "head-of-household", "type": "definition", "offset": [825, 842]}, {"key": "rental-assistance", "type": "definition", "offset": [1012, 1029]}, {"key": "a-year", "type": "definition", "offset": [1086, 1092]}, {"key": "the-design", "type": "clause", "offset": [1122, 1132]}], "snippet": "The study is a quasi-experimental design that compares the housing security outcomes of two groups: 1) a program group who receives a 2-year 90% fair market rent (FMR) monthly cash assistance following a temporary maximum 90-day stay at the Hope Center (n = 120) and 2) a household socio-demographic matched control group sourced from CMIS, which is composed of families on any waitlist for the Delaware State Housing Authority (DSHA)\u2014or local-level housing authorities in New Castle County\u2014Public Housing and Housing Choice Voucher Program as well as with start and exit dates to any housing program (e.g., emergency shelters, temporary housing, rapid re-rehousing) that match our study inclusion period (n=120). They will randomize controls at the family unit but will observe outcomes at the individual participant family head of household level, potentially boosting the study\u2019s power. There are 2 independent matched groups of 60 in this overall study, totaling 120 controls and 120 families receiving cash rental assistance. Cohort 1 begins in Q3 of 2025, with cohort 2 following a year later, begins in Q3 of 2026. The design incorporates one-to-one propensity score matching.", "samples": [{"hash": "2rLFFOtAb8w", "uri": "/contracts/2rLFFOtAb8w#evaluation-design", "label": "Project Grant Agreement", "score": 33.7732321691, "published": true}], "hash": "7021cdde2b554d7799f3f758c55744de", "id": 7}, {"size": 1, "snippet_links": [{"key": "the-state", "type": "clause", "offset": [0, 9]}, {"key": "days-after", "type": "definition", "offset": [131, 141]}, {"key": "approval-of", "type": "clause", "offset": [146, 157]}, {"key": "the-evaluation", "type": "clause", "offset": [177, 191]}, {"key": "in-accordance-with", "type": "definition", "offset": [215, 233]}, {"key": "attachment-a", "type": "definition", "offset": [234, 246]}, {"key": "evaluation-guidance", "type": "definition", "offset": [320, 339]}, {"key": "technical-assistance", "type": "clause", "offset": [344, 364]}], "snippet": "The state must submit, for CMS comment and approval, a draft Evaluation Design no later than one-hundred and eighty (180) calendar days after the approval of the demonstration. The Evaluation Design must be drafted in accordance with Attachment A (Developing the Evaluation Design) of these STCs, and any applicable CMS evaluation guidance and technical assistance for the demonstration\u2019s policy components. The Evaluation Design must be developed in alignment with CMS guidance on applying robust evaluation approaches, such as quasi-experimental methods like difference-in- differences and interrupted time series, as well as establishing valid comparison groups and assuring causal inferences in demonstration evaluations.", "samples": [{"hash": "adr8qtmEghR", "uri": "/contracts/adr8qtmEghR#evaluation-design", "label": "Special Terms and Conditions", "score": 31.6242321539, "published": true}], "hash": "f3b092076cfeed5309d911a4e4fc0c0e", "id": 8}, {"size": 1, "snippet_links": [{"key": "study-design", "type": "definition", "offset": [28, 40]}, {"key": "the-design", "type": "clause", "offset": [65, 75]}, {"key": "the-study", "type": "definition", "offset": [97, 106]}, {"key": "in-time", "type": "definition", "offset": [239, 246]}], "snippet": "Exploratory cross sectional study design was used in this study. The design was selected because the study wanted to explore the phenomena under study and it was cross sectional because data about the phenomena were obtained at one moment in time.", "samples": [{"hash": "8fUJyLQoreb", "uri": "/contracts/8fUJyLQoreb#evaluation-design", "label": "Service Agreement", "score": 24.9110198494, "published": true}], "hash": "dce989bf8d872f04d3beddc44d5f37ed", "id": 9}, {"size": 1, "snippet_links": [{"key": "overall-evaluation", "type": "clause", "offset": [4, 22]}, {"key": "special-services", "type": "clause", "offset": [111, 127]}, {"key": "treatment-group", "type": "definition", "offset": [222, 237]}, {"key": "control-group", "type": "definition", "offset": [348, 361]}, {"key": "the-services", "type": "definition", "offset": [375, 387]}, {"key": "the-system", "type": "definition", "offset": [414, 424]}, {"key": "collection-and", "type": "clause", "offset": [449, 463]}, {"key": "deemed-eligible", "type": "definition", "offset": [521, 536]}, {"key": "intake-worker", "type": "definition", "offset": [654, 667]}, {"key": "primary-service-provider", "type": "definition", "offset": [676, 700]}, {"key": "web-application", "type": "definition", "offset": [725, 740]}, {"key": "username-and-password", "type": "clause", "offset": [819, 840]}, {"key": "record-of", "type": "clause", "offset": [937, 946]}, {"key": "the-county", "type": "definition", "offset": [1034, 1044]}, {"key": "identification-number", "type": "definition", "offset": [1058, 1079]}, {"key": "a-separate", "type": "definition", "offset": [1159, 1169]}, {"key": "in-order-to", "type": "clause", "offset": [1216, 1227]}, {"key": "data-entry", "type": "definition", "offset": [1252, 1262]}, {"key": "information-is-correct", "type": "clause", "offset": [1565, 1587]}, {"key": "refer-to", "type": "definition", "offset": [2228, 2236]}, {"key": "user-session", "type": "definition", "offset": [2379, 2391]}, {"key": "the-application", "type": "clause", "offset": [2487, 2502]}, {"key": "in-sequence", "type": "clause", "offset": [2681, 2692]}, {"key": "private-function", "type": "clause", "offset": [2712, 2728]}, {"key": "random-seed", "type": "definition", "offset": [2774, 2785]}, {"key": "executed-on", "type": "clause", "offset": [3000, 3011]}, {"key": "random-number-generator", "type": "definition", "offset": [3490, 3513]}, {"key": "walk-through", "type": "definition", "offset": [3518, 3530]}, {"key": "this-code", "type": "definition", "offset": [3672, 3681]}, {"key": "number-of-subjects", "type": "clause", "offset": [3689, 3707]}, {"key": "the-request", "type": "clause", "offset": [3739, 3750]}, {"key": "the-function", "type": "clause", "offset": [3789, 3801]}, {"key": "the-assignment", "type": "clause", "offset": [3887, 3901]}, {"key": "decimal-places", "type": "clause", "offset": [4790, 4804]}, {"key": "to-validate", "type": "definition", "offset": [4915, 4926]}, {"key": "minimum-value", "type": "definition", "offset": [5090, 5103]}, {"key": "maximum-value", "type": "definition", "offset": [5195, 5208]}, {"key": "assignment-to", "type": "clause", "offset": [5342, 5355]}, {"key": "the-site", "type": "clause", "offset": [5459, 5467]}, {"key": "and-application", "type": "clause", "offset": [5524, 5539]}, {"key": "by-the-university", "type": "clause", "offset": [5595, 5612]}, {"key": "it-services", "type": "clause", "offset": [5627, 5638]}, {"key": "access-to-the-database", "type": "clause", "offset": [5774, 5796]}, {"key": "directly-accessible", "type": "definition", "offset": [5999, 6018]}, {"key": "assignment-application", "type": "definition", "offset": [6033, 6055]}, {"key": "access-controls", "type": "definition", "offset": [6105, 6120]}, {"key": "not-accessible", "type": "definition", "offset": [6129, 6143]}, {"key": "other-users", "type": "definition", "offset": [6151, 6162]}, {"key": "hosting-service", "type": "definition", "offset": [6327, 6342]}, {"key": "security-of-the", "type": "clause", "offset": [6406, 6421]}, {"key": "system-patches", "type": "clause", "offset": [6457, 6471]}, {"key": "maintenance-operations", "type": "definition", "offset": [6491, 6513]}, {"key": "university-standards", "type": "clause", "offset": [6548, 6568]}, {"key": "security-system", "type": "definition", "offset": [6641, 6656]}, {"key": "the-decision", "type": "clause", "offset": [6708, 6720]}, {"key": "the-activity", "type": "definition", "offset": [6848, 6860]}, {"key": "nature-of", "type": "clause", "offset": [6895, 6904]}, {"key": "common-security", "type": "definition", "offset": [6940, 6955]}, {"key": "high-level", "type": "definition", "offset": [7053, 7063]}, {"key": "security-and", "type": "clause", "offset": [7067, 7079]}, {"key": "user-interface", "type": "clause", "offset": [7131, 7145]}, {"key": "provide-a", "type": "definition", "offset": [7227, 7236]}, {"key": "where-appropriate", "type": "definition", "offset": [7318, 7335]}, {"key": "measuring-outcomes", "type": "clause", "offset": [7337, 7355]}], "snippet": "The overall evaluation design involves randomly assigning youth to one of two different conditions: treatment (special services) or control (usual care). This design is referred to as a randomized control trial (RCT). The treatment group will receive a variety of evidence-based services above and beyond what they would otherwise be provided. The control group will receive the services traditionally provided by the system. Pre-randomization Data Collection and Transmittal Random Assignment Database Each youth who is deemed eligible for participation will be randomized to either the treatment or control. After eligibility has been established, the Intake Worker of the [Primary Service Provider] will log into a secure web application, referred hereafter as the \u201cRandom Assignment Database,\u201d using a pre-assigned username and password. The Random Assignment Database is used for randomly assigning youth and creating an electronic record of the random assignment outcome. After logging into the system, the Intake Worker enters the county-issued Youth Identification Number (YIN) for the youth to be randomized. The Intake Worker then enters the YIN in a separate field, and both entries are required to match in order to help minimize errors in data entry. The Intake Worker will be prompted that the YIN must match in order to proceed. If the numbers match, the Intake Worker then selects the county from where the youth was referred from a drop-down menu of pre-defined sites. After selecting the referring county, the Intake Worker certifies that all the information is correct by checking a box and then formally submits the information. After the information is submitted, the Intake Worker is immediately shown a screen that provides the random assignment outcome (i.e., treatment or control) for that specific youth. After the Intake Worker clicks enter, all the data from the web application session is saved in an underlying database (described in the following section). The Intake Worker is presented with a new screen that indicates whether the youth is assigned to special services or control. The database automatically generates an e-mail record of the randomization outcome, referring county, site ratio (refer to Randomization Procedures), and the data and time when the outcome was generated. The underlying database stores a comprehensive record of the user session, which is described in Appendix B. Random Number Methodology The randomization function inside the application is implemented as follows: /** * Return the next random number in the sequence * @param type $offset int last position in random sequence * @return type float next random number in sequence between 0 and 1 */ private function getNextRandom($offset) { mt_srand(74481); // Random seed. $nextRandom = -1; // Loop through the sequence until we reach the next new number for ($i = 0; $i <= $offset; $i++) { $nextRandom = mt_rand(0, mt_getrandmax() - 1) / mt_getrandmax(); } return $nextRandom; } It is executed on each request to add a new subject: $totalSubjects = $this->Subject->find('count'); ; $nextRandom = $this->getNextRandom($totalSubjects); if ($nextRandom < $site['Site']['site_ratio']) { $groupID = 1; // treatment group} else {$groupID = 2; // control group } In a web environment, each request is detached from all previous requests and the entire application state (excluding the database, but including the random generator) is reset. As a result, it is necessary to seed the random number generator and walk through the sequence from the beginning every time a new random number is required. The getNextRandom() function takes an offset parameter (which in this code is the number of subjects in the database at the time of the request) and returns a floating point number. The function will return the \u201coffset+1\u201dth number in the sequence, which will be used to determine the assignment We are using mt_rand() function for the number generation, which is PHP\u2019s Mersenne Twister implementation (as documented at \u2587\u2587\u2587\u2587://\u2587\u2587\u2587.\u2587\u2587\u2587/manual/en/function.mt-rand.php). The PHP function takes two arguments - a starting integer and an ending integer - and returns a single integer. Because site ratios are specified in decimal percentage values (e.g., 0.5000 for 50%), we normalize the range of results to floating point numbers between 0.0 (inclusive) and 1.0 (exclusive). This normalization is accomplished by giving mt_rand() the integer range of \u201c0 through the maximum integer size on the system (typically 2147483647) minus one,\u201d and then dividing that number by the maximum integer size. This will return a floating point number between 0.0 (inclusive) and 1.0 (exclusive), and is easily demonstrated with two simple calculations. (Note that site_ratio can have a maximum of four decimal places, so 0.9999 is the largest ratio possible less than 1.0000.) It should be noted that a random seed will be set to validate the random generation sequence. This random seed will remain confidential and shared only with the Validator. mt_getrandmax() returns 2147483647, so substituting: Minimum value of mt_rand(0, 2147483647 - 1) = 0 0 / 2147483647 = 0.0 Minimum floating point result = 0.0 Maximum value of mt_rand(0, 2147483647 - 1) = 2147483646 2147483646 / 2147483647 = 0.99999999953 Maximum floating point result = 0.99999999953 The assignment to the treatment group is then a simple matter of ensuring that the generated random number was less than the site ratio. Site Architecture The Random Assignment Database and application are deployed on University of Michigan servers managed by the University of Michigan\u2019s IT Services. The database is a standard MySQL database hosted on the University\u2019s MiDatabase service (\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587.\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/midatabase) and access to the database is \u2587\u2587\u2587\u2587://\u2587\u2587\u2587.\u2587\u2587\u2587/manual/en/function.mt-rand.php \u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587.\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/midatabase restricted to users and applications inside the University\u2019s network. In our configuration, the database is only directly accessible by the Random Assignment application, secured by the University firewall and database access controls, and is not accessible by any other users or applications inside or outside the University network. The web application itself is hosted on a server provided and managed by the University\u2019s Web Application Hosting service (\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587.\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/web-application-hosting) and the security of the server itself, including operating system patches and other security maintenance operations, are managed by the University to University standards. The application is implemented in PHP. Rather than implement an entire security system and database abstraction layer from the ground up, the decision was made to use an existing PHP Model-View-Controller framework. CakePHP (\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/) was chosen due to its maturity, the activity of its community, the well-tested nature of its security libraries (preventing common security exploits like SQL injection attacks), and its comprehensive documentation, all of which ensure a high level of security and provide extra assurance of project continuity. The user interface for both data entry and administration is implemented using Twitter Bootstrap to provide a standard, mobile-friendly grid-based layout, and Knockout.js and jQuery are used where appropriate. Measuring Outcomes and Implementation", "samples": [{"hash": "fflELZKbDBk", "uri": "/contracts/fflELZKbDBk#evaluation-design", "label": "Memorandum of Understanding", "score": 24.1704312115, "published": true}], "hash": "02756322b1009dcffa193632474fe5e0", "id": 10}], "next_curs": "CloSVGoVc35sYXdpbnNpZGVyY29udHJhY3RzcjYLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhpldmFsdWF0aW9uLWRlc2lnbiMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"size": 25, "parents": [["methodology", "Methodology"], ["general-program-requirements", "GENERAL PROGRAM REQUIREMENTS"], ["enforcement-of-budget-neutrality", "Enforcement of Budget Neutrality"], ["demonstration-evaluation-activities-and-interim-findings", "Demonstration Evaluation Activities and Interim Findings"], ["evaluation", "Evaluation"]], "children": [["timeline", "Timeline"], ["state-additions", "State additions"], ["evaluator", "Evaluator"], ["assurances-needed-to-obtain-data", "Assurances Needed to Obtain Data"], ["study-design", "Study Design"]], "title": "Evaluation Design", "id": "evaluation-design", "related": [["evaluation-cycle", "Evaluation Cycle", "Evaluation Cycle"], ["evaluation-period", "Evaluation Period", "Evaluation Period"], ["schematic-design", "Schematic Design", "Schematic Design"], ["study-design", "Study Design", "Study Design"], ["development-plan", "Development Plan", "Development Plan"]], "related_snippets": [], "updated": "2025-07-07T16:38:45+00:00", "also_ask": [], "drafting_tip": null, "explanation": "The Evaluation Design clause outlines the framework and methodology by which a project's outcomes or performance will be assessed. It typically specifies the criteria, metrics, and processes to be used for evaluation, such as timelines for assessment, responsible parties, and data collection methods. By clearly defining how success or progress will be measured, this clause ensures transparency and accountability, helping all parties understand expectations and reducing disputes over project results."}, "json": true, "cursor": ""}}