Question:
Is the current CMS Kentico?

Does TIQ intend on remaining with Kentico or moving to a new CMS?

Answered on 09/Dec/2025 03:42 PM:


TIQ is moving away from Kentico 13 specifically which will reach end of life December 2026.

Other Kentico products can be considered (as with any CMS/DXP) that meets our requirements from a system and vendor perspective.

Question:
We note the requirement for “two UAT/staging environments.” Can you confirm whether separate UAT environments are mandatory, or if an equivalent approach (e.g., secured preview/draft review, version control) that has been accepted by other government customers will be considered compliant?

Answered on 15/Dec/2025 03:02 PM:


The current UAT and Production structure is not necessarily required for a future state. Suppliers are encouraged to advise how the three (3) different websites - Trade and Investment Queensland, Migration Queensland and Study Queensland - can exist on the one (1) UAT and one (1) Production environment without data and user error concessions, i.e.

- clear separation for the 3 websites within the UAT and Production environments for, e.g., secured preview/draft preview and version control which is accepted and compliant with Queensland Government requirements;

- easy modulation and migration of individual sites both from current state to new state;

- easy future modulation and migration of individual sites in the event of a MoG (Machinery of Government).

If possible, options ranging from how the supplier can meet requirements with only one (1) UAT and one (1) Production environment through to three (3) UAT and three (3) Production environments is welcomed.

Question:
Good afternoon,

I have noted in the TIQ26.029-Website_Content_Management_System_and_Support_Services-ITO-Final, 1.6 Documents in the Invitation to Offer which Supplier needs to complete and return

for the contract tterms it states - The Supplier is to complete and return the documents which are provided as part of this Invitation to Offer.

QITC Comprehensive Contract Details – ICT Products and Services



but when I open the contract details document, it contains a watermark - For information only, not to be completed.

Should we be filling this out and returning it or not?

Tash

Answered on 15/Dec/2025 12:13 PM:


Please note the QITC Comprehensive Contract Details - ICT Products and Services document does not require suppliers to complete on return of ITO submission. The preferred supplier will be required to work with TIQ to complete the final contract.

Question:
Could you please clarify the total number of page visits, combined for the three sites, annually?

What is your average Page Size?

What is your broad regional % breakdown of traffic - split between North America & Europe, APAC, and Middle East / Mediterranean / Africa

What percentage of visitors are desktop vs mobile?

Answered on 23/Dec/2025 02:42 PM:


"In the past 12 months, indicative page-view metrics for the websites in scope are as follows:

- Site 1: ~337,000 views

- Site 2: ~1,600,000 views

- Site 3: ~85,000 views

A 10–20% year-on-year growth in traffic across all sites is expected. These figures can be used to support CMS licensing estimates."

Supplier to assume industry average of 2.5MB.

Traffic breakdowns will not be provided to suppliers at this stage.

Approximately 70% Desktop, approximately 30% mobile/tablet over three (3) sites.

Question:
What are the domain names that are in scope?

How many pages are there currently across all sites? Are they all to be migrated across to the new WCMS?

What is the size of the digital media assets storage?

Outside of the web and social channels, does TIQ also manage other customer communication channels such as email marketing, native apps, kiosks / digital signage, or print publications?

Answered on 15/Dec/2025 03:01 PM:
(edited on 18/Dec/2025 03:50 PM)


We have 6 domains pertaining to 3 sites that are in scope for this project.

Question:
Can TIQ confirm the number and specific websites currently in scope, how these map to the three business areas, and whether all three business areas/sites are included in the initial implementation?

Does TIQ have any indicative timelines, sequencing expectations, or priority sites for the initial CMS implementation and migration activities, or is TIQ expecting suppliers to propose delivery timelines as part of their response and/or subsequent Statements of Work?

Can TIQ clarify whether the initial CMS implementation is expected to involve a visual and/or structural redesign of existing websites, or whether the intent is primarily a like-for-like lift-and-shift / migration of existing designs and content into the new CMS?

