• People

    Core Literacy, Experience and Culture

    Corporate boards have moved away from an emphasis on stakeholder representation to skills based composition. Project boards should also look past stakeholder representation to consider the skills and capabilities that members contribute. Board members should include external members, and be chosen for their authority, expertise, experience, status and connection (11),  focusing on people who:

    • are authorised to represent the interests of the area they represent;
    • can provide necessary resources; and
    • are committed to the project outcomes.

    Project boards rarely have the time or luxury to be able to develop complete knowledge of all aspects of any project. Some literacies can readily be taught, helping board members know what to look for and the questions to ask. Project board training can help rapidly develop core literacies.

    Other board member capabilities are developed through years of experience. We differentiate between SROs’ and board members’ digital project, (Table 4) the collective experience the board should contain, (Table 5) and the culture, attitude and behaviours that needs to be established for a digital project board to be effective.

    Core Literacy capabilities

    Foundational literacy all project board members should have:

    Benefits and outcomes

    Understanding of benefits management processes, and the relationship between outputs and outcomes, benefits and value

    Communication in the context of change

    Understanding the importance of a project narrative, creating a culture of
    transparency, stakeholder identification, constructive conflict and feedback loops

    Project management foundations

    Understanding of key project management concepts, giving the board the ability to question aspects of the project lifecycle, critical path, earned value, burn rate and baseline

    Core Experience skills

    The expertise needed on the Board should be guided by key areas of risk, both enterprise and project delivery.

    Common expertise requirements for Digital Project Boards:

    Business expertise

    Understanding of the business, impacts and change required for end users, allowing the board to maintain sight of the business logic of the project

    Operations expertise

    Understanding of the operational environment to ensure the solution is integrated,
    maintainable and sustainable within the existing IT applications portfolio

    Digital project management expertise

    Understanding of digital projects, their lifecycle, risks, ideally with experience in a similar type of project (e.g. AI, Software as a Service (SaaS), risk tier)

    Interpersonal skills and social capital

    Strong networks and relationships that support negotiation, decision-making, issue resolution, stakeholder management, effective communication and resourcing5,

    Digital, data and cyber expertise

    Depending on the project type and stage, deep technical expertise may be required

    Legal and policy

    Depending on the project type and stage, regulatory and policy expertise may be required

    Procurement and contract management

    Depending on the project type and stage, expertise in procurement and contract management may be necessary

    Independence

    Balancing the need for vested interests, ensuring there is someone who can view the project and its progress objectively and independently

    Supplier expertise

    Depending on the project, experience and knowledge of the product, implementation approach and supply chain

    Interdependencies

    Knowledge of areas the project has interdependencies with, for example, resourcing, systems integration

    Employee/customer experience

    Expertise in ensuring a solution is well suited to the needs of the users of project deliverables

    Change management expertise

    Experts in communicating and designing organisational change, reducing resistance and increasing uptake of change

    Financial expertise

    Depending on the complexity, size, risk and procurement strategy of the project

    Culture, Attitude and Behaviours

    Attitudes and behaviours required on project boards:

    Skin in the game

    Members should have a genuine interest, commitment and ownership of the project’s success28

    Psychological safety

    Boards need to foster a no-blame environment where people feel safe with constructive conflict, raising ideas and escalating issues (23, 41)

    “Can do” agency

    Board membership is not a passive role. Members should take action to ensure they have the right information to support decisions and proactively identify strategies that enhance project success (23)

    Time commitment

    Board members often underestimate the time involved. Members must ensure they are suitably informed, attending meetings and prepared to support decision-making(11, 23, 42)

    Courage

    Courage to stop a project, escalate risks or reset the project if the project does not have sufficient business justification and/or delivery confidence is low (1, 25) 

    Attendance

    Continuity in core board membership facilitates historically informed decision-making. Use of deputies or proxies should be avoided as it signals a lack of commitment, dilutes accountability and can delay decision-making (11).
    Members should not attend just to report to others (28).

    Decision expediency

    Boards need to make decisions escalated to them in a timely manner, possibly despite incomplete information. Decisions should be clear and prioritise action (23, 43).

    Value-focused

    Boards should suspend self-interest and operate from a position of what is best for the organisation and project, optimising value from the project investment

    Empowering

    The project board can make the decisions it needs to so that the project is empowered to deliver

    Humility

    Openness to learning and adaptation – seeking robust advice from independent advisors and project assurance, seeking out lessons learned from similar projects, listening to user and reference groups, acting on recommendations (1, 44).

  • “State Penalties Enforcement Registry (SPER) conducted at least 20 reviews (gateway reviews, program health checks and various other reviews)… SPER did not address warning signs raised through some of these reviews—including concerns with the lack of an operating model, the vendor’s product, and SPER’s relationship with the vendor”(3).

    Audit office inquiry
  • "Everyone has a stake but no one wants to be responsible"

    Interviewed Governance Professional, DTA
  • Motivation acts as a driving force for users to overcome digital barriers, such as a lack of skills and confidence. When users engage digitally, make sure their experience is as easy and enjoyable as possible to keep them engaged.

  • Overview

    1. The Digital Seller Underperformance Policy (Policy) supports the Australian Government and digital Sellers to jointly improve outcomes on Strategic Digital Contracts.
    2. This Policy is intended to encourage strong contract performance by Sellers, and to identify and record instances of serious underperformance from Sellers. This will support proper use of the Government's investment of public funds in digital projects. This Policy applies to 'Strategic Digital Contracts' which are defined as:
      1. contracts to procure digital products and services valued at $4 million (whole-of-life contract value and GST exclusive) or more (Threshold); or
      2. other contracts determined by the DTA to be Strategic Digital Contracts. This may be in contracts valued below the Threshold but are considered by the DTA to be strategically significant in the delivery of digital products and services to or on behalf of the Australian Government.
    3. The DTA has whole-of-Government responsibility for managing strategic coordination and oversight functions for digital projects, including during the planning and delivery phases.
    4. Digital projects are those that use digital products and services as the primary lever for achieving outcomes and benefits to:
      1. transform the way people and businesses interact with the Australian Government; and
      2. improve the efficiency and effectiveness of Australian Government operations, including through automation.
    5. The DTA will apply this Policy to:
      1. make decisions about whether a Seller's performance is an instance of a 'serious underperformance' under a Strategic Digital Contract and record the underperformance of Strategic Digital Contracts: and
      2. provide information on these contracts to Australian Government agencies making digital procurements (Agencies), to assist them with making informed procurement decisions.
    6. Under this Policy the DTA will only identify and record instances of 'serious underperformance', which means:

      1. instances of significant deficiencies in performance of any substantive requirement or obligation of a Seller under a Strategic Digital Contract;
      2. Sellers that are subject to bankruptcy or insolvency; or
      3. Sellers who have made false declarations.

      This approach is consistent with the Commonwealth Procurement Rules, including Rules 4.5 and 10.17.

    7. Where the DTA verifies serious underperformance by a Seller, this information will be held by the DTA and made accessible to Australian Government Agencies to inform their procurement processes.

    Purpose

    1. The purpose of this Policy is to drive performance improvement on a whole-of-Government basis, by creating stronger incentives for Australian Government Buyers and digital Sellers to resolve underperformance and jointly improve digital project performance.
    2. This Policy will also assist the DTA to give Ministers and stakeholders confidence that digital projects (supported by Strategic Digital Contracts) are being designed well and are optimised to deliver value for the Australian Government, by achieving their project objectives.
    3. This Policy will be periodically reviewed and updated by the DTA to adapt to changing market conditions, technological advancements, and feedback or consultation with Buyers, Sellers and other relevant stakeholders. Reviews will consider the effect of the Policy on Buyers and Sellers.

    Application of Policy

    1. Under this Policy, Sellers with Strategic Digital Contracts (Sellers) may be recorded as having 'confirmed serious underperformance' status in circumstances of verified serious underperformance.
    2. Commonwealth buyers of Strategic Digital Contracts (Buyers) will be able to report information to the DTA if the Buyer considers a Seller has demonstrated serious underperformance. This includes Buyers that are:
      1. Non-corporate Commonwealth entities; and
      2. Corporate Commonwealth entities for the purpose of the Public Governance, Performance and Accountability Act 2013 (Cth)
    3. This Policy applies to Strategic Digital Contracts entered into from the commencement date of the Policy.
    4. The DTA will first review Buyer reports of serious underperformance. The DTA will then engage with the Buyer to seek further information on the reported serious underperformance. The DTA will also invite Sellers to provide information on the reported serious underperformance. Details of this process are set out further below.
    5. If, after engaging with both the Buyer and Seller, the DTA is satisfied that the information provided supports an assessment that the Seller has seriously underperformed a Strategic Digital Contract, it will record the Seller on its Confirmed Serious Underperformance (CSU) Register as having 'confirmed serious underperformance' status.
    6. The DTA will make information on Sellers that have 'confirmed serious underperformance' status available to Australian Government Agencies procuring digital products and services during the tender evaluation process. Agencies will need to provide evidence of their procurement process and will be able to:
      1. access information held by the DTA about a Seller's serious underperformance; and
      2. use this information in accordance with procurement policy when assessing the Seller's performance history for relevant digital procurement(s). As a Seller's status on the CSU Register can change over time, information obtained from the DTA under paragraph 16.a of this Policy should only be used by Agencies to assess current digital procurements.
    7. The DTA's Digital Marketplace Panel 2 (DMP2) also has a Performance Management Framework (PMF), which operates separately to this Policy. The PMF only applies to all digital procurements from the DMP2. However, this Policy only applies to Strategic Digital Contracts as defined above (including but not limited to any contracts entered under DTA panels, such as the DMP 2, that meet the Threshold). The DTA will ensure alignment between this Policy and the PMF as required.
    8. The DTA will document its process and governance guidance to ensure Sellers are treated fairly and that the principles of probity are applied when:
      1. assessing and making determinations on reports of serious underperformance; and
      2. using serious underperformance information within the Australian Goverment.
    9. Buyers remain fully responsible for their own procurement and contract management. This includes instances of underperformance, regardless of the value of the contract. This policy also does not limit the Buyer's rights under its Strategic Digital Contract with an impacted Seller.

    Feedback that can be included in the CSU Register

    1. Buyers should confirm all the facts and circumstances to support their report(s) of a Seller's serious underperformance issues with a Seller. Before reporting serious underperformance to the DTA, Buyers should first attempt to address serious underperformance issues with the Seller, in accordance with the contractual mechanisms for managing performance that apply to the project. Buyers should also obtain legal advice to assist with managing serious underperformance, as required.
    2. After raising the serious underperformance issues with the Seller, Buyers can provide information to the DTA (even if the matter was resolved) relating to one or more of the following types of serious underperformance:
      1. failure to meet contractual requirements;
      2. failure to meet contracted schedule;
      3. failure to deliver within the contracted budget;
      4. failure to meet agreed performance standards;
      5. failure to invoice correctly (e.g., in accordance with agreed pricing or billing incorrect number of hours);
      6. failure to provide properly qualified and experienced personnel or the required number of personnel;
      7. failure to meet security obligations;
      8. failure to comply with the Commonwealth Supplier Code of Conduct1;
      9. failure to comply with a Procurement Connected Policy2;
      10. failure to satisfactorily resolve contract performance issues;
      11. aggregated failures under more than one Strategic Digital Contract. Instances of underperformance across several Contracts may be reported by Buyers. This could be where the aggregate value of the Contracts is $4 million or more, or where the DTA determines that the contracts, taken together, are Strategic Digital Contracts;
      12. aggregated incidents of minor underperformance by the same Seller across multiple agencies as reported to the DTA;
      13. bankruptcy or insolvency of the Seller;
      14. making of false declarations by a Seller; or
      15. where a matter affecting a Seller is a 'Significant Event'3.
    3. When the DTA receives a serious underperformance report, the DTA will contact the Buyer within 10 business days to discuss the report. If needed the DTA will request further information from the Buyer to support the report.
    4. Matters that are currently subject to formal investigation by Buyers or other authorities, such as allegations of fraud or serious misconduct, cannot be reported under this Policy. These matters may be notified to the DTA through a separate process, if adverse findings are made against the Seller following the completion of such investigations. This includes circumstances where legal proceedings are initiated in relation to the conduct.
    5. Division 137.1 of the Criminal Code makes it a serious offence to knowingly provide false or misleading information to a Commonwealth entity.

    Seller's right to respond

    1. Following discussion with the Buyer to obtain further information on the report of serious underperformance, the DTA will contact the Seller and provide the Seller with details of the report. The Buyer should have already engaged with the Seller on the reported serious underperformance issues.
    2. The Seller will have 15 business days to respond to the DTA.
    3. If:

      1. no response is received from the Seller; or
      2. an unsatisfactory response is received from the Seller, which fails to meaningfully engage with the report of serious underperformance,

      the Seller will be included in the CSU Register as having 'confirmed serious underperformance' status.

    4. The DTA may allow a Seller to respond in more than 15 business days, if the Seller satisfies the DTA that there are circumstances that justify an extension of time.
    5. If the Seller disagrees with the report, the Seller must provide further information to the DTA to support its position (including evidence of remediation of the issues identified in the report). The DTA will discuss this with the Buyer and provide the Buyer with an opportunity to review its report considering the Seller's response. Following this, the DTA will decide whether to include the Seller in the CSU Register as having 'confirmed serious underperformance' status.
    6. The DTA will act fairly and impartially in determining whether a report is properly substantiated, so as to record a Seller as having 'confirmed serious underperformance' status. The final decision to record a Seller as having 'confirmed serious underperformance' in the CSU Register will be made by the Deputy CEO of the DTA.
    7. The DTA will also take into consideration receipt of more than one serious underperformance report from different Buyers in relation to a Seller, when determining whether to record a Seller as having 'confirmed serious underperformance' status. This includes previous reports where the DTA did not determine at that time that the Seller's conduct was 'serious underperformance' for the purpose of this Policy.

    How feedback can be used

    1. When a Seller is included in the CSU Register as having 'confirmed serious underperformance' status, Australian Government Agencies will be able to access this information from the DTA when they conduct a digital procurement for a Strategic Digital Contract (during the tender evaluation process). Agencies will need to provide evidence of their procurement process (i.e., confirmation that a Seller has submitted a response to a request for digital procurement) before gaining access to a Seller's status and underperformance information under this Policy.
    2. During the tender evaluation process, this will enable Agencies to consider information about the Seller's serious underperformance as part of the Seller's performance history, including when assessing value for money and risk of relevant tenders from the Seller.
    3. This Policy does not prohibit Agencies from engaging Sellers on the CSU Register – a Buyer may choose to engage a Seller on the register.
    4. Buyers procuring new Strategic Digital Contracts must consult with the DTA about a Seller's underperformance history.
    5. The Commonwealth Procurement Rules (CPRs) paragraph 4.5 state:

      Price is not the sole factor when assessing value for money. When conducting a procurement, an official must consider the relevant financial and non-financial costs and benefits of each submission including, but not limited to the:

      […]

      c. potential supplier's relevant experience and performance history.

    6. Further, CPR paragraph 10.17 states:

      A relevant entity may exclude a tenderer on grounds such as bankruptcy, insolvency, false declarations, or significant deficiencies in performance of any substantive requirement or obligation under a prior contract.

    7. As a consequence, Agencies conducting a new digital procurement may take into account that a Seller has 'confirmed serious underperformance' status for a Strategic Digital Contract under this Policy in accordance with the CPRs.
    8. Agencies:
      1. should only use current and relevant information from the CSU Register to evaluate tenders;
      2. should not use information from the CSU Register as the only source of due diligence about a Seller;
      3. should consult the CSU Register before conducting a limited tender; and
      4. can and are encouraged to ask Sellers for more information after they have ascertained a Seller is recorded on the CSU Register.
    9. Sellers will retain 'confirmed serious underperformance' status on the CSU Register for a period of at least 1 year. Following that time a Seller may provide evidence to the DTA about steps it has taken to rectify the serious underperformance. Based on this and on consultation with Buyers who previously provided a Serious Underperformance Report for the Seller, the DTA will decide whether the Seller's 'confirmed serious underperformance' status should be removed.
    10. A Seller's serious underperformance history will remain on the CSU Register for 5 years (including the dates that the Seller's 'confirmed serious underperformance' was recorded in and/or removed from the CSU Register).
    11. The DTA has prepared template clauses (see below) and strongly encourages Agencies to include these in all digital approaches to market and any contracts valued at or over the Threshold, regarding the DTA's collection and use of information from serious underperformance reports (if any).

    Approach to market and contract clauses


     

    1. The DTA has prepared template clauses for:

      1. approaches to market; and
      2. contracts,

      that Agencies are strongly encouraged to include in their procurement documentation to make it clear to Sellers that Agencies can:

      1. take into consideration the Seller's performance history including any information held by the DTA in its CSU Register; and
      2. if the resulting contract is a Strategic Digital Contract, provide any serious underperformance information to the DTA.
    2. Buyers must not agree to terms or conditions in their contracts that may:
      1. prevent Buyers from sharing a Seller's serious underperformance information with the DTA and the provision of that information to other Buyers as contemplated by this Policy (for example confidentiality obligations); or
      2. otherwise restrict or limit the DTA's ability to properly administer this Policy with respect to a particular Seller.
    3. The DTA will make the template clauses available to Agencies during the next stage of Policy implementation.

    Commonwealth officials to act with integrity

    1. Commonwealth officials will act ethically, honestly, with integrity and in good faith in administering this Policy. This includes acting in accordance with the APS Values, the APS Code of Conduct and the duties under s 26 of the Public Governance, Performance and Accountability Act 2013 (Cth), and other applicable codes.
    2. Records kept under this Policy may need to be necessarily disclosed, e.g. through legal processes such as freedom of information, privacy, discovery in litigation, or inquiry, or other parliamentary, audit or oversight processes.

    Complaints

    1. Any complaints in relation to this Policy should be directed to the DTA via email (to be provided). Further details about the complaints handling process will be provided during the next stage of Policy implementation.

    Footnotes

    1. Published by the Department of Finance and available at: https://www.finance.gov.au/government/procurement/commonwealth-supplier-code-conduct-overview
    2. Published by the Department of Finance and available at: https://www.finance.gov.au/government/procurement/buying-australian-government/procurement-connected-policies
    3. 'Significant Event' means:
      1. any adverse comments or findings made by a court, commission, tribunal or other statutory or professional body regarding the conduct or performance of the Seller or its officers, employees, agents or subcontractors that impacts or could be reasonably perceived to impact on their professional capacity, capability, fitness or reputation; or
      2. any other significant matters, including the commencement of legal, regulatory or disciplinary action involving the Seller or its officers, employees, agents or subcontractors, that may adversely impact on compliance with Commonwealth policy and legislation or the Commonwealth's reputation.
  • Consultation Fact Sheet

  • The Digital Transformation Agency (DTA) is seeking feedback from digital sellers on the proposed Digital Seller Underperformance Policy (DSUP). This Policy is designed to support better outcomes from strategically significant government digital contracts by encouraging strong performance and enabling fair, transparent management of serious underperformance.

    Why this Policy matters to sellers

    We have designed the DSUP to recognise that performance challenges on digital contracts can arise from many factors.

    This Policy is not about penalising sellers. It's about:

    • Creating a fair and consistent approach to managing serious underperformance.
    • Encouraging collaboration between buyers and sellers to improve delivery outcomes.
    • Providing transparency in how performance history may be considered in future procurements.

    The DSUP will apply to Strategic Digital Contracts, valued at $4 million or more, or other contracts determined to be strategically significant by the DTA.

    What's being proposed

    The DSUP outlines a process for:

    • Reporting and assessing serious underperformance.
    • Providing sellers with a right of reply to the reporting of 'serious underperformance'.
    • Recording confirmed serious underperformance on a secure register (CSU Register).
    • Sharing relevant information with Australian Government buyers during tender evaluations.

    The CSU Register will be accessible only to authorised Australian Government buyers and will not prevent sellers from being awarded future contracts — but it will help buyers make informed decisions.

    Why your feedback is important

    Your insights will help ensure the Policy is:

    • fair and proportionate;
    • sensitive to the realities of digital delivery; and
    • supportive of sellers of all sizes and specialties.

    We want to hear from you — whether you're a sole trader, small to medium enterprise, or large seller — to help shape a Policy that works for the whole market.

    How to participate

    • Read the draft Policy
    • Submit your feedback in the 'Have your say' section of digital.gov.au
    • Consultation closes on 21 December 2025 at 4 PM (AEDT).

    Matters we'd like your feedback on

    • Are the criteria for "serious underperformance" clear and reasonable?
    • If you're a seller, is the right of reply for sellers sufficient to ensure you are able to respond to and that your perspective is taken into account by the decision maker?
    • Do you understand how your contracts may be affected by this Policy?
    • Does the Policy provide enough opportunity for sellers to improve and demonstrate remediation?
    • Do you have any views on the Policy's fairness and impartiality?
    • How would you prefer to receive updates or guidance once the Policy is finalised?
    • Is the scope of the policy clear, including which contracts will be covered and how the threshold will be applied?

    Applying the policy more broadly

    We are also interested in seller and stakeholder views on whether the seller underperformance policy should be applied more broadly to a wider range of contracts. We are interested in feedback on:

    • Which other contract types should be prioritised in extending the seller underperformance policy beyond digital contracts? This includes any you consider are high-risk or would especially benefit from the policy.
    • Do you see any barriers or issues associated with widening application of the policy to other types of contracts in future and, if so, do you have any suggestions to address these?
    • Noting the draft policy applies to all sellers, are there sellers you think should be exempt? Why?

    What happens next

    After the consultation period closes:

    1. The DTA will review all submissions: feedback from sellers and other industry stakeholders will be carefully considered for DTA's finalisation of the policy.
    2. We will publish a summary of feedback: a consultation summary will be made available outlining key themes and how they will shape the final policy.

    What the policy does

    • Applies to Australian Government digital contracts valued at $4 million or more; or other strategic digital contracts as determined by the DTA.
    • Improves transparency of digital seller performance across the Australian Government.
    • Provides incentives for buyers and sellers to work together to resolve delivery challenges and achieve successful outcomes.
    • Offers a simple, fair process for reporting potential cases of serious underperformance.
    • Ensures sellers have the right to respond and that all reports are assessed consistently, fairly, and ethically by DTA personnel with the requisite authority to make decisions. The final decision to record a seller as having 'confirmed serious misconduct' will be made by the Deputy CEO of the DTA.
    • Maintains a register of serious underperformance to inform agency decision-making during tender evaluation activities for digital contracts.
    • Protects seller and supplier privacy, with information only accessible under strict confidentiality arrangements including a 'need to know basis' only.

    What the policy does not do

    • It is not designed for minor issues, it only applies to serious underperformance (see Policy for definition).
    • It is not a procurement ban or debarment regime. Buyers make their own decisions about a seller's suitability on a case by case basis for procurements where the digital contract is valued at $4 million or more or the contract is a Strategic Digital Contract, as determined by the DTA.
    • It is not a 'blacklist'. The register is not public and does not prevent agencies from considering listed sellers for future work.
    • It is not the sole source of assessment. Buyers must still undertake their own due diligence and performance checks during evaluation.
    • It is not a dispute resolution or mediation service. Buyers remain responsible for managing contracts and engaging with sellers to resolve issues before escalating to the DTA.

    What does the DTA do?

    The DTA is the Australian Government's trusted adviser on digital transformation. This includes supporting and monitoring digital sourcing initiatives across the Australian Government, such as the Digital Marketplace Panel 2.0.

    Australian Government agencies have spent approximately $16.9 billion on digital products and services contracts across DTA marketplaces as at 31 July 2025.

    The DTA has whole-of-Government responsibility for managing strategic coordination and oversight functions for digital projects. This policy initiative is part of DTA's role...

    The DTA also has oversight of and reports on whole-of-Government digital project performance. The Major Digital Projects Report provides an annual update on the status of major digital projects and sets out how the DTA is working to create the conditions for success through ongoing reforms and improvements.

  • The Digital Transformation Agency (DTA) is seeking feedback from digital sellers on the draft Digital Seller Underperformance Policy (DSUP). This Policy is designed to support better outcomes from strategically significant government digital contracts by encouraging strong performance and enabling fair, transparent management of serious underperformance.

  • Digital Seller Underperformance Policy

    DRAFT – November 2025

  • Creating an Action Plan

    After completing the self-assessment, consider developing an action plan to address areas for improvement and build on strengths. For each action, assign a clear owner and set realistic due dates to ensure accountability. The action plan should be reviewed at regular intervals by the Board to track progress, adapt to changing needs, and maintain momentum.

    A well-structured action plan might include:

    • Clear actions: What needs to be done?
    • Owners: Who is responsible for each action?
    • Due dates: When should each action be completed?
    • Progress tracking: How will you monitor and report on progress?
    Example

    If your self-assessment highlights that decision-making is not always timely or that there's confusion about which decisions should be made by the board, the project team, or other forums, an effective action could be:

    Develop and implement a lightweight decision model that clarifies what decisions live where, who owns them, and when to escalate. Align this model to your Terms of Reference (ToR) and the organisation's governance environment.

    High-performing boards make it obvious what decisions live where, who owns them, and when to escalate. By introducing and regularly reviewing a simple decision model, you help ensure governance remains adaptive and responsive, rather than "set and forget."

    To use the self-assessment, a numerical rating is given for each row, giving an overall rating between 30 and 150.

    Self-Assessment Tool
    image displaying the print version of the self-assessment criteria table
  • Self-Assessment Maximum Scores by Category
    Maximum scores achievable for each self-assessment category
    CategoryNumber of QuestionsMaximum Score (1–5 scale)
    Project vision and purpose210
    Structure525
    Project information & communication420
    Decision-making315
    Board capability & composition420
    Project benefits & risks525
    Project culture735
    Total30150

     

    Important Reminder

    An average score over 100 usually means your board is relatively effective. However, it's important to look deeper.

    If you see consistently low scores in any group of questions, that could signal significant risks for your project. The scores aren't weighted, and some areas of the self-assessment may be more important than others depending on your project and where you are in the lifecycle.

  • Self-assessment score

    Performance Levels
    Foundational

    Self-assessment score: 30 – 59

    The board is struggling across most areas. Immediate, focused action is required to address weaknesses and build core governance capability.

    Developing

    Self-assessment score: 60 – 99

    The board is making progress, but there are still significant areas for improvement. Use this as a springboard for targeted development and capacity building.

    Established

    Self-assessment score: 100 – 119

    Overall, the board is functioning well, with most practices in place. Use scoring across key dimensions to target efforts to achieve best practice.

    Leading

    Self-assessment score: 120 – 150

    The board is a model of best practice, demonstrating high performance and a proactive approach to governance and improvement. The board also continually improves its own governance—using evidence and feedback to refine its charter, composition, cadence and reporting—rather than treating governance as 'set and forget.'

  • Criterion 2 – Motivate digital use

  • Self-assessment criteria

    Project vision and purpose
    Assessment questions for project vision and purpose
    QuestionLow (1)Med-Low (2)Med (3)Med-High (4)High (5)Area Total
    1. I am confident the project is delivering on our current strategy12345 
    2. The board is providing a clear and consistent vision of what the project is delivering and why12345 

     

    Structure
    Assessment questions for structure
    QuestionLow (1)Med-Low (2)Med (3)Med-High (4)High (5)Area Total
    3. The scope and authority of the board is clear, appropriate and effective12345 
    4. I am clear on what my roles and responsibilities are on the board12345 
    5. We have effective communication with other governance forums to remove roadblocks and optimise value12345 
    6. We have the appropriate level of authority to make decisions and empower the project team to improve the project's achievability, outcomes and benefits12345 
    7. I am empowered to make decisions on behalf of the area I represent12345 

     

    Project information and communication
    Assessment questions for project information and communication
    QuestionLow (1)Med-Low (2)Med (3)Med-High (4)High (5)Area Total
    8. I am confident in the project's status reporting and communication12345 
    9. We obtain appropriate and objective advice to inform risk-based, value-adding decision-making12345 
    10. The board actively ensures the various stakeholders who are involved or impacted by the project are appropriately informed and involved12345 
    11. The board gets appropriate and timely insights from the people who will be impacted by using or supporting the solution12345 

     

    Decision-making
    Assessment questions for decision-making
    QuestionLow (1)Med-Low (2)Med (3)Med-High (4)High (5)Area Total
    12. Our decision making is timely12345 
    13. Our decisions are based on optimising value and minimising negative impact12345 
    14. We consider the broader ecosystem in which the project exists and interacts with other organisational initiatives and priorities12345 

     

    Board capability and composition
    Assessment questions for board capability and composition
    QuestionLow (1)Med-Low (2)Med (3)Med-High (4)High (5)Area Total
    15. The SRO demonstrates the necessary knowledge, skills, and experience to effectively lead and influence the project12345 
    16. The board has the appropriate skills, experience and capability to govern this project12345 
    17. I have the skills, knowledge and experience I need to contribute to the project's governance12345 
    18. The SRO role is stable and consistently occupied by a committed and engaged individual12345 

     

    Project benefits and risks
    Assessment questions for project benefits and risks
    QuestionLow (1)Med-Low (2)Med (3)Med-High (4)High (5)Area Total
    19. Project benefits have been clearly articulated in foundational project artefacts, and we regularly review progress on realising benefits12345 
    20. We have a clear line of sight from the project deliverables to the benefits to our organisation12345 
    21. When we decide on changes, for example a reduction in scope, we consider the impact on benefits12345 
    22. I am confident the project will effectively deliver value to our organisation(s) and its stakeholders12345 
    23. I am confident that our collective work is reducing the overall risk of the project12345 

     

    Project culture
    Assessment questions for project culture
    QuestionLow (1)Med-Low (2)Med (3)Med-High (4)High (5)Area Total
    24. Members of the board are turning up and actively involved in the project's governance12345 
    25. We have a culture of constructive conflict and "no surprises"12345 
    26. My voice is heard in the project board12345 
    27. Members are suspending self-interest in the project board12345 
    28. I am suspending self-interest in the project board12345 
    29. We have the courage to stop the project or activities that are not adding value or creating unnecessary risk12345 
    30. We invite independent critique of the project to ensure we are addressing risks and maximising value12345 
    Total score 
  • Guidance for Senior Responsible Officials

  • Assurance Research Series 02

  • Appendix: Digital Project Governance Board Roles and Responsibilities

    References: 10, 12, 15, 19, 21, 23, 28, 31, 51-53

    Roles and responsibilities on digital project boards
    RoleRelationship to BoardResponsibilities
    All members and chairComprise the Board
    • Representing the interests of areas within their expertise (22)
    • Removal of roadblocks within the scope of their authority and social capital
    • Ensuring they have the information they need about project status
    • Supporting the Chair's timely and informed decision-making
    • Advising the Project Manager on contextual (for example, inter-agency) changes that may affect strategic alignment
    • Support the Project Manager with difficult decisions and resourcing

    Senior Responsible Official (SRO)

    Also known as:

    • Project/Program Sponsor
    • Senior Accountable Officer
    • Senior Responsible Owner/Officer

    To note:

    • For the largest (Tier 1) projects, the SRO is usually a Senior Executive Band 2 or Band 3 official.
    • The SRO is typically the Chair of the board.
    • For major digital projects, the SRO is accountable to the Agency Accountable Authority (for example, Secretary/CEO).
    Chair of board

    The Senior Responsible Official (SRO), is the official with ultimate accountability for a project meeting its objectives, delivering the projected outcomes and realising the required benefits within the policies set by Government. The SRO is the owner of the business case and accountable for all aspects of governance.

    Responsibilities include, but are not limited to:

    • delivery of the project according to its business case, measured against the agreed baseline
    • ensuring the policy/business need is well defined and being addressed
    • assuring ongoing viability – including through effective use of assurance under the Assurance Framework for Digital and ICT investments
    • engaging key stakeholders
    • providing the team with leadership, decisions and direction
    • ensuring the delivered solution meets the needs of the agency and its stakeholders

    Senior User

    Also known as:

    • Business Owner
    • Senior User
    • Benefit Owner
    • Operations Manager
    • Asset Manager
    Member of board

    A business owner/senior user must be identified for all projects, no matter the size or complexity. There may be one or more senior users or operations managers at varying managerial levels depending on the size of the project. These are typically senior operational or policy staff who will benefit, or whose stakeholders will benefit.

    The senior user is a core member of the governance board.

    Responsibilities may include, but are not limited to:

    • providing subject matter expertise throughout the project, to ensure that business requirements are communicated, and products are tested and fit for purpose
    • representing the user experience
    • supporting change management and implementation
    • managing project outputs for their operational use
    • securing resources for the ongoing maintenance of the asset/solution
    • being accountable for the measuring and reporting of project outcomes
    • being responsible for the realisation of benefits from the investment

    Independent Board Adviser

    To note:

    • This role could be filled by a representative from another agency or by an externally-engaged specialist.
    • For the largest, most complex projects (Tier 1), the DTA may fulfil this role consistent with the Assurance Framework for Digital and ICT Investments.
    Member of board

    An independent board adviser provides scrutiny and constructive challenge to help keep the SRO and board focussed on what must go right for the project to succeed. They are free from material conflicts of interest to ensure they can faithfully discharge their responsibilities.

    Responsibilities may include, but are not limited to:

    • bringing their expert judgement to scrutinise project performance and identify emergent areas of risk drawing on past experience
    • probing and challenging project reporting to support high-quality decision-making
    • providing strategic foresight to assist the SRO and board in remaining focussed on what will 'make the difference' in ensuring the project succeeds
    • supporting the SRO to maximise the value of the board in enabling good decision-making
    • actively engaging in assurance planning to maximise its value in effectively managing key areas of risk
    Assurance providersIndependent advice and assurance to BoardProviding impartial, expert advice and assurance to support informed decision-making and successful delivery of digital initiatives. To achieve this, assurance providers conduct objective assessments of project health, delivery confidence, and risk exposure. They also help identify early warning signs and recommend corrective actions to support successful outcomes.
    DTACentral Oversight and Monitoring

    The DTA's role on digital project boards usually includes:

    • representing whole-of-government digital strategy and policy (including the Assurance Framework and Benefits Management Policy), and ensuring alignment, transparency, and value in digital investments
    • sharing insights and lessons learned from across government to uplift delivery capability and advise on creating conditions for success
    • encouraging continuous improvement in digital governance practices

    The DTA has a mandated role for Tier 1 projects as well as projects experiencing delivery difficulty. Advice will be provided to relevant projects.

    Project Management Office (PMO)Support

    Providing support, for example, on reporting, project management and project governance standards.

    PMOs may also advise on adherence to agency project governance frameworks, methodologies, and assurance processes; promote continuous improvement and uplift in project delivery maturity across the agency; and provide insights into interdependencies, capacity, and delivery risks across the agency and wider portfolio.

    SecretariatSupportProviding support to the Board to comply with corporate and project governance requirements and standards, for example, with meeting administration and ensuring accurate records of meetings.

    Project Risk Manager/Lead

    Also known as:

    • Chief Risk Officer
    Support

    The purpose of the risk role is to take the lead in ensuring that the project has effective processes in place to identify and monitor risks, has access to reliable and up-to-date information about risk and uses the appropriate controls and actions to deal with risks. This role should also ensure that these processes are aligned with enterprise and whole-of-government risk management policy.

    Responsibilities include, but are not limited to:

    • establish and maintain a project risk register, integrating where necessary with the enterprise risk register
    • assist in the identification and ongoing management of risks by running risk workshops and conducting risk review activities
    • ensure that all risks have a nominated owner and actioner; take a proactive stance in ensuring that risks are proactively managed across the project and its stakeholders
    • ensure that the agreed risk responses are planned, resourced and implemented
    • establish consistent mitigation and contingency plans for risk that should be tackled across the project
    • assess and monitor the effectiveness of risk processes and refine as necessary

    Depending on the size of the project, part or all of the risk manager's role may be subsumed within the project manager's role.

    Project Director

    Also known as:

    • Program Manager
    • Project Manager
    • Delivery Manager
    • Stream Lead
    • Deputy SRO

    To note:

    • In larger, more complex programs there may be multiple Project Directors reporting to a Program Director who is accountable to the SRO.
    Reports to board

    The project director is accountable to the senior responsible officer for establishing the governance framework and for the day-to-day management of the project, to deliver the outputs and desired outcomes, and realise the required benefits.

    Responsibilities may include, but are not limited to:

    • ensuring the solution is designed and business case and plans prepared
    • defining the approach, accountabilities, work scope and targets for the team
    • timely monitoring, forecasting and reporting overall progress against the plan
    • resolving risks and issues and controlling change within their delegation and escalating to the board those outside their delegation
    • delivering the required outputs and outcomes
    • monitoring and managing supplier performance
    • engaging and communicating with stakeholders

    Change Manager

    To note:

    • Change Manager will sometimes report to a business lead or business owner
    • Duties may be integrated into another PMO role such as Director/Manager role
    Reports to board

    Change managers may report directly to the project manager or PMO, but can also report to a business lead, business owner, or a separate change management function. These duties may also be integrated into another role such as Director/Manager role.

    The primary responsibility of an organisational change manager is to develop and implement change management strategies and plans that maximise employee adoption and usage of required changes.

    The change manager's goal is to drive faster adoption, higher ultimate utilisation of changes, and proficiency with the changes that impact employees who must use the changes in their daily work. These improvements increase benefit realisation, value creation, ROI, and the achievement of results and outcomes.

    Responsibilities include, but are not limited to:

    • Leverage a change management methodology, process and tools to create a strategy to support adoption of the changes required by a project or initiative
    • Lead changes (to business processes, work practices, organisational structure, training, communications, roles and responsibilities, and so on) to ensure the realisation of business benefits
    • Conduct impact analyses, assess change readiness, and identify key stakeholders
    • Communicate with stakeholders, particularly those who are directly affected either by the change itself or by the response to the change
    • Provide input, document requirements, and support the design and delivery of training programs
    • Evaluate the extent to which business change activities have contributed to the realisation of business benefits

    Benefits Manager

    To note:

    • Duties may be integrated into another role such as the Project Manager role
    Reports to board

    The purpose of the benefits and value role is to ensure that a consistent 'fit for purpose' approach to benefits and value management is applied across the portfolio or program and that benefits realisation is optimised from the organisation's investment in change.

    Responsibilities include, but are not limited to:

    • lead and facilitate the benefits identification and mapping workshops
    • develop and maintain a benefits map and accompanying benefits profiles
    • facilitate agreement of the benefits realisation plan
    • develop and maintain the benefits management framework and ensure alignment with activities
    • work with business change managers and their teams to promote more effective benefits management practices
    • maintain the benefits forecast and escalate issues with benefits realisation
    • set the standards for, and monitor post implementation reviews to compare benefits realised with benefits forecast to capture lessons in relation to benefits management for wider dissemination

    Duties may be integrated into another role such as Project Manager role and may be sourced from the PMO.

    Senior SupplierReports to board

    The Senior Supplier represents the interests of those designing, developing, facilitating, procuring and implementing the project's product/s. This role is accountable for the quality of the product/s (and its components) delivered by the supplier(s) and is responsible for the technical integrity of the project. If necessary, more than one person may represent the suppliers.

    The Senior Supplier may be within the agency, for example the CIO, or an external integration partner. Depending on the customer/supplier environment, the customer may also wish to appoint an independent person or group to carry out assurance on the supplier's products (for example, if the relationship between the customer and supplier is a commercial one).

    Responsibilities may include, but are not limited to:

    • providing supplier expertise throughout the project to ensure that technical requirements are understood and that the products are fit for purpose
    • representing the supplier's interests, ensuring the project team has the necessary resources (people, technology, funding) to create the solution
    • being accountable to the project executive for the technical aspects of the project, including progress reporting and issue resolution
    • being responsible for the technical viability of the solution, making sure it can be built, tested, and implemented successfully
    • communicating technical standards and guidance on areas such as technical compliance

    Note: Vendors should not play any Board role in decision-making regarding their own work, such as vendor selection, progress payments, change requests, or readiness assessment.

  • Guidance for Senior Responsible Officials

  • Assurance Research Series 02

  • References

    1. Chesterman, R. Queensland Health Payroll System Commission of Inquiry; 2013. http://www.healthpayrollinquiry.qld.gov.au/
    2. Rees, D. Review of the Modernising Business Registers Program; Commonwealth of Australia, Canberra, Australia, 2023. https://treasury.gov.au/sites/default/files/2023-08/review-modernising-business-registers-program-report-redacted_0.pdf
    3. QAO. Effectiveness of the State Penalties Enforcement Registry ICT reform; Queensland Audit Office, Brisbane, 2020. https://www.qao.qld.gov.au/reports-resources/reports-parliament/effectiveness-state-penalties-enforcement-registry-ict-reform
    4. Flyvbjerg, B.; Budzier, A.; Aaen, J.; Keil, M.; Zottoli, M. The Uniqueness of IT Cost Risk: A Cross-Group Comparison of 23 Project Types. Project management Journal 2025, in press.
    5. Drake, S.; Bekker, M. C. Functions of project steering committees in large capital projects. Procedia Computer Science 2023, 219, 2058-2066.
    6. PMI. A guide to the project management body of knowledge (PMBOK® Guide); Project Management Institute, 2021.
    7. Lechler, T. G.; Cohen, M. Exploring the role of steering committees in realizing value from project management. Project management journal 2009, 40 (1), 42-54.
    8. McGrath, S.; Whitty, S. Do steering committees really steer? International Journal of Managing Projects in Business 2018.
    9. APM. What is governance? 2025.
    10. Cooke, J. The PRINCE2 Agile® Practical Implementation Guide-Step-By-step Advice for Every Project Type [online]. IT Governance Ltd. 2021.
    11. Karlsen, J. T. The project steering committee, project governance and trust: insights from a practical case study. Management Research Review 2021, 44 (6), 926-947.
    12. PMI. The Standard for Project Management; Project Management Institute, 2024.
    13. Zwikael, O.; Meredith, J. R. Who's who in the project zoo? The ten core project roles. International Journal of Operations & Production Management 2018, 38 (2), 474-492.
    14. Pollack, J.; Anichenko, E. The ten differences between programs and projects, and the problems they cause. Engineering Management Journal 2022, 34 (2), 314-328.
    15. Stoppels, J.; Bosch-Rekveldt, M.; Mooi, H.; Bakker, H. Exploring Current Practice in the Formation and Functioning of Project Steering Committees. Journal of Modern Project Management 2023, 11 (2), 58-77.
    16. Huse, M. Corporate governance: Understanding important contingencies. Corporate Ownership & Control 2005, 2 (4), 41-50.
    17. Teisman, G.; Gerrits, L. The emergence of complexity in the art and science of governance. Complexity, Governance & Networks 2014, 1 (1), 17-28.
    18. Garland, R. Project governance: A practical guide to effective project decision making; Kogan Page Publishers, 2009.
    19. Garland, R.; Morey, A. Project, Program and Portfolio Governance; The Stationery Office, 2022.
    20. Smith, N. Reducing transformation friction: the role of organisational leadership in transformational project outcomes. University of Queensland, Queensland, 2021.
    21. Crawford, L. Steering committees as governance entities. In Research Handbook on the Governance of Projects, Edward Elgar Publishing, 2023; pp 116-123.
    22. Huang, R.; Zmud, R. W.; Price, R. L. Influencing the effectiveness of IT governance practices through steering committees and communication policies. European Journal of Information Systems 2010, 19 (3), 288-302.
    23. Loch, C.; Mähring, M.; Sommer, S. Supervising projects you don't (fully) understand: Lessons for effective project governance by steering committees. California management review 2017, 59 (2), 45-67.
    24. QAO. Queensland Health's new finance and supply chain management system; Brisbane, 2020. https://www.qao.qld.gov.au/sites/default/files/2020-09/Queensland%20Health%27s%20new%20finance%20and%20supply%20chain%20management%20system%20%28Report%204%E2%80%942020%E2%80%9321%29.pdf
    25. Dolfing, H. Project Failure Case Studies: Lessons learned from other people's mistakes; Amazon, 2020.
    26. Cresswell, K.; Ali, M.; Avery, A.; Barber, N.; Cornford, T.; Crowe, S.; Fernando, B.; Jacklin, A.; Jani, Y.; Klecun, E.; et al. Adoption of the National Health Service Care Records Service (NHS CRS) in Secondary Care in England: Final report for NHS Connecting for Health Evaluation Program; 2011.
    27. Atlassian. A project management team's guide to successful project governance. 2021.
    28. McGrath, S.; Whitty, S. Governance terminology confusion in management and project management reference documents. Journal of Modern Project Management 2019, 7 (3), 146-171.
    29. Prasad, A.; Heales, J.; Green, P. A capabilities-based approach to obtaining a deeper understanding of information technology governance effectiveness: Evidence from IT steering committees. International Journal of Accounting Information Systems 2010, 11 (3), 214-232, Article. DOI: 10.1016/j.accinf.2010.07.013 Scopus.
    30. Müller, R. Project governance; Gower Publishing, 2017.
    31. Olsson, N. Elaborations on the role of project owner: introducing project owners type 1 and 2. International Journal of Managing Projects in Business 2018, 11 (3), 827-844.
    32. Sia, S. K.; Weill, P.; Zhang, N. Designing a future-ready enterprise: The digital transformation of DBS bank. California management review 2021, 63 (3), 35-57.
    33. Woerner, S. L.; Weill, P.; Sebastian, I. M. Future ready: the four pathways to capturing digital value; Harvard Business Press, 2022.
    34. Mosavi, A. Exploring the roles of portfolio steering committees in project portfolio governance. International Journal of Project Management 2014, 32 (3), 388-399. Scopus.
    35. Jenkins, M.; Warendh, A. Is it time to consider co-CEOs? Harvard Business Review 2022, Jul-Aug 2022.
    36. QAO. Report to Parliament No. 7 for 2010 Information systems governance and control, including the Queensland Health Implementation of Continuity Project; Queensland Audit Office, Brisbane, 2010. http://www.healthpayrollinquiry.qld.gov.au/__data/assets/pdf_file/0009/177903/Auditor-General_of_Queensland_Report_to_Parliament_No_7_for_2010.PDF
    37. Brunet, M.; Petit, M.; Romero-Torres, A. Interorganizational design for collaborative governance in co-owned major projects: An engaged scholarship approach. Project Management Journal 2024, 55 (5), 580-598.
    38. Whiteley, A.; Pollack, J.; Matous, P. The origins of agile and iterative methods. The Journal of Modern Project Management 2021, 8 (3).
    39. PMI. Agile Practice Guide; Project Management Institute, 2017.
    40. Smith, N.; Burton-Jones, A.; Sullivan, C. From benefits idealisation to value optimisation: Application in the digital health context. Australian Health Review 2020, 2020 (44), 706-722.
    41. NSW Government Sydney Water Customer Experience Program (CxP): Lessons to Emulate. 2021.
    42. Elonen, S.; Artto, K. A. Problems in managing internal development projects in multi-project environments. International journal of project management 2003, 21 (6), 395-402.
    43. Murphy, K. A Theory of Steering Committee Capabilities for Implementing Large Scale Enterprise-Wide Information Systems; Case Western Reserve University, 2016.
    44. Shergold, P. Learning from Failure: Why large government policy initiatives have gone so badly wrong in the past and how the chances of success in future can be improved. Commission, A. P. S., Ed.; Australian Public Service Commission, 2015.
    45. Axelos. Managing Successful Projects with PRINCE2; The Stationery Office, 2017.
    46. DTA. Closure Reporting Standard for Digital and ICT-enabled Projects. Digital Transformation Agency, 2024. https://architecture.digital.gov.au/standard/closure-reporting-standard-digital-and-ict-enabled-projects
    47. Lewis, E.; Millar, G. The viable governance model: A theoretical model for the governance of IT. In 42nd Hawaii International Conference on System Sciences, 2009; IEEE.
    48. Hamilton, S. Moveable Transactions Project – Senior Responsible Officer (SRO) reflections. Scottish Government, 2024. https://blogs.gov.scot/digital/2024/11/13/moveable-transactions-project-senior-responsible-officer-sro-reflections
    49. ANAO. myGov Digital Services. Australian National Audit Office, 2024. https://www.anao.gov.au/work/performance-audit/mygov-digital-services
    50. House of Commons. Oral evidence: Lessons learned: Delivering value from government investment in major projects – HC 456. Public Accounts Committee: 2024.
    51. Department of Treasury and Finance. Project Governance Guidelines. 2012.
    52. Infrastructure and Projects Authority. Government Functional Standard GovS 002: Project delivery portfolio, program, and project management. 2021.
    53. IPA. Project delivery: guidance. The role of the senior responsible owner Infrastructure and Projects Authority: UK, 2023.
  • Next page

    Appendix: Digital Project Governance Board Roles and Responsibilities

  • Next page

    References

Connect with the digital community

Share, build or learn digital experience and skills with training and events, and collaborate with peers across government.