T Level Digital: Codes of Conduct, Standards and Digital Inclusion

Alongside the law, the Pearson digital T Level cores ask what guides a digital professional where the law is silent, and who a digital service might leave out. That content is shared by the Digital Software Development, Digital Support and Security and Digital Data Analytics cores, which are assessed through two written papers and an employer-set project, and it is where questions about ethics and fairness usually come from: a professional body's code against a manager's deadline, a screening tool that learned the wrong lesson from old data, a council service that only works for people who are online.

The quiz has twelve questions set in invented organisations. Three match a need to the body that sets the standard: card payments and the PCI Security Standards Council, accessibility success criteria graded A to AAA and the Web Content Accessibility Guidelines, and Wi-Fi equipment and the IEEE. Four deal with professional behaviour: a developer told to release an update that exposes patient records, a laptop used for cryptocurrency mining and the acceptable use policy that should have forbidden it, an analyst who finds a breach being hidden and needs a whistleblowing procedure, and telling a professional body's code apart from an employer's or the government's. Four deal with inclusion: a recruitment tool trained on a decade of skewed hiring, a parking permit service moved online, the accessibility requirements for a public body's website, and an app designed for readers over seventy. The last asks what professional development actually brings. Every explanation says why the key follows from the scenario and why the other options do not.

The flashcards cover the sources of codes of conduct, the named professional bodies, each standards body with an example of what it publishes, the contents of an acceptable use policy, whistleblowing, the parts of digital inclusion and the end-user characteristics that affect it.

The written work has eight tasks to answer on paper. Five are explanations: matching standards to three needs of a retailer, the contents of an acceptable use policy, why whistleblowing matters, how bias gets into an automated recruitment tool and how to reduce it, and designing a benefits service for three kinds of user. Two are longer, evaluative answers of the kind used for the higher-mark questions: whether codes of conduct are needed when the law already applies, and whether a council should close its telephone and counter services. The last covers the benefits of professional development. Each has a model answer and the points a marker would look for.

There is also a short oral practice with an examiner, who describes an organisation, asks one question at a time and gives brief feedback at the end.

  • Name the sources of codes of conduct and explain how codes influence professional behaviour
  • Match a workplace need to the standards body or guidelines that cover it (ISO, WCAG, W3C, IETF, BS, IEEE, PCI SSC)
  • Describe the purpose and typical contents of an acceptable use policy
  • Explain why whistleblowing procedures matter
  • Explain how bias in datasets undermines fair access and how to reduce it
  • Design for end-user characteristics such as age, digital skills and additional needs
  • State the accessibility requirements for public sector websites and apps

Practice material written by Zestly, based on the core content of the Pearson T Level Technical Qualifications in Digital Software Development, Digital Support and Security and Digital Data Analytics (first teaching September 2025): 4.2 guidelines (codes of conduct, industry standards, acceptable use policies, whistleblowing) and 3.1 digital inclusion and end-user characteristics. Public sector accessibility requirements as described in gov.uk guidance.

Sample question

Ormskirk Outdoor, an invented online retailer, takes card payments on its website. Its bank tells it to show that it stores, processes and transmits card data securely, following the industry's security standard for cardholder data. Which body publishes that standard?

See the answer

The Payment Card Industry Security Standards Council (PCI SSC)

The PCI Security Standards Council publishes the Data Security Standard (PCI DSS) that organisations handling payment card data are expected to meet. W3C writes web standards such as HTML and the accessibility guidelines, the IETF writes internet protocol standards, and the IEEE writes engineering standards such as those for Wi-Fi and Ethernet.

← Digital

↑ T Levels and BTEC