Where redesign or re-templating is in scope, can TIQ confirm whether the Supplier is expected to: 1) provide UX/UI design services, 2) implement designs provided by TIQ, or 3) deliver a like-for-like implementation of existing designs with minimal visual change?

Does TIQ have an objective to standardise visual design and components across sites and business areas, or should each site retain its existing visual identity and layouts as part of the initial implementation?

Are any accessibility or compliance-driven design changes anticipated as part of the CMS transition (e.g. to meet WCAG 2.2 AA), or should suppliers assume existing designs are largely compliant and can be migrated as-is?

If a broader redesign is anticipated, does TIQ envisage this occurring as part of the initial CMS implementation, or as a separate, future phase following CMS migration?

Does TIQ have a site-by-site feature or functional requirements list (e.g. content types, integrations, forms, search behaviour, personalisation, events, analytics) for the websites in scope? If so, can this be provided, or should suppliers assume a common baseline of CMS features across all sites for the initial implementation?

Has TIQ completed a content inventory or audit across the websites in scope, including page counts, document volumes, media assets and content types? If so, can this be provided?

Can TIQ clarify whether decisions regarding content rationalisation, archiving and de-duplication will be led by TIQ, or whether suppliers are expected to provide analysis and recommendations as part of the migration effort?

Can TIQ outline the core page templates and components expected at launch, and whether templates/components should be standardised across all sites or vary by business unit?

How are events currently managed (within the CMS or via a third-party platform), and what level of integration or synchronisation is expected?

Approximately how many active content users exist today, and what roles (author, editor, publisher, admin, developer) do they perform?

What content approval workflows are currently in place across TIQ sites, and what are the key pain points TIQ is seeking to address?

For “inclusive methods to preview and review content”, who requires access (internal, external, public), and should preview access be authenticated or shareable via secure links?

Can TIQ provide indicative detail on content volumes (pages, documents, media assets), the number of current CMS platforms, and any known content quality or archival challenges?

What CMS platforms are the websites in scope currently using, and are multiple CMS platforms involved? (We understand Kentico may be in use.)

Is multi-language content currently in use? If so, which languages are required at launch, and are additional languages anticipated during the contract term?

Can TIQ describe the current site search implementation and any known limitations it is seeking to address?

Is personalisation (geo- or persona-based content) currently implemented on any TIQ sites? If so, using what technology, and what level of capability is required?

Can TIQ confirm the specific integrations required per site at launch (e.g. CRM, analytics, DAM, forms, events)?

How does TIQ currently use Bynder? Do the current CMS platform(s) integrate with Bynder, and is ongoing integration required?

Is AI or chatbot functionality currently in use on any TIQ sites? If so, what technology is used today?

Can TIQ clarify expected peak concurrent visitor volumes, and whether the “100,000s” requirement reflects observed usage, forecast growth, or an upper bound?

Can TIQ provide any indicative content volume and page-view metrics for the websites in scope (e.g. over the past 12 months) to support CMS licensing estimates, or should suppliers assume baseline volumes to be confirmed post-award?

Answered on 18/Dec/2025 02:51 PM:
(edited on 23/Dec/2025 02:49 PM)


3 sites are in scope for this project.

An indicative implementation and migration project schedule is required with timeframes, high-level tasks and key resources. Target completion date of the project and subsequent go-live is mid June 2026, if not earlier.

The initial CMS implementation will mainly be a like-for-like migration.

There are no UX/UI design services required for this ITO opportunity. It will be a like-for-like lift and shift for e.g. existing templates.

The long-term goal is to standardize designs, but for this migration, each site will keep its current look and layout.

"Current site designs are not fully accessibility compliant. During migration, sites may need adjustments to meet standards (e.g., WCAG 2.2 AA).

Suppliers should not assume designs can be migrated. Accessibility improvements may also be addressed after migration if there will be timeline impacts to make identified changes. if there will be timeline impacts to make identified changes."

