Organisation level |
Organisation |
Organisation documents |
Fully compliant
|
2012-11-28 |
Annual report, overall strategy and country operational plan documents are included in the organisation file from August 2012. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2012-08-01 |
2012-11-28 |
Initial date later |
Notes |
Annual report, overall strategy and country operational plan documents are included in the organisation file from August 2012. |
Annual report, overall strategy and country operational plan documents are included in the organisation file from August 2012. |
No change |
|
Organisation |
Recipient country budgets |
Fully compliant
|
2012-11-28 |
We provide annual forward planning budget data related to the CSR period in the organisation file and in detail in operational plans and annual reviews. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We provide annual forward planning budget data related to the CSR period in the organisation file and in detail in operational plans and annual reviews. |
We provide annual forward planning budget data related to the CSR period in the organisation file and in detail in operational plans and annual reviews. |
No change |
|
Organisation |
Organisation budget |
Fully compliant
|
2012-11-28 |
We publish all information that is available as part of the organisation file, as annual budgets for DFID. We publish information within the Spending Review Period (4 years at a time, not on a rolling basis). The current CSR lasts from 2010 to financial year 2014/15. The financial year runs from April to March. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We publish all information that is available as part of the organisation file, as annual budgets for DFID. We publish information within the Spending Review Period (4 years at a time, not on a rolling basis). The current CSR lasts from 2010 to financial year 2014/15. The financial year runs from April to March. |
We publish all information that is available as part of the organisation file, as annual budgets for DFID. We publish information within the Spending Review Period (4 years at a time, not on a rolling basis). The current CSR lasts from 2010 to financial year 2014/15. The financial year runs from April to March. |
No change |
|
Organisation |
Funded institution budgets |
Partially compliant
|
|
We do not set budgets for individual institutions beyond our commitments to each institution. Budget data for institutions can be derived from the budgets published for each project in business cases. |
|
|
Identification |
Activity |
Reporting organisation |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
IATI Identifier |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
Other Identifier |
Fully compliant
|
2012-11-28 |
Based on the internal DFID activity identifier. |
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2012-09-01 |
2012-11-28 |
Initial date later |
Notes |
Based on the internal DFID activity identifier. |
Based on the internal DFID activity identifier. |
No change |
|
Basic activity information |
Activity |
Activity dates (End Date) |
Fully compliant
|
2012-11-28 |
The dates reflect the anticipated end date of the activity and not the actual date the activity ends. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
The dates reflect the anticipated end date of the activity and not the actual date the activity ends. |
The dates reflect the anticipated end date of the activity and not the actual date the activity ends. |
No change |
|
Activity |
Activity dates (Start Date) |
Fully compliant
|
2012-11-28 |
Start dates reflect the date DFID expect the activity to begin. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Start dates reflect the date DFID expect the activity to begin. |
Start dates reflect the date DFID expect the activity to begin. |
No change |
|
Activity |
Participating organisation (Accountable) |
Future publication
|
2014-12-01 |
Where the accountable organisations for on-budget aid are reported, the name of the government ministry responsible will be provided. This will be published by end 2014. |
N/A |
|
Activity |
Participating organisation (Funding) |
Fully compliant
|
2012-11-28 |
We define the UK government as the participating organistion (funding) |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We define the UK government as the participating organistion (funding) |
We define the UK government as the participating organistion (funding) |
No change |
|
Activity |
Participating organisation (Implementing) |
Fully compliant
|
2012-11-28 |
We currently only record the details for the first level of implementation (i.e. who we directly give our money to). DAC codes are used to identify the organisation type (eg type 12000 = Recipient Government) |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We currently only record the details for the first level of implementation (i.e. who we directly give our money to). DAC codes are used to identify the organisation type (eg type 12000 = Recipient Government) |
We currently only record the details for the first level of implementation (i.e. who we directly give our money to). DAC codes are used to identify the organisation type (eg type 12000 = Recipient Government) |
No change |
|
Activity |
Participating organisation (Extending) |
Fully compliant
|
2012-11-28 |
We define DFID as the extending organisation (extending) |
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We define DFID as the extending organisation (extending) |
We define DFID as the extending organisation (extending) |
No change |
|
Activity |
Title (Agency language) |
Fully compliant
|
2012-11-28 |
IATI and CRS return includes this information.
DFID publishes Project Summary documents in the major local languages of the country where appropriate which will contain this information, and the system allows for publication of a title in recipient languages. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
IATI and CRS return includes this information.
DFID publishes Project Summary documents in the major local languages of the country where appropriate which will contain this information, and the system allows for publication of a title in recipient languages. |
IATI and CRS return includes this information.
DFID publishes Project Summary documents in the major local languages of the country where appropriate which will contain this information, and the system allows for publication of a title in recipient languages. |
No change |
|
Activity |
Title (Recipient language) |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
Description (Agency language) |
Fully compliant
|
2012-11-28 |
IATI and CRS return includes this information.
DFID publishes Project Summary documents in the major local languages of the country where appropriate which will contain this information, and the system allows for publication of a description in recipient languages. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
IATI and CRS return includes this information.
DFID publishes Project Summary documents in the major local languages of the country where appropriate which will contain this information, and the system allows for publication of a description in recipient languages. |
IATI and CRS return includes this information.
DFID publishes Project Summary documents in the major local languages of the country where appropriate which will contain this information, and the system allows for publication of a description in recipient languages. |
No change |
|
Activity |
Description (Recipient language) |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
Contact information |
Fully compliant
|
2012-11-28 |
We publish DFID’s Public Enquiry Point details for all projects, rather than individuals contact details. This is a conscious decision as DFID does not publish the names of civil servants below Senior Civil Service level; people move around the organisation so may not still be in the same post; PEP can direct the enquiry immediately to the relevant person. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We publish DFID’s Public Enquiry Point details for all projects, rather than individuals contact details. This is a conscious decision as DFID does not publish the names of civil servants below Senior Civil Service level; people move around the organisation so may not still be in the same post; PEP can direct the enquiry immediately to the relevant person. |
We publish DFID’s Public Enquiry Point details for all projects, rather than individuals contact details. This is a conscious decision as DFID does not publish the names of civil servants below Senior Civil Service level; people move around the organisation so may not still be in the same post; PEP can direct the enquiry immediately to the relevant person. |
No change |
|
Activity |
Activity status |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Geopolitical information |
Activity |
Recipient country |
Fully compliant
|
2012-11-28 |
Only one recipient country OR region is recorded per child activity. (Hierarchy 2) |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Only one recipient country OR region is recorded per child activity. (Hierarchy 2) |
Only one recipient country OR region is recorded per child activity. (Hierarchy 2) |
No change |
|
Activity |
Recipient region |
Fully compliant
|
2012-11-28 |
Only one recipient country OR region is recorded per child activity. (Hierarchy 2) |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Only one recipient country OR region is recorded per child activity. (Hierarchy 2) |
Only one recipient country OR region is recorded per child activity. (Hierarchy 2) |
No change |
|
Activity |
Sub-national geographic location |
Fully compliant
|
2014-04-01 |
DFID provides sub-national geographic information in IATI and Development Tracker. DFID provides semi-automated geo-coded coordinates as data-sets for all projects, as set out in our Open Data Strategy, and pilots are underway to test the new format. |
1 |
|
Classifications |
Activity |
Flow type |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
Sector (DAC CRS) |
Fully compliant
|
2012-11-28 |
DFID specific sectors are mapped to the DAC sector codes. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
DFID specific sectors are mapped to the DAC sector codes. |
DFID specific sectors are mapped to the DAC sector codes. |
No change |
|
Activity |
Sector (Agency specific) |
Partially compliant
|
2012-11-28 |
The list of DFID specific codes are published in the Statistics on International Development (yearly in October). DFID specific sectors published through legacy data. |
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Partially compliant |
Partially compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
The list of DFID specific codes are published in the Statistics on International Development (yearly in October). DFID specific sectors published through legacy data. |
The list of DFID specific codes are published in the Statistics on International Development (yearly in October). DFID specific sectors published through legacy data. |
No change |
|
Activity |
Tied aid status |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
Policy marker |
Fully compliant
|
2012-11-28 |
DAC policy codes are used. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
DAC policy codes are used. |
DAC policy codes are used. |
No change |
|
Activity |
Collaboration type |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
Finance type |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Activity |
Aid type |
Fully compliant
|
2012-11-28 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
|
|
No change |
|
Financial |
Activity |
Budget identifier (Administrative/functional) |
Fully compliant
|
2014-03-01 |
Compliant with IATI 1.03, format still to be finalised. |
N/A |
|
Activity |
Budget identifier (Economic) |
Fully compliant
|
2014-03-01 |
Compliant with IATI 1.03, format still to be finalised. |
N/A |
|
Activity |
Budget |
Fully compliant
|
2012-11-28 |
Budgets are show by financial quarter through the financial year. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Budgets are show by financial quarter through the financial year. |
Budgets are show by financial quarter through the financial year. |
No change |
|
Activity |
Planned disbursement |
Future publication
|
|
We are unable to show planned disbursments at present, but will do so when systems are upgraded. |
|
|
Financial transaction |
Activity |
Transactions (Reimbursement) |
Partially compliant
|
2012-11-28 |
We are publishing reimbursement information but we are currently unable to distinguish between funding and reimbursement. There are currently no plans to take this any further. |
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Partially compliant |
Partially compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We are publishing reimbursement information but we are currently unable to distinguish between funding and reimbursement. There are currently no plans to take this any further. |
We are publishing reimbursement information but we are currently unable to distinguish between funding and reimbursement. There are currently no plans to take this any further. |
No change |
|
Activity |
Transactions (Disbursement / Expenditure) |
Fully compliant
|
2012-12-01 |
Transactions prior to May 2010 are aggregated quarterly and published.
We publish all individual transactions over £500.
If under £500 transactions are aggregated and then published (Dec-12).
|
1 |
|
Activity |
Transactions (Incoming Funds) |
Partially compliant
|
2012-11-28 |
These are recorded and published in the Annual Accounts (chapter 5). |
|
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Partially compliant |
Partially compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
These are recorded and published in the Annual Accounts (chapter 5). |
These are recorded and published in the Annual Accounts (chapter 5). |
No change |
|
Activity |
Transactions (Commitment) |
Fully compliant
|
2012-11-28 |
Not all activities at level 1 (project level) will have a transaction as these may be at level 2 (component level). All information is captured in MoUs, accountable grants and contracts (where contracts are the only written binding document). |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Not all activities at level 1 (project level) will have a transaction as these may be at level 2 (component level). All information is captured in MoUs, accountable grants and contracts (where contracts are the only written binding document). |
Not all activities at level 1 (project level) will have a transaction as these may be at level 2 (component level). All information is captured in MoUs, accountable grants and contracts (where contracts are the only written binding document). |
No change |
|
Activity |
Transactions (Loan repayment / interest repayment) |
Partially compliant
|
2012-11-28 |
Loans are managed by Export and Credit Guarantee Department (ECGD), some loans can be tracked however loans made prior to DFID being established cannot be linked to specific activities, and therefore difficult to show.
Details can be found in the DFID Annual Report & Accounts (Chapter 5) |
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Partially compliant |
Partially compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Loans are managed by Export and Credit Guarantee Department (ECGD), some loans can be tracked however loans made prior to DFID being established cannot be linked to specific activities, and therefore difficult to show.
Details can be found in the DFID Annual Report & Accounts (Chapter 5) |
Loans are managed by Export and Credit Guarantee Department (ECGD), some loans can be tracked however loans made prior to DFID being established cannot be linked to specific activities, and therefore difficult to show.
Details can be found in the DFID Annual Report & Accounts (Chapter 5) |
No change |
|
Related documents |
Activity |
Activity website |
Not applicable
|
|
No links available to point to specific activity information. |
N/A |
|
Activity |
Related activity |
Fully compliant
|
2012-11-28 |
Optional - DFID is using this section of the standard for parent/ sibling relationships under project/ component; not using multi-funded option |
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Optional - DFID is using this section of the standard for parent/ sibling relationships under project/ component; not using multi-funded option |
Optional - DFID is using this section of the standard for parent/ sibling relationships under project/ component; not using multi-funded option |
No change |
|
Activity |
Activity documents |
Fully compliant
|
2012-11-28 |
All activity documents including Business Cases published as of 1 January 2011, with annual and project completion reports published since April 2011. Also published are contracts and evaluations. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
All activity documents including Business Cases published as of 1 January 2011, with annual and project completion reports published since April 2011. Also published are contracts and evaluations. |
All activity documents including Business Cases published as of 1 January 2011, with annual and project completion reports published since April 2011. Also published are contracts and evaluations. |
No change |
|
Performance |
Activity |
Conditions (Attached Y/N) |
Fully compliant
|
2012-11-28 |
We currently publish whether conditions are attached to projects on DFID's project database site, but not on IATI. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
We currently publish whether conditions are attached to projects on DFID's project database site, but not on IATI. |
We currently publish whether conditions are attached to projects on DFID's project database site, but not on IATI. |
No change |
|
Activity |
Conditions (Text) |
Fully compliant
|
2012-11-28 |
Text of conditions is included in documents published on DFID's project database site. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
Text of conditions is included in documents published on DFID's project database site. |
Text of conditions is included in documents published on DFID's project database site. |
No change |
|
Activity |
Results |
Fully compliant
|
2012-11-28 |
All results data for financial year are published in Annual Reviews, project completion reports. Plan to publish via IATI in 2015. |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
2011-01-01 |
2012-11-28 |
Initial date later |
Notes |
All results data for financial year are published in Annual Reviews, project completion reports. Plan to publish via IATI in 2015. |
All results data for financial year are published in Annual Reviews, project completion reports. Plan to publish via IATI in 2015. |
No change |
|