BDQ

Asana - Work Management Software

Asana Work Management is a cloud-based platform that helps teams plan, track and deliver work. It provides task management, project planning, workflow automation, reporting and collaboration tools, improving visibility, accountability and delivery across departments and suppliers, with role-based access and integrations to support secure, efficient operations.

Features

• Task and project management with owners, due dates and priorities.
• AI-powered summaries, status updates and work insights in Asana.
• Workflow automation, templates and rules to standardise delivery.
• Real-time dashboards and reporting for progress, risks and workload.
• Integrations with Microsoft 365, Google Workspace and other tools.

Benefits

• Improved visibility and accountability across teams and stakeholders.
• Faster delivery through automation and AI-assisted updates.
• Better collaboration with clear priorities, ownership and shared context.
• Reduced risk through tracking, reporting and predictive insights.
• Consistent ways of working across programmes, departments and suppliers.

• Education pricing available
• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at enquiries@bdq.cloud. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

858093177716295

Contact

Dominic Bush
+44 (0)844 8265 236
enquiries@bdq.cloud

About the service

• Service categories:
  • Applications
    • Collaborative
      • Team collaboration
        • Team collaboration
• Multi cloud support: Yes

Service scope

• Software add-on or extension: No
• Cloud deployment model: Public cloud
• Service constraints: Asana is a cloud only SaaS solution. An on-premise deployment is not possible.
• System requirements:
  • The latest version of Chrome, Safari, Firefox or Edge browser
  • An email address is required

User support

• Email or online ticketing support: Yes
• Support response times: For Asana Enterprise plan customers, Asana provides 24/7 English support and will respond to Customer support inquiries filed via https://asana.com/support within two (2) business hours of receipt of such inquiry (excluding US, Ireland, and Australia holidays). Please see https://asana.com/service-levels for full details.
• User can manage status and priority of support tickets: No
• Phone support: No
• Web chat support: No
• Onsite support: No
• Support levels: For Asana Enterprise plan customers, we provide L1 (How to) through L4 (System Outage) support. Additionally Forum, Academy, Webinars, Guides and Developer resources are available. Customer Success may also be provided to Enterprise plan customers based on the size of deployment.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Asana is designed to be used with minimal training and support. Self guided Forums, Academy, Webinars, Guides and Developer resources are available to all users. Customer Success may also be provided to Enterprise plan customers based on the size of deployment. For organisations that require additional support, there is an optional onboarding package, where an organisation can opt to purchase additional support in the form of consultation and training.
• Service documentation: Yes
• Documentation formats: HTML
• Documentation accessibility standard: None or don’t know
• How the documentation is accessible: Onboarding and offboarding documentation is centrally maintained in an internal knowledge repository and serves as the single source of truth for required procedures, role-based checklists, and operational standards. Access is provided to relevant teams (e.g., HR, IT, Security, and managers) using role-based permissions to ensure appropriate visibility and control.; ; The documentation is also linked directly within our Asana Work Management onboarding and offboarding templates. Key references are embedded at the project level and within individual tasks/subtasks so users can easily access instructions at the point of execution. This ensures consistent process execution and reduces reliance on informal knowledge.; ; Process owners are responsible for keeping documentation current, and updates are reflected in both the repository and the corresponding Asana templates to maintain alignment over time.
• End-of-contract data extraction: Asana will make Customer Data available to Customer for export in accordance with the Documentation as long as Asana receives written notice within thirty (30) days after the effective date of expiration or termination from Customer regarding its intent to import such Customer Data. After such thirty (30) day period, Asana will have no obligation to retain Customer Data and will thereafter, unless legally prohibited, be entitled to delete all Customer Data in its systems or otherwise in its possession or under its control. Subject to any limitations in Customer’s Subscription plan, upon Customer’s request at datadeletions@asana.com, Asana will, within one-hundred and eighty (180) days of receipt of such request, securely destroy all Customer Data from its systems; provided that all back-ups will be deleted within thirty (30) days after such one-hundred and eighty (180) day period.
• End-of-contract process: Asana may immediately deactivate Customer’s account(s) associated with the Agreement. All Subscriptions and any other rights granted will immediately terminate, and Buyer shall immediately cease all use of the Service.; ; For the process related to data extraction at the end of the contract, please see our previous answer.

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
• Application to install: No
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: Most features are available on both platforms. Where there is imparity between the desktop and mobile service, we will aim to develop parity.
• Service interface: No
• User support accessibility: None or don’t know
• API: Yes
• What users can and can't do using the API: The Asana API is a RESTful interface, providing programmatic access to much of the data in the system. It provides predictable URLs for accessing resources, and uses built-in HTTP features to receive commands and return responses. This makes it easy to communicate from a wide variety of environments: command-line utilities, gadgets, and even the browser URL bar itself.; ; The API accepts JSON or form-encoded content in requests and returns JSON content in all of its responses, including errors. Only the UTF-8 character encoding is supported for both requests and responses.; ; Please see https://developers.asana.com/ for documentation regarding Asana's API.
• API documentation: Yes
• API documentation formats: HTML
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Many different fields, views and workflows can be built around the same underlying units of work, allowing every individual to customize their experience in Asana in a way that best suits them.

