Skip to main content

Technology Code of Practice (TCoP) Review

The /arckit.tcop command generates a comprehensive Technology Code of Practice review for UK Government technology projects.

What is TCoP?

The Technology Code of Practice is a set of 13 criteria to help UK Government design, build, and buy technology. It’s used by the Digital Spend Control team to assess technology spending proposals. TCoP is the implementation guidance for Government Functional Standard GovS 005: Digital.

Command: /arckit.tcop

Usage

/arckit.tcop 001  # By project ID
/arckit.tcop "Land Registry Digital Gateway"  # By project name
Arguments:
  • Project ID (e.g., 001) or project name

Output: ARC-{PROJECT_ID}-TCOP-v1.0.md

Generates a TCoP review document with compliance assessment for all 13 points.

The 13 TCoP Points

Point 1: Define User Needs

  • Understand user needs through research
  • Test prototypes with real users
  • Have a plan to test the service with users frequently
Evidence: User research, personas, usability testing from ARC-*-STKE-*.md and ARC-*-REQ-*.md

Point 2: Make Things Accessible and Inclusive

  • Meet accessibility standards (WCAG 2.1 AA minimum)
  • Test with assistive technologies
  • Make it easy for everyone to use your service
Evidence: Accessibility requirements (NFR-A), testing results, accessibility statement

Point 3: Be Open and Use Open Source

  • Publish your code under an open source license
  • Use open source software to avoid lock-in
  • Share learning and collaborate
Evidence: Repository links, open source licenses, contribution guidelines from HLD review

Point 4: Make Use of Open Standards

  • Use open standards and common platforms
  • Build services on open standards (APIs, data formats)
  • Contribute to the development of open standards
Evidence: API standards (OpenAPI), data standards (JSON, CSV), GOV.UK Design System usage

Point 5: Use Cloud First

  • Consider public cloud solutions first
  • Justify exceptions to cloud-first policy
  • Use cloud-native patterns
Evidence: Cloud strategy from principles, infrastructure choices from HLD, deployment architecture

Point 6: Make Things Secure

  • Identify security and privacy threats
  • Have a plan to address security risks
  • Collect and process personal data securely
Evidence: Threat model, security controls from ARC-*-SECD-*.md, Cyber Essentials certification

Point 7: Make Privacy Integral

  • Comply with data protection legislation (UK GDPR, DPA 2018)
  • Complete a Data Protection Impact Assessment (DPIA) if required
  • Have a plan for managing data subject rights
Evidence: DPIA from ARC-*-DPIA-*.md, privacy policy, data protection controls

Point 8: Share, Reuse and Collaborate

  • Avoid duplicating technology that’s already available
  • Use common platforms and services (GOV.UK Notify, Pay, etc.)
  • Share your solutions with other teams
Evidence: Research showing reuse of existing solutions, use of GOV.UK platforms, collaboration with other departments

Point 9: Integrate and Adapt Technology

  • Use APIs to integrate services
  • Plan to adapt your technology as needs change
  • Consider using microservices architecture
Evidence: Integration architecture from diagrams, API design from HLD, evolution strategy

Point 10: Make Better Use of Data

  • Use data to inform decisions
  • Have a plan for managing and improving data quality
  • Publish data for reuse where appropriate
Evidence: Data model from ARC-*-DATA-*.md, data quality framework, analytics strategy

Point 11: Define Your Purchasing Strategy

  • Know your total cost of ownership
  • Consider build vs buy
  • Avoid vendor lock-in
  • Follow government procurement rules
Evidence: Research showing build vs buy analysis, procurement strategy from ARC-*-SOW-*.md, cost analysis from ARC-*-SOBC-*.md

Point 12: Make Your Technology Sustainable

  • Consider environmental impact
  • Use energy-efficient technology
  • Plan to reduce carbon footprint
Evidence: Sustainability requirements (NFR-ENV), carbon footprint assessment, green hosting strategy

Point 13: Meet the Service Standard

  • Follow the GDS Service Standard for public-facing services
  • Book and pass service assessments
