It is now several months since Bellberry updated its procedures and we are pleased to report that there has been a significant drop in start-up times for additional sites.

The table beneath is a comparator of Jan/Mar 2020 to 2021. These months have been chosen as Jan/Mar may pre-date any COVID related issues sites may have, and in December 2020, the grace period ceased.

Approval-Month Count of Applications Average of Bellberry Days
Jan-20 32 34
Jan-21 39 13.05
Feb-20 55 27.72
Feb-21 54 10.38
Mar-20 60 20
Mar-21 72 10.45

Amendments are tracking at the same turnaround time in Bellberry days (3.8 days). The updated model’s difference is we now ensure all sites are listed on the one approval letter, as appropriate.

We appreciate the teething issues as sites, sponsors, and our administration tackle the changes together. If you have any questions or you would like to schedule a call with the quality team to discuss the practicality of the changes at your site, please email alisonbarr@bellberry.com.au.

Document Updates

We recently made some minor changes to some of our documents and guidance for researchers. A summary of the changes can be found here.

FAQs relating to the process changes rolled out in late 2020

The Committee will want to see the radiation report (if above standard of care) and the wording from that report placed in the site-specific wording doc. The HREC notes the radiation report, whereas they approve the site-specific wording.

If the lead has already imbedded the radiation report wording of multiple sites into the Master PICF, then it would not need to be put in the site-specific doc.


Yes, if the lead selects pathway 2.

It is for the following reasons:

  • The sites are submitting it to confirm they aren’t making changes.
  • If there are ethical changes, then the RGO/other institutional representative has a point of reference that the HREC has reviewed the wording, and it is OK for inclusion. We hope that it can help with making the line clear between what is ethics and what is governance. Governance is then about adding administrative items (headers, footers, logos, local site complaints).
  • The real value in the document is post-approval. If the site is not changing any site-specific content, they are free to create a site-specific PICF on the same day as the Master is approved. Historically, they may have created it, but they would then need to submit it to the HREC and await approval. In discussion with sites, we found our former approach caused issues when a Master PICF had urgent safety updates, and sites were then waiting for their site-specific PICFs to be approved post Master.

When we audit a study, if we find ethical changes to the site-specific PICF that were not submitted in the site-specific clauses document, we will bring it to the PI’s attention. We recognise there is no clauses document for historical studies, so we would go by the previously approved site-specific PICF.

No, the site does not reference the version and date. The site only needs to reference which document their wording is going into (e.g. Master Main, Master Pregnancy).

If the lead has chosen pathway two, and each site has submitted a site-specific clauses document, if they never wish to change any ethical content in their site-specific PICF, we will never receive an update to that document for the rest of the study.

The clauses document is approved, and each time the Master is updated, they include their approved clauses in their site-specific version, which is approved via whatever mechanism they choose for their own site (e.g. Clin Trial Manager go-ahead, CRO sign off etc).

  1. Does not need to be listed in site-specific clauses document as the wording has been ethically approved in the Master PICF, so site deleting the not applicable section would be a known admin change.
  2. Copy and paste the deleted wording into the site-specific clauses template stating that it is not applicable and therefore deleted.

The correct answer is option 1.

No. It only holds up the site/s in question. Suppose it is something minor that could be dealt with swiftly. In that case, we will encourage our team to rectify the issue so approval for all sites can occur on the same day. If it appears that is not likely, sites 1 & 4 would be approved. Then, sites 2&3 would be approved when they have resolved their issues. Sites 2&3 are then provided with any approval letters that have been issued for the other sites if there are documents on there that are relevant to them (e.g. protocol, IB, Master PICF).

The BB website lists the FAQ below:

If I have an additional site what do I need to submit and when?”

“If the lead site has yet to be approved please submit your site application via eProtocol, however you do not need to attach any study documentation on page 7 of your application. If your lead site has already received HREC approval you will need to submit a full application including all your site’s study documentation on page 7”

 In this context, we define ‘full application’ to mean each site must complete an application in eProtocol and answer all questions. We don’t wish for the definition of ‘full application’ to relate to the uploading of core study documents such as the protocol, IB etc.

The additional sites are only responsible for uploading documents relating to them. The sort of items we would expect to see uploaded:

  • CV if not current within 12 months.
  • A site-specific form – if applicable.
  • Any other site-specific documentation that is not relevant to other sites – e.g. social media plan or local advertising.

The HREC administration keeps a record of the lead site’s PICF pathway at the initial submission. If a site tries to change the pathway, the HREC administration will return the documentation, along with an explanation that it does not match the study pathway. The only exception to this would be when a single centre study on PICF pathway 1 has changed to a multi-centre study. The Sponsor needs to determine who is responsible for unpacking the PICF and moving the study to PICF pathway 2 or 3. In this case, the submitting site should also explain the change in the pathway to the HREC. Providing as much information as possible will help the administrator understand why the documentation change is being submitted.

Please contact the Sponsor and get them to confirm with the site that submitted the initial application (lead) which pathway they would like the study to follow. Once you have confirmation, please attach any email correspondence that confirms the pathway and upload it with your application. If there is no correspondence, the HREC administrator will need to contact the lead site and ask which will potentially delay approval for the additional site.

The lead site only needs to choose a pathway. There may be some situations where updated documentation is required, but it should be rare.

For example, if they pick pathway 2, they do not need to send in site-specific clauses documents if we have already approved their site-specific PICF. Sites approved before the PICF pathways only need update the HREC with a site-specific clauses document if they are changing the wording from an already HREC approved site-specific PICF.

If the lead site chooses pathway 3, the only update required is if the Master PICF does not cover the requirements of the additional site that is being added. E.g. the radiation statement has two options, but the new additional site has different wording that isn’t already covered. The lead site would then need to submit an amendment with an update to the Master PICF. The amendment can come either before or after the additional site is approved. If it comes post-approval, the additional site will be delayed in creating its site-specific PICF. This is a matter for Sponsors and sites to work out what suits them best.

Please only submit electronic indemnities listing sites that have applied or are due to apply in the coming days. Bellberry will not execute indemnities that list sites that have not applied eProtocol.

If the indemnity is on paper, Bellberry will strike through the sites that haven’t applied in eProtocol.