<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="SLV_2009_MCC-NTH_v01_M" xml-lang="en" xmlns="http://www.icpsr.umich.edu/DDI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.icpsr.umich.edu/DDI http://www.icpsr.umich.edu/DDI/Version1-2-2.xsd">
<docDscr>
  <citation>
    <titlStmt>
      <IDNo>DDI_SLV_2009_MCC-NTH_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="MCC" affiliation="" role="Metadata Production">Millennium Challenge Corporation</producer>
      <prodDate date="2014-12-17">2014-12-17</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 1.0 (December 2014)
Version 1.1 (January 2015) : Description of main outcomes, other.
Version 2.0 (April 2015). Edited version based on Version 01 (ddi-mcc-slv-socialimpact-connectivity-2014-v1) that was done by Millennium Challenge Corporation.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Northern Transnational Highway 2009-2014</titl>
      <subTitl/>
      <altTitl>MCC-NTH 2009-14</altTitl>
      <parTitl>Carretera Longitudinal del Norte</parTitl>
      <IDNo>SLV_2009_MCC-NTH_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="">Social Impact Inc.</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-04-01">NADA</software>
      <fundAg abbr="MCC" role="">Millennium Challenge Corporation</fundAg>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <contact affiliation="Millennium Challenge Corporation" URI="" email=" impact-eval@mcc.gov">Monitoring &amp; Evaluation Division</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Independent Impact Evaluation</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date="">Raw data for internal use only</version>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
      <keyword vocab="" vocabURI="">Roads</keyword>
      <keyword vocab="" vocabURI="">Transport</keyword>
      <keyword vocab="" vocabURI="">Impact evaluation</keyword>
      <keyword vocab="" vocabURI="">Continous treatment</keyword>
      <keyword vocab="" vocabURI="">Regression discontinuity</keyword>
      <topcClas vocab="" vocabURI="">El Salvador</topcClas>
      <topcClas vocab="" vocabURI="">Roads</topcClas>
      <topcClas vocab="" vocabURI="">Impact evaluation</topcClas>
      <topcClas vocab="" vocabURI="">Continous treatment</topcClas>
      <topcClas vocab="" vocabURI="">Regression Discontinuity</topcClas>
    </subject>
    <abstract>The benefits of the connectivity project will be measured using a rigorous impact evaluation methodology. An impact evaluation is a study that measures changes in outcomes affecting wellbeing that can be attributed to a specific intervention. Impact evaluations require a credible and rigorously defined counterfactual that estimates what would have happened to the beneficiaries in the absence of the project. Estimated impacts, when contrasted with total related costs, provide an assessment of the intervention’s cost effectiveness.

It is expected that this project will reduce transportation costs and enable households to extend their labor activities and diversify their income sources. The first questions are related to the project outputs (direct products of the program, such as segments of the NTH constructed, etc.) as opposed to outcomes or impacts (changes access to markets, changes in income).  


Some questions that will be addressed in the impact evaluation:

• Was the NTH implemented according to plan? 
• Did the NTH reach the originally intended beneficiaries? Did it reach unintended population or sectors of the economy? 
• Does access to the improved NTH improve market participation by increasing the likelihood of going to the market and/or the volume sold in the market?
• Does access to the improved NTH increase income from agricultural sources?
• Does access to the improved NTH increase the availability of non-farm employment and promote the creation of non-farm enterprises?
• Does access to the improved NTH increase the use of public services? Specifically, health and education services?</abstract>
    <sumDscr>
      <collDate date="2009" event="start" cycle="Baseline"/>
      <collDate date="2010" event="end" cycle="Baseline"/>
      <collDate date="2010" event="start" cycle="Follow-up 1"/>
      <collDate date="2011" event="end" cycle="Follow-up 1"/>
      <collDate date="2011" event="start" cycle="Follow-up 2"/>
      <collDate date="2012" event="end" cycle="Follow-up 2"/>
      <collDate date="2012" event="start" cycle="Follow-up 3"/>
      <collDate date="2013" event="end" cycle="Follow-up 3"/>
      <collDate date="2013" event="start" cycle="Follow-up 4"/>
      <collDate date="2014" event="end" cycle="Follow-up 4"/>
      <nation abbr="SLV">El Salvador</nation>
      <geogCover>The connectivity project initially consisted of a network of connecting roads (NCR) and the Northern Transnational Highway but because of the significant increase in construction costs and the existence of other interventions in connecting roads the project only focused on the Northern Transnational Highway. As a result of these changes the current impact evaluation design focuses only on the evaluation of the Northern Transnational Highway.</geogCover>
      <geogUnit/>
      <anlyUnit>Households</anlyUnit>
      <universe>The population being analyzed consists of the people living within a 30 minute radius of the NTH. This region (the Northern Zone) contains one-half of El Salvador’s poorest municipalities and suffered more damage from the country’s internal conflict during the 1980s than any other region. Economic and social indicators in the Northern Zone are currently worse than the national averages.</universe>
      <dataKind>Sample survey data [ssd]</dataKind>
    </sumDscr>
    <!-- qualityStatement - ddi2.5 - complex type
     
     This structure consists of two parts, standardsCompliance and otherQualityStatements. 
     In standardsCompliance list all specific standards complied with during the execution of this 
     study. Note the standard name and producer and how the study complied with the standard. 
     Enter any additional quality statements in otherQualityStatements.
     
     -->
    <qualityStatement>
      <standardsCompliance>
        <standard>
          <standardName/>
          <producer/>
        </standard>
        <complianceDescription/>
      </standardsCompliance>
      <otherQualityStatement/>
    </qualityStatement>
    <notes/>
    <!-- exPostEvaluation ddi2.5
      Use this section to describe evaluation procedures not address in data evaluation processes. 
      These may include issues such as timing of the study, sequencing issues, cost/budget issues, 
      relevance, instituional or legal arrangments etc. of the study. 
      
      The completionDate attribute holds the date the evaluation was completed. 
      The type attribute is an optional type to identify the type of evaluation with or without 
      the use of a controlled vocabulary.
    -->
    <exPostEvaluation completionDate="" type="">
      <evaluationProcess/>
      <outcomes/>
    </exPostEvaluation>
  </stdyInfo>
  <method>
    <dataColl>
      <timeMeth/>
      <dataCollector abbr="" affiliation="">Social Impact</dataCollector>
      <dataCollector abbr="DIGESTYC" affiliation="El Salvador National Statistics">Dirección General de Estadísticas y Censos - El Salvador National Statistics</dataCollector>
      <!-- collectorTraining - DDI2.5
        
        Collector Training

        Describes the training provided to data collectors including internviewer training, process testing, 
        compliance with standards etc. This is repeatable for language and to capture different aspects of the 
        training process. The type attribute allows specification of the type of training being described.
        
        -->
      <collectorTraining type=""/>
      <frequenc/>
      <sampProc>The household survey for the connectivity impact evaluation interviewed 3,450 households at baseline. There was high attrition in the first two follow-up surveys (2010 and 2011), with few of the households lost in the follow-up being regained in 2011. In the 2012 round, the evaluator implemented a farther-reaching tracking of the baseline households and were able to recuperate more households, bringing the effective sample size in the 2012 survey to 3,065 households. For the endline survey in 2014, the evaluator will continue to track down the baseline households that are still missing and, to the extent possible, use methods that are robust to unbalanced panel data in the final analysis.</sampProc>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat/>
      <collMode/>
      <resInstru>Quantitative Household Survey: The baseline and endline survey questionnaire includes two sections – one (including questions about household income and agricultural productivity) that is answered by the male head of household who is interviewed by a male survey taker and one (including questions about household demographics, time allocation, and expenses) which is answered by a female in the household, i.e. spouse or female household head, who is interviewed by a female survey taker.

Quantitative and Qualitative Community Survey: The community survey was administered to key informants in communities where selected households live; each section of the survey was administered to the better-informed informant.</resInstru>
      <!-- instrumentDevelopment - DDI2.5             
        Describe any development work on the data collection instrument. Type attribute allows for the optional use of a defined development type with or without use of a controlled vocabulary.
        -->
      <instrumentDevelopment type=""/>
      <collSitu>The surveys took place from November to February of the indicated years.</collSitu>
      <actMin>Interviewing was conducted by teams of interviewers. Each interviewing team comprised of 3-4 interviewers,  and a supervisor, and a driver.

The role of the supervisor was to coordinate field data collection activities, including management of the field teams, supplies and equipment, finances, maps and listings, coordinate with local authorities concerning the survey plan and make arrangements for accommodation and travel. Additionally, a chief field supervisor assigned the work to the supervisors/interviewers, spot checked work, maintained field control documents, and sent completed questionnaires and progress reports to the central office.  

The team 2 coordinators for data entry and quality control that were responsible for managing the headquarter team reviewing each questionnaire, checking for missed questions, skip errors, fields incorrectly completed, and checking for inconsistencies in the data.  
For the follow-up surveys electronic devices where specifically programmed for the survey that automatically performed checks of the data in the field.</actMin>
      <ConOps/>
      <weight/>
      <cleanOps>The evaluator will produce cleaned raw datasets that follows MCC’s guidelines for public use data, including programming syntax used to clean the datasets for documentation purposes. 

A full set of documentation for each survey will be provided. The raw data and the data used for the final analysis will be provided. A public use version of analysis data files will be provided. The publicly available version will be anonymized, and thus free of personal or geographic identifiers that would permit identification of individual respondents or their household members.</cleanOps>
    </dataColl>
    <notes/>
    <anlyInfo>
      <respRate/>
      <EstSmpErr/>
      <dataAppr/>
    </anlyInfo>
    <stdyClas/>
    <dataProcessing type=""/>
    <codingInstructions relatedProcesses="" type="">
      <txt/>
      <command formalLanguage=""/>
    </codingInstructions>
  </method>
  <dataAccs>
    <setAvail>
      <accsPlac URI="http://data.mcc.gov/evaluations/index.php/catalog/135">Millennium Challenge Corporation</accsPlac>
      <origArch>Millennium Challenge Corporation
http://data.mcc.gov/evaluations/index.php/catalog/135
Cost: None</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <restrctn/>
      <citReq/>
      <deposReq/>
      <conditions/>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
