<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="STP_2011_MCC-T_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_STP_2011_MCC-T_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="MCC" affiliation="" role="Review of Metadata">Millennium Challenge Corporation</producer>
      <prodDate date="2014-04">2014-04</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 1.0 (April 2014)
Version 2.0 (April 2015). Edited version based on Version 01 (DDI-MCC-STP-IE-2011-v01) that was done by Millennium Challenge Corporation.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Threshold 2011</titl>
      <subTitl/>
      <altTitl>MCC-T 2011</altTitl>
      <parTitl/>
      <IDNo>STP_2011_MCC-T_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="">Duca Consulting International</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-04-08">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 Performance Evaluation</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date="">- v01:  Edited, anonymous dataset for public distribution.</version>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
                  
                  
    </subject>
    <abstract>This report is a summative evaluation of the Millennium Challenge Corporation's (MCC) Threshold Country Program (TCP) for São Tomé and Príncipe. The program was formally launched through a Memorandum of Understanding in November 2007. The MCC contracted with the U.S. Department of the Treasury's Office of Technical Assistance (OTA) for implementation of the program; field work commenced in January 2008. 
This evaluation covers three of the four major components of the TCP: 
-Increase tax revenue through higher voluntary compliance with tax laws; 
-Increase tax revenue through strengthened tax enforcement; and 
-Improve the business environment. 

The objectives established for this ex-post evaluation are to: 
-document the implementation of activities and inputs proposed in the TCP plan; 
-gauge the extent to which intended outcomes and program goals were achieved; 
-assess the clarity and appropriateness of program design; 
-understand shared roles and responsibilities in the success of the program; and 
-present findings that may prove useful to all stakeholders in future TCP programming. 

The evaluation's findings were based on Document Review and Key-Informant Interviews. The Evaluation Team conducted direct interviews with respondents in São Tomé, in Lisbon, and via both one-on-one and telephone interviews with TCP managers and consultants in the U.S. Findings in the Monitoring and Evaluation (M&amp;E) Contract's Phase II report, along with MCC's and OTA's comments on them, were also important sources for this final report.</abstract>
    <sumDscr>
      <collDate date="2011" event="start" cycle=""/>
      <collDate date="2011" event="end" cycle=""/>
      <nation abbr="STP">São Tomé and Príncipe</nation>
      <geogCover/>
      <geogUnit/>
      <anlyUnit/>
      <universe/>
      <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/>
      <!-- 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/>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat/>
      <collMode/>
      <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/>
      <actMin/>
      <ConOps/>
      <weight/>
      <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/89">Millennium Challenge Corporation</accsPlac>
      <origArch>Millennium Challenge Corporation
http://data.mcc.gov/evaluations/index.php/catalog/89
Cost: None</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <confDec required="no" formNo="" URI=""/>
      <restrctn/>
      <citReq/>
      <deposReq/>
      <conditions/>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