Evidence: Service Standard assessment preparation from /arckit.service-assessment

Assessment Criteria

Each point is assessed as:
  • ✅ Compliant: Clear evidence exists, all key criteria met, no significant gaps
  • ⚠️ Partially Compliant: Some aspects addressed but gaps remain, evidence incomplete
  • ❌ Non-Compliant: Criteria not met, no evidence of compliance, critical gaps exist
  • N/A: Point genuinely not applicable (e.g., Point 13 if not building a public service)

Report Contents

The TCoP review document includes:
  1. Executive Summary
    • Overall TCoP compliance status
    • Compliance scorecard (X/13 compliant)
    • Critical issues requiring immediate attention
    • Key strengths
  2. Detailed Assessment (for each of 13 points)
    • Status: ✅/⚠️/❌/N/A
    • Evidence of compliance (with file references)
    • Checklist items
    • Gaps and required actions
    • Specific recommendations
  3. Overall Compliance Summary
    • Score breakdown by status
    • Critical issues list
    • Prioritized recommendations (High/Medium/Low)
  4. Next Steps
    • Immediate actions (before next gate)
    • Short-term improvements (1-3 months)
    • Long-term enhancements (3-6 months)
  5. GovS 005 Alignment Mapping
    • Traceability between TCoP points and GovS 005 principles
    • Governance obligations

Project Phase Considerations

TCoP expectations vary by project maturity: Discovery/Alpha:
  • User research, technical spikes, open source exploration expected
  • Cloud-first policy application
  • Initial security and privacy considerations
Beta:
  • Accessibility testing complete
  • Security assessments complete
  • DPIA completed (if processing personal data)
  • Open source code published
Live:
  • All 13 points must be fully compliant
  • Continuous improvement demonstrated
  • Performance data published

Common Critical Issues

Issues that often block progression: Point 2 (Accessibility):
  • No accessibility testing for user-facing services
  • WCAG 2.1 AA compliance not achieved
Point 5 (Cloud First):
  • Public cloud not considered
  • Cloud-first exemption not justified
Point 6 (Security):
  • No security assessment completed
  • Cyber Essentials not obtained
Point 7 (Privacy):
  • No DPIA for projects processing personal data (BLOCKING for Beta)
Point 1 (User Needs):
  • No user research conducted
  • Service built without user testing

Integration with Other Commands

TCoP assessment works best when combined with:
  • /arckit.service-assessment - GDS Service Standard (Point 13 requires this)
  • /arckit.secure - Security assessment (Point 6 evidence)
  • /arckit.dpia - Data Protection Impact Assessment (Point 7 evidence)
  • /arckit.research - Technology research (Point 11 build vs buy)
  • /arckit.wardley - Strategic technology choices (Point 11)
  • /arckit.requirements - If requirements weak (Point 1)

Digital Spend Control

For Digital Spend Control submissions, focus on these points:
  • Point 5 (Cloud First) - Justify cloud strategy
  • Point 11 (Purchasing Strategy) - Total cost of ownership, procurement route
  • Point 8 (Reuse and Collaboration) - Use of existing platforms
TCoP compliance is required for spend approvals >£100k.

Re-running for Updates

Re-run the command when project state changes:
/arckit.tcop 001
The command will:
  • Detect existing ARC-{PROJECT_ID}-TCOP-v*.md files
  • Determine whether to increment version (minor or major)
  • Compare current state against previous assessment
  • Update compliance status based on new evidence
Version increments:
  • Minor (e.g., 1.0 → 1.1): Refreshed assessments, updated evidence, corrected details
  • Major (e.g., 1.0 → 2.0): New TCoP points assessed, fundamentally different compliance posture

Resources

Official Guidance: Supporting Standards:

Example Use Cases

Technology approval:
/arckit.tcop 001  # Assess compliance before Digital Spend Control submission
Quarterly review:
/arckit.tcop 001  # Regular compliance check, update evidence
Architecture governance:
/arckit.tcop 001  # Validate technology choices against TCoP principles

Build docs developers (and LLMs) love