Describe the need
Within GOB, describe the need is treated as part of partner-search and consortium requests. The project is designed to make this area useful to participating organizations through clear responsibilities, documented processes and a realistic understanding of available capacity. The aim is not to create ceremonial activity, but to help organizations become easier to understand, better prepared to cooperate and more capable of using opportunities that fit their own mission.
Implementation should remain consistent with the wider GOB framework. That means preserving the legal independence of member organizations, distinguishing project roles from public authority, protecting confidential information and avoiding promises that depend on an external partner, funder or institution. Where a programme, appointment or benefit is still under development, the public website should describe the direction accurately rather than presenting it as an established result.
- Clear scope for describe the need
- Documented responsibility and follow-up
- No unsupported claims or implied public authority
Protect sensitive information
Within GOB, protect sensitive information is treated as part of partner-search and consortium requests. The project is designed to make this area useful to participating organizations through clear responsibilities, documented processes and a realistic understanding of available capacity. The aim is not to create ceremonial activity, but to help organizations become easier to understand, better prepared to cooperate and more capable of using opportunities that fit their own mission.
Implementation should remain consistent with the wider GOB framework. That means preserving the legal independence of member organizations, distinguishing project roles from public authority, protecting confidential information and avoiding promises that depend on an external partner, funder or institution. Where a programme, appointment or benefit is still under development, the public website should describe the direction accurately rather than presenting it as an established result.
- Clear scope for protect sensitive information
- Documented responsibility and follow-up
- No unsupported claims or implied public authority
Match responsibly
Within GOB, match responsibly is treated as part of partner-search and consortium requests. The project is designed to make this area useful to participating organizations through clear responsibilities, documented processes and a realistic understanding of available capacity. The aim is not to create ceremonial activity, but to help organizations become easier to understand, better prepared to cooperate and more capable of using opportunities that fit their own mission.
Implementation should remain consistent with the wider GOB framework. That means preserving the legal independence of member organizations, distinguishing project roles from public authority, protecting confidential information and avoiding promises that depend on an external partner, funder or institution. Where a programme, appointment or benefit is still under development, the public website should describe the direction accurately rather than presenting it as an established result.
- Clear scope for match responsibly
- Documented responsibility and follow-up
- No unsupported claims or implied public authority
Formalize when needed
Within GOB, formalize when needed is treated as part of partner-search and consortium requests. The project is designed to make this area useful to participating organizations through clear responsibilities, documented processes and a realistic understanding of available capacity. The aim is not to create ceremonial activity, but to help organizations become easier to understand, better prepared to cooperate and more capable of using opportunities that fit their own mission.
Implementation should remain consistent with the wider GOB framework. That means preserving the legal independence of member organizations, distinguishing project roles from public authority, protecting confidential information and avoiding promises that depend on an external partner, funder or institution. Where a programme, appointment or benefit is still under development, the public website should describe the direction accurately rather than presenting it as an established result.
- Clear scope for formalize when needed
- Documented responsibility and follow-up
- No unsupported claims or implied public authority
Close the loop
Within GOB, close the loop is treated as part of partner-search and consortium requests. The project is designed to make this area useful to participating organizations through clear responsibilities, documented processes and a realistic understanding of available capacity. The aim is not to create ceremonial activity, but to help organizations become easier to understand, better prepared to cooperate and more capable of using opportunities that fit their own mission.
Implementation should remain consistent with the wider GOB framework. That means preserving the legal independence of member organizations, distinguishing project roles from public authority, protecting confidential information and avoiding promises that depend on an external partner, funder or institution. Where a programme, appointment or benefit is still under development, the public website should describe the direction accurately rather than presenting it as an established result.
- Clear scope for close the loop
- Documented responsibility and follow-up
- No unsupported claims or implied public authority
