Support & managed IT
Troubleshooting paths, runbooks, reproduction steps and recorded resolutions, stripped of credentials and appropriately reviewed for client information.
← All sector guides
From issue to tested change
Software, computing & telecommunications
An issue, a code change and a test result are more informative together. Support histories, runbooks and versioned technical work can reveal how problems were investigated and resolved.
Discuss records in this sectorDigital & creative
Can the technical response be linked to the evidence that followed?
Access to a repository or support system does not establish the right to license its contents. The discussion starts with ownership, project scope and exclusions, not a system export.
Illustrative connectionNot a sample archive or a promise of value
- 01
Issue or requirement
- 02
Reasoning & versioned change
- 03
Test, review or deployment evidence
- 04
Resolution or regression
Relevant records
Look beyond
the final file.
What was known, what was decided, what happened and what the evidence shows.
The examples below are categories to discuss. Existence, rights, suitability and buyer requirements still need to be established.
Software & product work
Code and configuration versions, issue histories, design discussions, review corrections and tests, where the business controls the relevant rights.
Infrastructure & telecoms
Permitted event descriptions, capacity or performance histories and service interventions with their operational context.
Potential uses, not promised demand
What might an AI team investigate?
- Evaluating issue-to-resolution retrieval and evidence-based technical answers.
- Studying versioned workflows and the relationship between tests, changes and later incidents.
- Researching permitted software-agent tasks without implying that any dataset is ready for training.
Any actual recipient, purpose and permitted use must be agreed. These are research and evaluation possibilities, not confirmed buyers, available datasets or claims of proven AI performance.
Before anything is shared
The boundaries
are part of the work.
- Never send credentials, API keys, tokens, live configurations, exploitable incident details or access links in an enquiry.
- Client repositories, employee contributions, third-party code and open-source licences need separate ownership and licence review.
- Logs and support tickets can contain personal information and secrets even when their filenames appear harmless.
McKays does not promise that redaction or anonymisation will make material suitable. Detailed review, preparation responsibilities and any specialist advice must be agreed separately.
Find your kind of business
Specific work.
Specific records.
Explore examples for the businesses and organisations in this sector.
Managed IT service providers
Record classes to describe, not upload
- Support tickets and customer correspondence
- Troubleshooting paths and resolution decisions
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveCybersecurity service companies
Record classes to describe, not upload
- Detection and incident-event logs
- Incident evidence and investigation findings
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveSoftware development agencies
Record classes to describe, not upload
- Code changes, reviews and test histories
- Issue workflows and resolution steps
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveSaaS vendors
Record classes to describe, not upload
- Product workflows and support-linked software actions
- Application logs and diagnosed failures
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveVideo-game studios
Record classes to describe, not upload
- Playtest and gameplay recordings
- Bug reports and reproduction evidence
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveTelecommunications operators
Record classes to describe, not upload
- Network telemetry and service-quality logs
- Fault repair and restoration outcomes
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveData-centre operators
Record classes to describe, not upload
- Power, cooling and equipment telemetry
- Outage investigations and recovery decisions
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveDomain registrars
Record classes to describe, not upload
- Registration support and abuse correspondence
- Registration exception and verification workflows
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveData-annotation companies
Record classes to describe, not upload
- Annotation instructions and reviewer corrections
- Disagreement resolutions and labelling decisions
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveUser-experience research agencies
Record classes to describe, not upload
- Usability sessions and screen recordings
- Task difficulties, feedback and observed behaviour
- Support, development and operational issue discussions
- Runbooks, reproduction steps and recovery procedures
Examples to investigate, not a claim that these records exist, are owned by the holder or can be licensed.
Discuss this type of archiveNo matching business type in this guide. Search all sectors, or describe your records in an enquiry.
A useful first enquiry
Start with a description.
Not the archive.
Describe the product or service type, archive years, record systems, version links and whether the business owns or merely accesses the material.
Paper, digital and mixed archives can be discussed. Approximate answers are fine. Mention your role, who can authorise a review and any practical deadline.
Prepare an enquirySend a non-confidential enquiry through the website. No archive files are uploaded.