Scaling

• Independence of resources: The production infrastructure is secured so that only the load balancer machines are allowed to receive external web traffic. Each host is assigned a role; security groups are used to define the expected traffic between these roles. This makes Asana secure and scalable.

Analytics

• Service usage metrics: Yes
• Metrics types: The Asana Admin Insights dashboard provides details on who is using Asana, how many Teams, Projects and Tasks are in Asana. The Insights dashboard also shows the most active and influentials users in the platform. User reporting is also available within the Asana console to all users. This includes Status updates and Project reporting.
• Reporting types: Real-time dashboards
• Resource tagging: No
• FOCUS resource tagging: No

Supplier type

• Supplier type: Reseller providing extra support
• Organisation whose services are being resold: Asana

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: None

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations: Other locations
• User control over data storage and processing locations: Yes
• Datacentre security standards: Managed by a third party
• Penetration testing frequency: At least once a year
• Penetration testing approach: Another external penetration testing organisation
• Protecting data at rest:
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
• Data sanitisation process: Yes
• Data sanitisation type:
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Explicit overwriting of storage before reallocation / Secure Erase
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

• Data export approach: Individual projects can be exported via CSV, JSON and Calendar integrations. The APIs are also available to perform regular/ bulk exports.
• Data export formats: CSV
• Data import formats: CSV

Data-in-transit protection

• Data protection between buyer and supplier networks: TLS (version 1.2 or above)
• Data protection within supplier network: TLS (version 1.2 or above)

Availability and resilience

• Guaranteed availability: Asana provides transparency into real-time and historical uptime status at our publicly facing platform status page. For Enterprise plan customers, Asana commits to a 99.9% service uptime.
• Approach to resilience: Asana has a formal business continuity plan for extended service outages caused by unforeseen or unavoidable disasters in an effort to restore services to the widest extent possible in a reasonable time frame. Asana has a documented set of disaster recovery policies and procedures to enable the recovery or continuation of vital technology infrastructure and systems following a disaster.; ; Asana’s primary data centers are hosted on AWS in Virginia, USA. Eligible customers (Enterprise tier) may request to have their data stored in Frankfurt, Germany; Sydney, Australia; or Tokyo, Japan. In the event of a single AWS data center loss, recovery procedures would bring up nodes in another data center. To account for major disasters, a disaster recovery (DR) site is hosted in an AWS data center in Ohio, USA (for USA-based data); Dublin, Ireland (for EU and Australia-based data); or Osaka, Japan (For Japan-based data).
• Outage reporting: Customers can view and subscribe to system status updates at status.asana.com, which shares our web app, mobile app, and API availability over the previous 12 hours, 7 days, 30 days, and year.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
• Access restrictions in management interfaces and support channels: Asana treats all customer data as confidential, regardless of classification. Access to applications, operating systems, databases, and network devices is provisioned according to the principle of least privilege. This policy restricts access to confidential information to those employees who are required to access such confidential information as a part of their job, and then only in those circumstances where access to such confidential information is required to provide a specific service to the customer. In such circumstances, the employee is directed to access only the minimum amount of confidential information necessary to perform the task at hand.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)

