Team Member Guide
Everything you need to navigate your Solution Site, work through the GAITS frameworks, and track your project's progress through the Healthcare Innovation Cycle.
Your access level
Every team member on GAITS has one of three access levels. Your access level is set by the person who invited you to the site — either your Site Admin or programme leadership. You can see your access level on your site's member list.
Most working team members will have Member access. If you need to invite others to your site or adjust settings, you will need Site Admin access — contact your current Site Admin or programme leadership to request this.
Your Solution Site
A Solution Site is your team's private workspace on the GAITS platform. It is created and assigned to your team by programme leadership, who also set the solution type (for example, MedTech, Digital Health, or Therapeutics) when the site is first configured. The solution type determines the specific set of Deliverables your team will work through.
To access your site, sign in to GAITS and go to My GAITS Sites from the platform hub. You will see a list of all the sites you have permission to access — including any project sites you are a member of, and (if you are a Site Admin on more than one site) any additional sites you manage.
What's in your Solution Site
Your Solution Site is organised around the Healthcare Innovation Cycle. The cycle has 10 stages — called Innovation Maturity Levels (IMLs) — and four dimensions: clinical, regulatory, commercial, and technical. All work in your site is structured within this framework.
At any given point, your site shows:
- Your team's current maturity level across each of the four dimensions
- The Work Packages and Deliverables that apply to your solution type at each stage
- A record of your team's progress, including pivots and completed milestones
- The names of your assigned mentors (if any have been assigned by programme leadership)
Your site is private. Only team members, assigned mentors, and programme leadership can access your Solution Site. It is not visible to other teams or to the general public.
Deliverables and Work Packages
The work your team does on GAITS is structured into Deliverables — the specific outputs, analyses, or decisions your project needs to produce at each stage of the Healthcare Innovation Cycle. Deliverables are grouped into Work Packages (WPs) — defined collections of Deliverables that organise related work into coherent units. A Work Package can draw on Deliverables from any dimension, and is designed to bring together work that logically belongs together at a given point in your project's development.
How Deliverables are assigned
When programme leadership creates your Solution Site, they assign a solution type. GAITS uses this to configure your site with the Deliverable set for that type. Many Deliverables are shared across solution types — for example, completing a stakeholder interview plan is relevant for MedTech, Digital Health, and Therapeutics — while others are specific to your type's regulatory, clinical, or commercial requirements.
You do not choose or configure your Deliverables. They are pre-set based on your solution type and the current stage of your project. If your Site Admin has added custom Deliverables, these will appear alongside the standard set.
Working with a Deliverable
Each Deliverable has a status that your team updates as work progresses. As you complete the work, you record the outcome against the Deliverable — this is how your team's progress is tracked and made visible to your mentor and programme leadership.
Members (and Site Admins) can update Deliverable status and add content. Viewers can read Deliverables but cannot make changes.
Recording pivots
GAITS is built on the understanding that healthcare innovation teams pivot — discovery interviews reveal unexpected needs, market assumptions prove incorrect, or the regulatory pathway changes. When your team makes a significant change in direction, you can record this as a pivot against the relevant Deliverable or stage. Pivots are part of the project record and are visible to your mentor and programme leadership.
Innovation Maturity Levels
The 10 Innovation Maturity Levels (IMLs) define where a healthcare innovation sits in its journey from unmet need to standard of care. They were developed from CIMIT's 20+ years of experience supporting healthcare innovators and are the foundation on which the entire GAITS platform is built.
Progress through the IMLs is tracked independently across the four dimensions of the Healthcare Innovation Cycle:
- Clinical — evidence of unmet need, clinical validation, and safety
- Regulatory — understanding the regulatory pathway and meeting its requirements
- Commercial — stakeholder discovery, business model development, and market validation
- Technical — solution development and technical feasibility
This means your project can be at different maturity levels across different dimensions at the same time — which is normal and expected. Regulatory work often lags technical development early on; commercial validation frequently precedes clinical evidence in certain solution types. Your site displays your maturity level across all four dimensions so that you, your mentor, and programme leadership can see the full picture at a glance.
IMLs are not a rigid checklist. They are a framework for understanding where you are and what work is most critical at each stage — not a lock-step process that must be completed in sequence. The Deliverable set for your stage guides the work; the IML level reflects the maturity you have demonstrated.
To explore the full IML framework and understand what each level means for your solution type, visit the Healthcare Innovation Cycle section of the GAITS site.
The GAITS frameworks
The four GAITS frameworks are the intellectual core of the platform. They are available to all registered users and can be accessed at any time from the navigation bar at the top of the page. You do not need to be on your Solution Site to use them.
Understanding the frameworks is what makes the Deliverables meaningful. Each framework addresses a specific challenge that every healthcare innovation team faces as they advance, and the Deliverables in your Solution Site are built around these frameworks.
These frameworks are not sequential in the sense that you finish one before starting the next. Stakeholder discovery (VERITAS) should begin early and continue throughout. Business model work (H-BMC) draws on discovery insights and matures alongside clinical evidence. Funding readiness criteria are useful to understand from the beginning, even if you are not yet raising capital.
Working with your mentor
If programme leadership has assigned a mentor to your team, they will appear in your Solution Site. Mentors are typically experienced healthcare innovators, clinicians, or commercial specialists assigned to support your team's progress.
How your mentor works with you
Your mentor's role is active and collaborative — they work alongside your team, not just observe from a distance. When you first start working together, your mentor will review your site with you, helping your team calibrate your self-assessment and build an accurate picture of where the project actually stands. From there, you will work together to identify the most important gaps and build a plan using Work Packages. Your ongoing collaboration is then structured around those active Work Packages — reviewing progress, addressing blockers, and keeping the work moving.
What your mentor can see
Your mentor has full Site Admin access to your Solution Site — they can see your project dashboard, your Deliverables, your progress across the IMLs, and any pivots you have recorded. This means the work you do in your site is your primary means of communicating progress between mentor meetings.
The mentor workspace
In addition to access to your site, your mentor has a private workspace shared with programme leadership. This space is not visible to your team. It is where your mentor and programme leadership record their observations, discuss your project's progress, and coordinate feedback and support behind the scenes.
You will not see what is written in the mentor workspace, but it directly informs the guidance and support your mentor brings to your interactions. Keeping your Deliverables up to date is the best way to ensure your mentor and programme leadership have an accurate picture of where your project is.
Keep your site current. Your mentor reviews your project based on what is recorded in your Solution Site. A Deliverable that is complete in practice but not updated in the site looks the same as one that has not been started. Regular updates to your site make mentor interactions more useful and efficient.
Site Admin tasks
If you have Site Admin access, you have control over who can access your site and how it is configured. Site Admin responsibilities typically belong to the project lead or a designated team member who manages the project's GAITS presence.
The tasks in this section are only available to users with Site Admin access. If you need Site Admin access, contact your current Site Admin or programme leadership.
Inviting team members
You can invite new members to your Solution Site at any time. When you send an invitation, you set the access level for that person — Member (read/write) or Viewer (read-only). Choose the access level that matches what the person needs to do on the site.
A few things to keep in mind when inviting members:
- Viewers are appropriate for advisors, external reviewers, or stakeholders who need visibility into the project without making changes.
- Members should be active contributors who will update Deliverables and engage with the platform regularly.
- You can change a member's access level or remove them from the site at any time.
- Mentors are assigned by programme leadership, not by Site Admins. You cannot add a mentor directly.
Adding custom Deliverables
The Deliverable set for your site is based on your solution type and was configured by programme leadership. As a Site Admin, you can add custom Deliverables to the site if there is specific work your team needs to track that is not covered by the standard set.
Custom Deliverables behave the same as standard Deliverables — they can be assigned to a Work Package and stage, given a status, and updated by any team Member or Site Admin. They are visible to your mentor and programme leadership in the same way standard Deliverables are.
Managing site settings
Site settings allow you to update basic information about your project — including the project name, description, and contact details displayed on the site. These settings are visible to your mentor and programme leadership and help them keep track of your project in the context of the wider portfolio.
If you need to change your solution type, contact programme leadership — this is a portfolio-level setting that affects your Deliverable set and cannot be changed from within the site itself.