Update from the SDG working Group - draft guidance available for review

(IATI Technical Team) #1

Dear all,

The SDG working group set up after the 2018 TAG has been working hard and can now share the draft SDG guidance. Currently this only contains publishing guidance, and data use guidance will follow shortly.

We have aimed to create guidance that every organisation can use and that works for data users. We recognise that some organisations may choose to go beyond this, and the guidance does not stop them doing so.

Please do read over the document. We would like to hear from you as to whether or not the suggested guidance works for your organisation or data use needs, and your suggestions on how to make the guidance easier to understand. Please enter your thoughts into the google doc or on this Discuss post. There is also a proposal to implement the required codelist changes here.

Please can you add your comments by the 17 July. They will then be reviewed by the SDG working group.

A summary of the recommendations of the working group is below:


The SDG working group recommends that organisations should publish:

  • Goals and/or Targets using the <tag> element
  • Indicators using the result/indicator attribute

Recommendations and reasons for recommendations:

Recommended

  • Using the <tag> element is the most ‘vanilla’ way of reporting SDGs and aligns with CRS reporting. Everyone who can attach SDGs to their activities should be able to use this. Data users can also turn SDGs reported in other areas into tags (see section 3.2)

  • Using the <result/indicator/reference> element adds further details, by ‘tagging’ an SDG Indicator to a result and aligning it with the organisation’s internal indicators. It allows SDGs to be published at an outcome level, providing additional detail to the <tag> element. We recognise that not every organisation will be able to do this.

Other areas where SDGs could be reported (not recommended)

  • Using the<policy-marker>, whilst similar to the <tag> element, adds complexity and diverges from CRS reporting.

  • The majority of the group were not in favour of using the <sector> element for SDGs. This adds complexity, is not financially accurate and requires SDGs to add up to 100%. However, it is recognised that some publishers may want to use this option in the future. The UN agencies are one example but further discussion about how it is best for them to do so needs more exploration. In the SDG guidance, we do not recommend the <sector> element being used.

  • There is no direct mapping between the DAC sector codes and the SDGs. Previous comparisons have been carried out and the results do not allow a mapping to take place and place barriers to data interpretation on data users.

Other points to note

  • The guidance is only guidance. It has been developed with a view to introducing conformity in published data to benefit end users by providing better comparability. It is not mandatory and does not prevent a publisher from using a different method according to their own business models and internal processes.

  • This guidance is not being released along with a Standard upgrade. Accordingly, publishers are still governed by the existing rules and capabilities within the Standard.

5 Likes
[Approved] Add SDG goals and targets to the TagVocabulary codelist
(James McKinney) #2
  • Goals and/or Targets using the element

I assume a word is missing between “the” and “element”? (Perhaps it was eaten by an HTML filter.)

1 Like
(Amy Silcock) #3

Thanks @James_McKinney. You’re correct, I’ve added the <tag> back in.

1 Like