"This migration focuses on moving existing sites into the new CMS with minimal visual changes.

"

Suppliers should assume a common baseline of CMS features across all sites with primarily a functional requirements approach for use of the CMS. There may be a requirement for a site to have a feature which is not required on the other sites. Please advise how you are are able to deliver on functional and ad hoc feature requirements.

"TIQ hasn’t done a formal content audit, but we can provide estimates:

About 600 pages across all sites

Around 10 GB of media assets (PDFs, images, videos)"

TIQ will lead decisions about which pages to archive for all sites. Supplier advice about e.g. de-duplication and content optimisation will be captured as part of the migration process.

"Each site has:

- one or two core page templates

- one or two core event listing templates

- one or two collapsable/expandable accordion templates

- several slider/featured content templates"

Events are currently manually published on the websites via the existing CMS. TIQ does not currently have an events platform, or program, bulit into the existing CMS.

"TIQ has about 10 active CMS users.

Admins: 2-4 per site

Editors: Up to 10 users for authoring, editing, and publishing

Developers: It's expected that the successful supplier will be undertaking the Developer role."

TIQ does not currently use workflows in its existing CMS; however, TIQ remains open to using the best practice options available. Timeframes to implement the preferred solution is limited so introducting a new way of using a CMS may not be achievable for the intial rollout.

We currently provide preview access for internal stakeholders via our UAT sites. At present, we use authentication-based access for these previews. Suppliers are welcome to advise of secure preview options for external partners.

TIQ has one (1) CMS platform with two (2) separate instances of the application. Across the three sites, there are approximately 600 pages in total. Media libraries collectively contain around 10 GB of assets, including but not limited to e.g. PDF documents, images, and video files.

TIQ currently using the one (1) CMS platform.

Current multi langauge use is specific to office locations and focused on landing pages which are manually translated.

"The current site search implementation is keyword-based, which limits its ability to deliver relevant or intuitive results.

As part of the CMS migration, TIQ would like to implement a more intuitive search experience, ideally incorporating features such as advanced filtering, predictive search, and improved relevance ranking. (These are desirable but not mandatory). "

"No, personalisation (geo- or persona-based content) is not currently implemented on any TIQ sites.

There is no existing technology or capability for personalisation, and it is not a requirement for the initial CMS migration."

Integrations are as per the requirements in the ITO. The examples given in the question are all part of the requirements.

"TIQ marketing uses Bynder as its Digital Asset Management (DAM) system. The current CMS platform does not integrate with Bynder, and there is no existing integration in place.

While integration with Bynder is not a requirement for the initial CMS migration, TIQ would prefer that any proposed CMS solution offers the option for future integration to support ongoing utilisation of Bynder."

"No, AI or chatbot functionality is not currently in use on any TIQ websites.

There is no existing technology or integration for these capabilities, and they are not part of the initial CMS migration requirements."

The 100,000s requirement is upper bound for specific campaigns increasin site traffic. Typical monthly volumes are below 50,000. The preferred supplier will need to be able to articulate how it manages 'bursts' of traffic - planned and unplanned - without site degradation, i.e. slowness and lack of availability (outage).

"In the past 12 months:

TIQ: ~337K views

MQ: ~1.6M views

SQ: ~85K views

Traffic is expected to grow 10–20% YoY. Use these figures for CMS licensing estimates."

Question:
1. If the Supplier can demonstrate a secure Multi-Site Architecture—where a single CMS Core powers all three business unit websites (TIQ, MQ, SQ) with distinct branding and separate user permissions—would the Customer accept this as a valid response to the requirement?

2. Aside from the current system reaching "End of Life," what are the specific problems or frustrations you experience with the current CMS that you definitely do not want to see in the new platform?

3. To assist with accurate project scheduling, could the Customer provide an estimate of the current volume of content assets to be migrated? (Approximate number of Pages, PDFs, and Images).

4. Is there an approved budget range and timeline allocated for the initial build and transition phase?