Audit information for users

• Access to user activity audit information: Users have access to real-time audit information
• How long user audit data is stored for: At least 12 months
• Access to supplier activity audit information: No audit information available
• How long system logs are stored for: At least 12 months

Security governance

• Named board-level person responsible for service security: Yes
• Software Security Code of Practice: Yes
• Security governance certified: Yes
• Security governance standards:
  • ISO/IEC 27001
  • Other
• Other security governance standards: SOC 2 Type II;; ISO 27017; ISO 27018; ISO 27701
• Information security policies and processes: Asana maintains a formal information security management program with dedicated security personnel reporting to Asana's Head of Security. This organization is responsible for implementing security controls and monitoring Asana for malicious activity.; ; Our information security management program also includes a cybersecurity risk management process which aims to identify and assess material risks from cybersecurity threats, including from vulnerabilities within Asana systems and new and emerging threats to Company operations by using automated and manual tools, subscribing to and analyzing reports and services that identify certain cybersecurity threats, conducting scans of certain environments, evaluating our and our industry’s risk profile, evaluating threats reported to us, and conducting audits and threat assessments.; ; For additional details on Asana's Security program, please visit security.asana.com.

Operational security

• Configuration and change management standard: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Configuration and change management approach: Changes made to systems follow Asana's Change Management Policy, where changes to our application, systems, databases, infrastructure, and services are appropriately documented, tested, and approved in accordance with our internal guidelines.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Asana maintains a vulnerability scanning process for production systems. The scope of vulnerability scans includes both external and internal systems in the production environment. Vulnerability priority is appropriately assigned based upon a number of factors, such as Risk and Asana-specific environmental controls. Risk is informed by industry standards such as the Common Vulnerability Scoring System (CVSS).; ; Asana’s Security team performs vulnerability scans at least quarterly and determines a severity rating for each vulnerability based on the assessment tools criteria such that high or higher-level ranked vulnerabilities require remediation.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: Asana uses Amazon Cloudwatch combined with custom scripts that extract important data from logs and push them to its monitoring services. Asana monitors the capacity utilization of physical and computing infrastructure both internally and for customers to ensure service delivery matches service level agreements. We have automated security scans on our network and applications. A monitoring script runs weekly to validate code changes were properly reviewed. The results of monitoring issues are tracked to resolution.
• Incident management type: Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
• Post-quantum cryptography secure: No
• Incident management approach: Asana maintains an Incident Response Plan designed to establish a reasonable and consistent response to security incidents and suspected security incidents involving the accidental or unlawful destruction, loss, theft, alteration, unauthorized disclosure of, or access to, proprietary data or personal data transmitted, stored, or otherwise processed by Asana. These incident response procedures detail how Asana triages, investigates, remediates, and reports on security incidents. Asana has contracted with third party digital forensics and incident response firms in the case of a data breach.

Secure development

• Approach to secure software development best practice: Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: A free trial is available for Asana Starter or Advanced for up to 60 days. The trial period includes all features listed per paid product.
• Link to free trial: https://asana.com/create-account

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 0%
• Between £250,000 and £500,000: 0%
• Between £500,001 and £1,000,000: 0%
• Between £1,000,001 and £2,500,000: 0%
• Between £2,500,001 and £5,000,000: 0%
• Over £5,000,001: 0%

Standards and certifications

