360Giving Data Standard fields for publishing grants to organisations - #SHARED

	A	B	C	D	E	F
1	360Giving Data Standard fields for publishing grants to organisations
2	Required fields are in green and the recommended ones are in yellow. To be used for mapping to internal system field names.
3
4	360Giving field name	Example 360Giving data	What is it?	Data Type	Internal system field name	Notes
5	Identifier	360G-ExampleFunder-001	A unique identifier for the grant. This is created by combining your publisher prefix (issued by 360Giving), starting with 360G, with a unique ID from your system. If you don't have a system, a unique ID should be created for the grant. 360Giving can support you to create these identifiers.	string (text)
6	Title	Grant to Orange Gardens	Short text (140 characters) about the grant OR Filler text for example "Grant to recipient org name"	string (text)
7	Description	Towards the rebuilding of the historic orangery	Description of the purpose of the grant. No text limit but it's recommended to be one or two sentences long only. Use clear language to communicate about funded work, people supported, aims of the project etc. Can reuse Title text, or use generic information about the grant programme. Check carefully for personal data.	string (text)
8	Amount Awarded	25000	Total amount awarded formatted as a number. No currency symbols or commas	string (text)
9	Currency	GBP	Currency code for your grants E.g. GBP = British Pounds	number
10	Award Date	2022-09-05	Date when the grant was awarded, usually board or panel meeting date. Must be formatted YYYYMMDD. Can use proxy dates first or last of month, quarter or year.	date-time
11	Recipient Org:Name	Orange Gardens	The name of the recipient, as collected in your system, doesn't have to be the official registered name, however please try to avoid acronyms.	string (text)
12	Recipient Org:Identifier	GB-CHC-1092948	Unique but consistent identifier for the recipient organisation. These are created using official identifiers, such as charity or company numbers and a prefix for the applicable register. If no official identifier available, the unique ID needs to be created using using the publisher prefix and the organisation name or identifier from your system. 360Giving can support you to create these identifiers.	string (text)
13	Funding Org:Name	Example Funder	Funder name, using preferred brand. The name shared in this field is used as the organisation name across all 360Giving tools.	string (text)
14	Funding Org:Identifier	GB-CHC-1112346	Unique but consistent identifier for the funding organisation, which is created using official identifiers, such as charity or company numbers. If no official identifier available, need to create the unique ID using the publisher prefix	string (text)
15	Recipient Org:Charity Number	1092948	Include if the organisation has a charity number. Only include the properly formatted number, no other text. If there is no charity number, leave the field blank.	string (text)
16	Recipient Org:Company Number	00945932	Include if the organisation has a company number. Only include the properly formatted number including leading zeros. If there is no company number, leave the field blank. If organisation has a charity number, don't need company number as well	string (text)
17	Grant Programme:Title	Major grants	Name of the programme grants awarded under. Ensure consistency so grants can be correctly grouped together. Further information can be provided in grant programme description field.	string (text)
18	Planned Dates:Start Date	2020-09-05	Date when the grant is supposed to start. Must be formatted YYYYMMDD. Can publish start and end dates, OR duration, or both	date-time
19	Planned Dates:End Date	2022-03-04	Date when the grant is supposed to end. Must be formatted YYYYMMDD. Can publish start and end dates, OR duration, or both.	date-time
20	Planned Dates:Duration (months)	18	Duration is in months, so 1 year = 12. The duration of the funding OR time period over which funding needs to be spent. Can publish start and end dates, OR duration, or both.	string (text)
21	Last modified	2023-09-19T00:00:00Z	Information about when the data in the file was last modified. This is meta data, which is data about the data. This field helps users know if they have the latest version. Must be in datetime format YYYYMMDDthh:mm:ssZ	date-time
22	Data Source	https://www.example.com	Information about the organisation that published the data. This is meta data, which is data about the data. This field helps users know the source of the information. Must be formatted as URL with https:// or http:// prefix	uri (website url)
23	Beneficiary Location:Name	Cardiff	A place name, based on project delivery area or where people served are based. Funder or recipient area of operation can also be used. Can be multiple beneficiary locations, if delivery is in more than one place.	string (text)
24	Beneficiary Location:Geographic Code	W06000015	Official ONS geocodes can be matched to place name(s). Including geocodes means that the location of the grants can be mapped and analysed. We have lookup tools available to help turn postcodes or names into geocodes, so please contact 360Giving for help and advice if you need it.	string (text)
25	Beneficiary Location:Country Code	GB	The 2 character ISO Country Code of the location of this activity. For example, the United Kingdom is GB, the Republic of Ireland is IE	string (text)
26	Location scope	GLS030	A codelist with seven categories and corresponding codes that can be used to describe the geographical scope of the funded work, ranging from global to local areas. For example, GLS030 code indicates that a grant has a National scope. It is also possible to indicate when a grant has an undefined location, for example, because the funded activity is online with no restrictions to who can access it.	string (text)
27	Recipient Org:Postal Code	CF10 1DZ	Recipient location is usually taken from the organisation address. Can be branch, project location or head office. If postcodes could be from an individual's private address, convert to geocodes instead. Please contact 360Giving for help and advice if you need it.	string (text)
28	Recipient Org:Location:Name	Cardiff	In cases when it isn’t possible or appropriate to publish postal codes, it is possible to publish the recipient location in the form of a location name. This data is most useful when accompanied with corresponding Office for National Statistics (ONS) geocodes using the Recipient Org:Location:Geographic Code field.	string (text)
29	Recipient Org:Location:Geographic Code	W06000015	A code referring to a geographical area, drawn from an established gazetteer. For example, the code for a local authority ward, or parliamentary constituency. Please contact 360Giving for help and advice if you need it.	string (text)
30	Funding Type	Project costs	Information about the type of funding provided by the grant. Example text that can be used in this field are Unrestricted, Running costs, Project costs, Salary costs, Capital, Capital and running costs, Regranting	string (text)
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100