slug: clockodo
provider: Clockodo
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: Customers
  spec_file: clockodo-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: GET /v2/customers  listCustomers  List customers; POST /v2/customers  createCustomer  Create
    a customer
  reason: Full CRUD over customer master records (the vendor lists 'customers' among the objects mirrored
    from the UI), which is customer data management. Not a deeper CRM lifecycle surface — no segmentation
    or lifecycle operations.
- tag: Absences
  spec_file: clockodo-absences-api-openapi.yml
  capability_id: BC-300.70
  capability_id_l1: BC-300
  capability_name: HR Operations Management
  confidence: 0.7
  evidence: GET /absences  listAbsences  List absences; POST /absences  createAbsence  Create an absence
  reason: CRUD over employee absence records in a workforce time-tracking product is leave/absence administration,
    an HR operations activity. L2 chosen as HR Operations Management (employee records/administration);
    some chance it belongs under benefits administration, hence moderate confidence.