Functionally, yes. Parent/guardian consent is given via a checkbox when accepting an event invitation. This consent is tied to the event details already in the system rather than a separate form.

No. The system includes an approval workflow aligned to formation approvals (Section Leader → Group Leader → District Commissioner), but this does not replace the traditional C5 process.

No - there appears to be no specific way to add custom questions to an event. We have raised this a development opportunity with Consent2Go.

Documents can be uploaded to events and profiles and made available for extended periods however, they are not live automatically across all events eg gear list. They are specific to each event created and are visible links on the invite page for parents/guardians.

No - the system permits only one price point per event, unless you allow them to pay later and include content in the payment box related to those options.

Yes. Events show attending, not attending and no response statuses and reports can be downloaded for attendance, medical, catering and activity-specific needs. You can tap on a profile on an event to mark them as 'present'.

Payments are processed via Stripe, connected at the formation (group/district) level. This mirrors Operoo’s setup. There remains a Stripe fee as part of the payment processing and is included in the value you set for the event. Consent2Go does not charge additional fees like Operoo did.

Yes. Events can require payment as part of accepting an event invitation and disable “pay later” options.

This use case (e.g. PlayOn credits, volunteers) has been identified and raised. The simple answer is No - if you have turned off pay later options. Credits will need to be applied to an activity for which payments are not required in Consent2Go.

You can only have one unique Stripe account attached to Xero which is setup through Xero online payments. The Stripe link is 'powered' by Xero and a unique Stripe account is setup. Most groups will have two accounts - one for Xero and one a generic Stripe account. 

1. A non-Xero powered Stripe account needs to be linked to Consent2Go.
2. Stripe deposits a payment into Xero.
3. The deposit needs to coded on the Xero 'bank rec' screen. Possibly use either the 260 Registration Fees - Activities or 261 Registration Fees - Camp fees account codes in Xero or your relevant account code if the chart of accounts has been modified. They also are able to use Xero tracking codes if needed.
4. Attach the Stripe balance report and Consent2Go report so you don't need to raise Xero invoices.

Additional words from a District Treasurer - It does require logging into Stripe, but it is managed with one payment coming into the main bank account reconciled off the spreadsheet from Stripe identifying who paid but listing it as a bulk amount. Rather than payments coming through Stripe Xero bank feed which singularly lists them.  State Office recommended ceasing using the Xero Stripe bank feed system, which State Office ceased in 2025, due to ongoing issues. The amounts paid through Consent2Go/Stripe are not recorded against the individual profiles. No invoices are set up to reconcile so it doesn't matter.  If a credit is needed, then the credit would be against the individual's profile to be used at a later date.

Raw data is fed into Xero for our bank reconciliation. In Xero we allocate each payment to their family code to ensure we can reconcile each activity and if necessary, issue a credit note if the youth member is no longer able to come.  The data that is being captured in Stripe and fed into Xero has no unique identifier as to the participant in a sperate column to import in the bank feed. 

The workaround is to open Stripe, go to each unique record and identify the family from the email the receipt was sent to.

In the Description Field however the Participants name in captured in Brackets in Column K.  The problem, however with this is that the Bank Feed into Xero is limited to only a few characters and therefore the name is not able to be imported.  I could shorten the name of the activity to ensure the participants name also is captured in the spaces required in Xero field however, it would more than likely not make sense to Parents on their receipt if we shortened the activity name in Consent2Go.

Essentially there is more work required if Xero is directly connected to Stripe/Consent2Go as you cannot see who made what payment easily.

State Office will discuss with the developers however, the two current options are to slowly work through as Albany Creek has suggested or do not form a connection with Xero and use bulk payments only from Stripe to Xero.

We are attempting to avoid stating that Consent2Go is a replacement for Operoo as it is a completely different system that does some of what Operoo did. Some of the functions are a replacement however, the entire system is not. It is also a temporary replacement / stepping stone. Scouts Queensland has longer-term plans for a more integrated system later in 2026/early 2027 that will be of enormous benefit to our members.

Consent2Go should be used once profiles are live although it is not mandatory for a formation to use Consent2Go.

Events after Operoo shutdown on 31 January will need to be recreated in Consent2Go. If an event in Operoo is needing to be accessed after 31 January then you will need to run the event another way as all Operoo access ceases on 31 January 2026.