• ISO/IEC 27001 certification: No
• ISO 28000:2022 certification: No
• ISO 9001 certification: No
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Cyber Essentials Certificate Number: Provided
• Cyber essentials plus: No
• Cyber Essentials Alternative: None of the criteria
• Other security certifications: No

Social value

• Mission: Kick start economic growth:

  To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

  Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority

  • New or retained jobs on the contract workforce in the relevant area that meet the criteria set out in MAC 1b, 1c and 1d
  • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
  • Plans to engage the contract workforce in deciding the most important workplace issues to address
  • Ensuring new workers are informed of their right to join a trade union
  • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
  • Employment contracts that reflect actual hours worked; steps taken to ensure employees understand their contracts and have the ability to review and adjust them if actual hours regularly exceed contracted hours
  • Activities that support an environment where staff are educated about, and feel empowered to, address their physical wellbeing
  • Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
  • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
  • Entitlement to sick pay for the contract workforce, with provision in place for any staff who do not meet the earnings threshold for statutory sick pay, payment of sick pay from day one of absence and payment of staff on the contract workforce who are off sick a replacement income of 100% of their usual earnings for as long as possible
  • Understanding of in-work progression issues affecting the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
  • Measures to support in-work progression to help people in the contract workforce, to move into higher paid work by developing new skills relevant to the contract
  • Support for the contract workforce by providing career advice, and providing opportunities for staff working on the contract with in-work progression career development into known skills shortages or high growth areas
  • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
  • Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors
  • Measures to identify, mitigate and manage modern slavery risks relating to the contract and how these will be implemented
  • Outline policies and practices to be applied to or put in place for the contract to mitigate and manage modern slavery risks, including: Pre-employment checks, recruitment practices. Workplace conditions, safeguarding plans and processes in place and regular monitoring with relevant groups considered, which may include sampling
  • How these flow down the supply chain and are monitored Illustrative examples include reporting, site visits, audits, etc.
  • How to ensure business decisions re: price/cost, short lead times, payment timescales do not create modern slavery risks in the supply chain

  Policy Outcome 2: Skills for growth: Supporting growth sectors and addressing skills gaps.

  • Understanding of employment and relevant skills issues, and of the education and training issues relating to the contract. Illustrative examples: demographics, skills shortages, new opportunities in high growth sectors, geographic/local community and skills/employment challenges
  • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications

  Policy Outcome 3: Resilient, innovative and flexible supply chains: Support economic growth through enabling resilient businesses, opportunities for small businesses and voluntary, community and social enterprises

  • Understanding of the types of businesses in the market and the level of participation by new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
• Mission: Make Britain a clean energy superpower:

  To cut bills, create jobs and deliver security with cheaper, zero-carbon electricity by 2030, accelerating to net zero

  Policy Outcome 4: Sustainable procurement practices: Reducing carbon footprints, minimising waste, and promoting the use of clean energy and green technologies.

  • Understanding of opportunities for additional environmental benefits delivery in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
  • Delivery of additional environmental benefits through the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
  • Understanding of how to influence staff, suppliers, customers, communities and/or any other appropriate stakeholders through the delivery of the contract to support climate and nature protection and improvement
• Mission: Break down barriers to opportunity:

  By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

  Policy Outcome 6: Employment and training: For those who face barriers to employment

  • Understanding of employment and skills issues, and of the skills and employment shortages of high growth sectors relating to the contract
  • Understanding of the issues affecting the representation of disabled people in the workforce in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
  • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
  • Working conditions which promote an inclusive working environment and promote retention and progression
  • Understanding of the issues affecting inequality in employment, skills and pay in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors. Measures to tackle inequality in employment, skills and pay in the contract workforce
  • Inclusive and accessible development practices, including guidance for line managers on recruiting, managing and developing people with a disability or health condition
• Mission: Build an NHS fit for the future:

  That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.

  Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.

  • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
  • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at enquiries@bdq.cloud. Tell them what format you need. It will help if you say what assistive technology you use.