When you are supporting a programme as important as Growing Up in New Zealand, trust is not a feature. It is the foundation. GUiNZ is one of New Zealand’s most significant longitudinal studies, following thousands of children and their families over many years. Its insights help inform decisions that affect children, whānau, and communities across the country. That gives the programme an unusual level of responsibility. It is not simply gathering information. It is stewarding relationships, protecting sensitive data, and helping generate evidence that shapes public understanding and public policy over time.
That context matters, because it changes what “good digital delivery” looks like.
For a programme like GUiNZ, digital systems are not just operational tools sitting in the background. They play a direct role in how participants experience the study, how easily they can stay involved, and how much confidence stakeholders can have in the continuity and integrity of the research itself. If the digital experience is clumsy, hard to trust, or unreliable under pressure, the consequences go beyond inconvenience. They can affect engagement, confidence, and momentum across the wider programme.
That was the backdrop to the GUiNZ HOME initiative: a digital front door designed to make it easier for whānau to connect with the study and complete key interactions in a secure, dependable environment. Assertio supported that journey by helping put in place the delivery foundations needed to make the platform production‑ready — including the underlying AWS environment, performance testing, contributions to test strategy, go‑live support, and operational readiness.
The challenge
At first glance, the challenge might sound straightforward: create a better digital channel for participants.
In practice, it was more demanding than that.
The HOME platform was intended to support important participant-facing interactions including completing consent documents, survey engagement, incentive facilitation, and insights sharing. That meant it needed to feel accessible and straightforward for users, while also operating inside the kinds of constraints that come with any high-trust digital environment: privacy expectations, security controls, reliability, and the need to perform consistently when real users arrive in volume.
That combination is where many projects become difficult. Building a front end is one thing. Creating a participant-facing platform that feels simple on the surface while standing on strong operational foundations underneath is something else entirely.
GUiNZ needed more than a functional interface. It needed a platform that could support a better participant experience without creating new delivery risk. The environment had to be secure by design, scalable enough for expected demand, and governed in a way that would stand up to scrutiny. Just as importantly, the path to production needed to be credible. Stakeholders needed confidence that the platform was ready, not merely available.
This is often the real challenge in digitally enabled research or public-interest environments. The work is not judged solely by whether something launches. It is judged by whether the service can be trusted, whether risks are being actively managed, and whether the delivery approach reflects the seriousness of the setting.
Why this mattered to GUiNZ
The business case for GUiNZ HOME was not only about modernisation. It was about continuity, engagement, and confidence.
Longitudinal research programmes depend on sustained cohort participation over time. That means the systems surrounding the programme need to facilitate participation. Digital engagement with families in the study is a core element of the GUiNZ programme. The HOME project sought to create a more structured digital destination for whānau. The architecture describes the platform as the home for GUiNZ whānau to connect and engage with the study. That language is important. It signals that this was not simply a transactional tool. It was designed as an engagement platform, a place to enhance the relationship between participant and programme. That gave the work a broader significance.
A stronger digital experience could help strengthen participation. A diligently-governed platform could support operational reliability. And a more scalable, tested environment would allow for growth, peak demand, and production readiness. Taken together, those things support the long-term function of the study.
The approach
The project was delivered under GUiNZ’s oversight, alongside creative partners supporting the wider initiative. Assertio was a principal technical partner, helping make the platform credible where it mattered most: in the underlying AWS foundations.
This was not just about provisioning infrastructure and walking away. The work centred on supporting the cloud environment, embedding security and compliance controls aligned with the University of Auckland policies, and helping validate that the platform was ready to perform under real-world conditions.
From a technology perspective, the architecture was designed on AWS and included a set of services that supported application deployment, identity, public access, storage, encryption, logging, access control, and secrets management. Infrastructure components were defined in Terraform and scanned using Checkov to help align with recognised security practices and compliance expectations. But the more important point for the case study is not the service list. It is what that approach enabled.
It enabled repeatability, which matters when teams need environments that are consistent and dependable. It enabled stronger security posture, because controls were part of the environment rather than an afterthought. And it enabled a more disciplined route to production, because the platform was being shaped around readiness, not just feature completion.
That distinction is worth highlighting. In many digital projects, success gets defined too narrowly around whether the application has been delivered. In practice, especially in sensitive environments, success depends just as much on the strength of the underlying platform and the maturity of the delivery process. Assertio’s contribution sat in that space.
Building confidence, not just infrastructure
One of the reasons this story is commercially useful is that it shows a more mature definition of delivery.
Assertio’s value lay not just in standing up AWS infrastructure, but in designing and validating it to scale reliably, giving the client confidence the platform could support thousands of participants, alongside client‑led user acceptance and readiness testing for end-to-end flows using realistic usage scenarios.
For GUiNZ, that matters because uncertainty is expensive. It slows decision-making, increases pressure before go-live, and can leave teams exposed to avoidable operational or reputational risks after launch. The more a partner can reduce uncertainty through sound architecture, embedded controls, and evidence-based validation, the more useful that partner becomes.
Assertio helped GUiNZ move from a delivery question — can we launch this? — to a better operational question — can we launch this with confidence?
Performance testing and production confidence
Performance testing was one of the most important parts of that confidence-building process.
The value was not in producing statistics for reporting, but in providing a realistic evidence-based view of how the platform would perform under increased participant demand and where issues still needed to be addressed before production cutover. The performance testing focused on what mattered for the HOME platform: registration, login, and survey activity, grounding the results in user behavior rather than abstract technical tests. That gave GUiNZ a clearer view of the platform’s readiness in real‑world use.
Just as importantly, the testing achieved two things.
First, it helped confirm that the infrastructure was stable and that the platform could credibly support expected demand.
Second, it surfaced practical issues that needed attention before production. The report notes issues related to repeated temporary password sending, email service quota limits in test, error handling and user messaging when email services were unavailable, and release alignment gaps between environments.
That is exactly why performance testing matters in a case like this. Its value is just not proving the system can cope but in uncovering weaknesses that would otherwise surface later as support incidents, user confusion, or production risk. In this case, the testing helped strengthen readiness rather than certify progress. The report ultimately concludes that from a performance perspective, GUiNZ HOME was ready for production cutover.
That conclusion matters, and so does the route taken to reach it. Confidence was not assumed. It was earned through validation.
What made the difference
What distinguished this work was not a single technical component but the way delivery discipline, assurance, programme needs were brought together to client timelines.
GUiNZ was not seeking digital change for its own sake. It needed an additional option to support participant engagement in a setting where trust and continuity were critical. Assertio’s role focused on supporting the foundations that influence long‑term reliability: secure cloud infrastructure, consistent delivery practices, embedded controls, and structured readiness checks.
This contribution reflects an approach centred on assurance rather than leading with technology for its own sake. The emphasis was on helping ensure the technology was shaped, governed, and validated in a way that supported the client’s objectives. In this case, this meant contributing to a platform that was functional, resilient, and better prepared for real-world use.
From a commercial perspective, this speaks to a role many clients value from a partner. They do not just need someone who can implement. They need someone who can provide informed support that helps reduce risk and increase confidence as systems move towards production.
Why this matters beyond one platform
The significance of the work extends beyond the Home platform itself. The Secure Research Platform in AWS places GUiNZ’s technology investment within a broader programme of modernising secure data access, collection, and presentation across public and private cloud environments. Seen in that context, the Home initiative is not an isolated delivery, but one step in strengthening the digital foundations around a long-running national research programme. The focus was on enabling a more sustainable, scalable, and secure way for participants to stay connected with the study over time.
For Assertio, that makes the case study useful beyond this individual context. It demonstrates experience working within environments that involve shared accountability, multiple stakeholders, and no tolerance for delivery risk – settings where careful execution and validation matter.
Outcome
GUiNZ HOME provided the programme with a strengthened digital channel foundation for participant engagement.
For GUiNZ, that meant a structured and dependable platform through which whānau could connect with the study. It meant a platform supported by security and compliance controls aligned to University of Auckland policies, clearer validation activity, and increased confidence in production readiness.
For Assertio, the outcome reflects a supporting role focused on assurance, helping validate readiness, contributing to risk reduction and treating infrastructure as an enabler of reliable participant experience rather than background concern.
In the end, that is what makes this story worth telling.
Improving the participant experience on the front end. Strengthening the technical foundations underneath and supporting a careful transition to production in a research programme where reliability and trust are essential.
That context matters, because it changes what “good digital delivery” looks like.
For a programme like GUiNZ, digital systems are not just operational tools sitting in the background. They play a direct role in how participants experience the study, how easily they can stay involved, and how much confidence stakeholders can have in the continuity and integrity of the research itself. If the digital experience is clumsy, hard to trust, or unreliable under pressure, the consequences go beyond inconvenience. They can affect engagement, confidence, and momentum across the wider programme.
That was the backdrop to the GUiNZ HOME initiative: a digital front door designed to make it easier for whānau to connect with the study and complete key interactions in a secure, dependable environment. Assertio supported that journey by helping put in place the delivery foundations needed to make the platform production‑ready — including the underlying AWS environment, performance testing, contributions to test strategy, go‑live support, and operational readiness.
The challenge
At first glance, the challenge might sound straightforward: create a better digital channel for participants.
In practice, it was more demanding than that.
The HOME platform was intended to support important participant-facing interactions including completing consent documents, survey engagement, incentive facilitation, and insights sharing. That meant it needed to feel accessible and straightforward for users, while also operating inside the kinds of constraints that come with any high-trust digital environment: privacy expectations, security controls, reliability, and the need to perform consistently when real users arrive in volume.
That combination is where many projects become difficult. Building a front end is one thing. Creating a participant-facing platform that feels simple on the surface while standing on strong operational foundations underneath is something else entirely.
GUiNZ needed more than a functional interface. It needed a platform that could support a better participant experience without creating new delivery risk. The environment had to be secure by design, scalable enough for expected demand, and governed in a way that would stand up to scrutiny. Just as importantly, the path to production needed to be credible. Stakeholders needed confidence that the platform was ready, not merely available.
This is often the real challenge in digitally enabled research or public-interest environments. The work is not judged solely by whether something launches. It is judged by whether the service can be trusted, whether risks are being actively managed, and whether the delivery approach reflects the seriousness of the setting.
Why this mattered to GUiNZ
The business case for GUiNZ HOME was not only about modernisation. It was about continuity, engagement, and confidence.
Longitudinal research programmes depend on sustained cohort participation over time. That means the systems surrounding the programme need to facilitate participation. Digital engagement with families in the study is a core element of the GUiNZ programme. The HOME project sought to create a more structured digital destination for whānau. The architecture describes the platform as the home for GUiNZ whānau to connect and engage with the study. That language is important. It signals that this was not simply a transactional tool. It was designed as an engagement platform, a place to enhance the relationship between participant and programme. That gave the work a broader significance.
A stronger digital experience could help strengthen participation. A diligently-governed platform could support operational reliability. And a more scalable, tested environment would allow for growth, peak demand, and production readiness. Taken together, those things support the long-term function of the study.
The approach
The project was delivered under GUiNZ’s oversight, alongside creative partners supporting the wider initiative. Assertio was a principal technical partner, helping make the platform credible where it mattered most: in the underlying AWS foundations.
This was not just about provisioning infrastructure and walking away. The work centred on supporting the cloud environment, embedding security and compliance controls aligned with the University of Auckland policies, and helping validate that the platform was ready to perform under real-world conditions.
From a technology perspective, the architecture was designed on AWS and included a set of services that supported application deployment, identity, public access, storage, encryption, logging, access control, and secrets management. Infrastructure components were defined in Terraform and scanned using Checkov to help align with recognised security practices and compliance expectations. But the more important point for the case study is not the service list. It is what that approach enabled.
It enabled repeatability, which matters when teams need environments that are consistent and dependable. It enabled stronger security posture, because controls were part of the environment rather than an afterthought. And it enabled a more disciplined route to production, because the platform was being shaped around readiness, not just feature completion.
That distinction is worth highlighting. In many digital projects, success gets defined too narrowly around whether the application has been delivered. In practice, especially in sensitive environments, success depends just as much on the strength of the underlying platform and the maturity of the delivery process. Assertio’s contribution sat in that space.
Building confidence, not just infrastructure
One of the reasons this story is commercially useful is that it shows a more mature definition of delivery.
Assertio’s value lay not just in standing up AWS infrastructure, but in designing and validating it to scale reliably, giving the client confidence the platform could support thousands of participants, alongside client‑led user acceptance and readiness testing for end-to-end flows using realistic usage scenarios.
For GUiNZ, that matters because uncertainty is expensive. It slows decision-making, increases pressure before go-live, and can leave teams exposed to avoidable operational or reputational risks after launch. The more a partner can reduce uncertainty through sound architecture, embedded controls, and evidence-based validation, the more useful that partner becomes.
Assertio helped GUiNZ move from a delivery question — can we launch this? — to a better operational question — can we launch this with confidence?
Performance testing and production confidence
Performance testing was one of the most important parts of that confidence-building process.
The value was not in producing statistics for reporting, but in providing a realistic evidence-based view of how the platform would perform under increased participant demand and where issues still needed to be addressed before production cutover. The performance testing focused on what mattered for the HOME platform: registration, login, and survey activity, grounding the results in user behavior rather than abstract technical tests. That gave GUiNZ a clearer view of the platform’s readiness in real‑world use.
Just as importantly, the testing achieved two things.
First, it helped confirm that the infrastructure was stable and that the platform could credibly support expected demand.
Second, it surfaced practical issues that needed attention before production. The report notes issues related to repeated temporary password sending, email service quota limits in test, error handling and user messaging when email services were unavailable, and release alignment gaps between environments.
That is exactly why performance testing matters in a case like this. Its value is just not proving the system can cope but in uncovering weaknesses that would otherwise surface later as support incidents, user confusion, or production risk. In this case, the testing helped strengthen readiness rather than certify progress. The report ultimately concludes that from a performance perspective, GUiNZ HOME was ready for production cutover.
That conclusion matters, and so does the route taken to reach it. Confidence was not assumed. It was earned through validation.
What made the difference
What distinguished this work was not a single technical component but the way delivery discipline, assurance, programme needs were brought together to client timelines.
GUiNZ was not seeking digital change for its own sake. It needed an additional option to support participant engagement in a setting where trust and continuity were critical. Assertio’s role focused on supporting the foundations that influence long‑term reliability: secure cloud infrastructure, consistent delivery practices, embedded controls, and structured readiness checks.
This contribution reflects an approach centred on assurance rather than leading with technology for its own sake. The emphasis was on helping ensure the technology was shaped, governed, and validated in a way that supported the client’s objectives. In this case, this meant contributing to a platform that was functional, resilient, and better prepared for real-world use.
From a commercial perspective, this speaks to a role many clients value from a partner. They do not just need someone who can implement. They need someone who can provide informed support that helps reduce risk and increase confidence as systems move towards production.
Why this matters beyond one platform
The significance of the work extends beyond the Home platform itself. The Secure Research Platform in AWS places GUiNZ’s technology investment within a broader programme of modernising secure data access, collection, and presentation across public and private cloud environments. Seen in that context, the Home initiative is not an isolated delivery, but one step in strengthening the digital foundations around a long-running national research programme. The focus was on enabling a more sustainable, scalable, and secure way for participants to stay connected with the study over time.
For Assertio, that makes the case study useful beyond this individual context. It demonstrates experience working within environments that involve shared accountability, multiple stakeholders, and no tolerance for delivery risk – settings where careful execution and validation matter.
Outcome
GUiNZ HOME provided the programme with a strengthened digital channel foundation for participant engagement.
For GUiNZ, that meant a structured and dependable platform through which whānau could connect with the study. It meant a platform supported by security and compliance controls aligned to University of Auckland policies, clearer validation activity, and increased confidence in production readiness.
For Assertio, the outcome reflects a supporting role focused on assurance, helping validate readiness, contributing to risk reduction and treating infrastructure as an enabler of reliable participant experience rather than background concern.
In the end, that is what makes this story worth telling.
Improving the participant experience on the front end. Strengthening the technical foundations underneath and supporting a careful transition to production in a research programme where reliability and trust are essential.
Planning a secure, governed digital platform? Assertio helps organisations build the cloud and AI foundations, controls, and delivery confidence needed for production-ready systems.