CRCNA sample project agreements

Deprecated function: Return type of Drupal\google_analytics\Component\Render\GoogleAnalyticsJavaScriptSnippet::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 10 of modules/contrib/google_analytics/src/Component/Render/GoogleAnalyticsJavaScriptSnippet.php).

include('/home/crcna/public_html/modules/contrib/google_analytics/src/Component/Render/GoogleAnalyticsJavaScriptSnippet.php') (Line: 571)
Composer\Autoload\includeFile('/home/crcna/public_html/modules/contrib/google_analytics/src/Component/Render/GoogleAnalyticsJavaScriptSnippet.php') (Line: 428)
Composer\Autoload\ClassLoader->loadClass('Drupal\google_analytics\Component\Render\GoogleAnalyticsJavaScriptSnippet') (Line: 372)
google_analytics_page_attachments(Array) (Line: 315)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}(Object, 'google_analytics') (Line: 405)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('page_attachments', Object) (Line: 316)
Drupal\Core\Render\MainContent\HtmlRenderer->invokePageAttachmentHooks(Array) (Line: 289)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 290)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 132)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 142)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 174)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 270)
Drupal\shield\ShieldMiddleware->bypass(Object, 1, 1) (Line: 137)
Drupal\shield\ShieldMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

Any individual or organisation participating or contributing to a CRCNA project is required to sign an agreement with the CRCNA.

The table below provides an overview of the different types of agreements between the CRCNA and our participants. You can click on the agreement type to review a sample agreement.

Agreement types	Description	When agreements are applied
Head Agreement	A research agreement which is legally binding between CRCNA and the research provider. This agreement type is our main contract, formalising the researchers’ obligations to undertake the project and achieve the milestones as described in Annexure B. Annexures A B C D E form a head agreement, with a title page. Annexure A - provides an overview of the investment to date from research provider Annexure B - is the Project Plan which forms the basis of the collaborative research agreement between all participants and co-funders Annexure C - special conditions as negotiated Annexure D Terms of Agreement Annexure E - CRC Standard terms	Where a participant is receiving and/or contributing funds – cash expenditure to the project and is responsible for milestone delivery.
Participant Declaration (in-kind only)	This declaration acknowledgement stipulates the contributions a participant will contribute to the individual project The participant should have all rights, title, licences, interests, property, and regulatory approvals necessary to lawfully perform its obligations under the Participant Declaration and schedule – project plan	Participant declarations are used when a participant is not expending any cash but is contributing in-kind only through FTE amounts and/or non-staff in-kind contribution to the project.
Contribution Deed (cash + in-kind)	This is an agreement contracting a project participant who is providing a cash contribution (or cash plus in-kind). They are listed as a participant but are not carrying out specific activities.	The participant is nominated as a participant, contributing cash (or cash plus in-kind) but not expending it. They are not responsible for delivering activities.
Deed of variation	This deed is used when CRCNA and a research provider agree to vary the terms of their currently executed agreement. Changes will be specified in the deed.	A DOV will be issued to participants with head agreements that need a formal variation to their agreement by changes to a project and/or contracted financials.
DoV via written agreement	A written agreement either by email or letter confirming simple variation request.	An email can be used to confirm a simple variation such as : Change of name of participant or contact details Corrections to typos or omissions which don’t fundamentally alter the Plan or agreement A letter co-signed by lead participant or co-funder can be used to confirm: Extension of project end date where it does not impact on the end date reported in the Commonwealth Agreement Value of the milestone Overall budget Financial year
Participant declaration - notice of variation/ variation letters	Where there is a formal change to a project and/or contracted financials this will apply to participants to legally advise change/s	Project participants and/or Co funders will be formally advised of any project plan variations.

Error message

CRCNA sample project agreements

Agreement types

Description

When agreements are applied