The IGDA special interest group “Developer Credit” promotes best practices for how credits are attributed, affecting career and awards prospects.  The guidelines are available for sharing in video form at  Links are indexed below.



INCL.1 Five percent or 30 days


INCL.1-1 Time in days, not hours


INCL.1-2 Total workdays in lead role


INCL.1-3 Non-leads


INCL.2 Person who leaves company


INCL.3 Fired or engaged in illegal activity


INCL.4 Legacy credit


INCL.4-1 Re-releases or acquired properties


INCL.4-2 Ported games


INCL.4-3 Expansion packs


INCL.4-4 Sequels or franchise installments


INCL.5 [Optional] Original creation of tools, assets


INCL.6 [Optional] Special thanks credit


ATTR.1 Name and role


ATTR.2 Credits for work in like disciplines


ATTR.2-1 Where a conflict arises


ATTR.2-2 Noteworthy team members


ATTR.2-3 Geographically separate teams


ATTR.3 Leads first


ATTR.4 Senior distinctions not used


ATTR.5 Developer credits listed first


ATTR.6 Identical credit


ATTR.7 Number of multiple credits; disavow


ATTR.7-1 Role performed in less than 30 days


ATTR.7-2 Fewer credits that are broader in scope…


ATTR.7-3 Managers supervising multiple disciplines


ATTR.7-4 Leads serving exclusively managerial…


ATTR.7-5 Single managerial credit


ATTR.8 [Optional] Refusing credit


ATTR.9 [Optional] Discipline order list


ATTR.9-1 Multi-platform development


ATTR.9-2 Discipline order


ATTR.10 [Optional] Specially created credit


ATTR.11 [Optional] Standardized roles


ATTR.12 Nickname credits


ATTR.13 Fictional credits


USAG.1 Credits must appear in the actual game…


USAG.1-1 When to credit by URL


USAG.1-2 Port, expansion, adaptation, re-release credit


USAG.2 Credits not hidden or locked


USAG.3 Printed manual credits


USAG.4 Right to list credit in resume


METH.1 Establish approach


METH.2 Final review


METH.3 Cap on multiple credits


METH.4 [Optional] Regular review


METH.5 [Optional] Designated credits keeper


METH.6 [Optional] Accessible credit records