5. Regarding the design approach: Is the intention to "Lift and Shift" the current look and feel into the new CMS, or are you seeking a redesign of the User Interface components to fix current usability issues?

6. To ensure the solution is future-proof, we plan to propose a "Hybrid Headless" architecture using the Drupal CMS. We believe this stack is the best fit because it offers the strict security compliance you need (for forms and audit logs) while giving you the API flexibility to integrate with Salesforce and Bynder easily. Can TIQ confirm if a Drupal-based solution aligns with your internal IT roadmap and technology preferences?

7. How should we price the "Highly Desirable" and "Optional" requirements?

If we include all these features in the main price, it could increase the total cost by 20-30% due to the extra setup effort. To ensure you can compare vendors fairly, should we provide a "Base Price" for the Mandatory items and list the others separately, or would you prefer a single total figure that includes everything?

8. Can you list exactly which third-party integrations must be fully connected and working by the "Go Live" date? The requirements list many tools (Salesforce, Bynder, Hotjar, etc.) as "Mandatory" or "Desirable." While our solution includes ready-made connectors for most of these, we need to know which ones you want us to set up during the project so we can accurately calculate the delivery effort.

9. Does TIQ permit the use of offshore development resources for the software build phase, provided that the Prime Contractor is Australian-based and all live data remains strictly hosted within Australia?

Answered on 18/Dec/2025 02:54 PM:
(edited on 23/Dec/2025 02:53 PM)


"Yes. If the supplier can provide a secure multi-site CMS that powers all three sites (TIQ, MQ, SQ) with separate branding and user permissions, that meets our requirement.

We also prefer clear separation between UAT and Production environments for proper testing and deployment."

No specific issues related to current CMS

"Across the three sites, there are approximately 600 pages in total.

Media libraries collectively contain around 10 GB of assets, including PDF documents, images, and video files."

An indicative implementation and migration project schedule is required with timeframes, high-level tasks and key resources. Target completion date of the project and subsequent go-live is mid June 2026.

The intention is primarily a “Lift and Shift” of the current look and feel into the new CMS.

TIQ is seeking a user friendly platform due to limited internal resources however future proofing is a part of the innovation critera in the procurement process.

Pricing is at the descretion of the supplier

The pricing proposal provided is at the discretion of the supplier and needs to be in line with QITC frameworks. Separation between mandatory and desirable will assist understanding the offer.

As per the requirements, the mandatory items are required for go-live. CRM and Google reCAPTCHA are mandatory for operational reasons.

Inline with Queensland Governments Family and Small Business Policy, preferences for work to be sourced in Australia where possible.

Question:
1. Are the three websites managed independently in separate CMS environments, or are they managed under a single CMS environment using a multi-site setup?

2. Is a design refresh included as part of this project, or are the existing designs expected to remain largely unchanged?

3. Which hosting model is preferred: managed hosting within the customer’s TIQ Azure cloud environment, or a supplier-hosted SaaS model?

4. You have specified a requirement to scale to hundreds of thousands of concurrent site visitors. Can you share any historical analytics or traffic data to help vendors understand realistic traffic patterns?

5. The requirements mention “data interpretation where possible.” Can you clarify what types of data you expect to be interpreted?

Answered on 18/Dec/2025 02:55 PM:
(edited on 23/Dec/2025 02:57 PM)


TIQ has one (1) CMS platform with two (2) separate instances of the application.

The requirements are as per the ITO documentation, with the detailed requirements in TIQ26.029 Website Content Management System and Support Services - Part A - Appendix 1 - Requirements.

Requirement requests the supplier to provide the best option to suit the ITO requirements and terms. Both options are listed for response.

The 100,000s requirement is upper bound for specific campaigns increasin site traffic. Typical monthly volumes are below 50,000. The preferred supplier will need to be able to articulate how it manages 'bursts' of traffic - planned and unplanned - without site degradation, i.e. slowness and lack of availability (outage).

Any available data related to the CMS such as usage, performance, and content analytic (if applicable)