Short guides to the records we're asked about most: what tends to be useful, what usually stays out or needs care, and how to prepare. They apply whether you hold the records or want to license them. For the wider picture of how records connect, see the data families on the homepage.
- Slack and Teams chat
- CAD and engineering files
- Job and project files
- CRM and customer support records
- Source code and software records
- Lab and research data
- Recorded calls
Email threads show who knew what, what it cost and what was decided. That context is hard to find anywhere else.
What tends to be useful
- Threads with customers and suppliers about quotes, orders, changes and problems
- Internal discussion where decisions were made
- Attachments that link back to jobs, orders or drawings
What usually stays out, or needs care
- Personal and HR email, payroll, and anything about individuals' health
- Client material held under confidentiality, unless the client agrees
- Payment details and passwords
Preparing: email accounts often close when the bills stop, so check what is still retained and exportable. A mailbox export does not by itself establish permission to license everything inside it.
Slack and Teams chat
Chat channels capture the quick fixes and decisions that never make it into a manual.
What tends to be useful
- Project and operations channels where work was coordinated
- Threads that link to tickets, orders or drawings
- Support and engineering channels
What usually stays out, or needs care
- Private messages and personal conversations
- HR, disciplinary or health discussions
- Shared channels with other companies, unless they agree
Preparing: export options and retained history depend on your plan and settings, so check them before an account is downgraded or closed.
CAD and engineering files
Drawings with their revision history show how designs changed and why.
What tends to be useful
- Drawings with revisions, tied to the job or part
- Calculations, specifications and technical reports
- Change requests and the correspondence around them
What usually stays out, or needs care
- Designs owned by clients or architects under your contracts
- Material under export-control or defence restrictions
- Files that can't be opened without lapsed software licences
Preparing: keep revisions together with the job or part they belong to, and check that the files still open.
Job and project files
A job file follows the work from enquiry to invoice. Linked together, these records show how a business really ran.
What tends to be useful
- Quotes, estimates and take-offs, with the notes behind them
- Job sheets, site diaries, inspection and completion reports
- Project software histories, for example from Jira, Asana or Procore
What usually stays out, or needs care
- Customers' personal details
- Client-owned documents and anything under a confidentiality agreement
- HR and health and safety records about individuals
Preparing: the links between records matter most, so keep job references, dates and versions intact where you can.
CRM and customer support records
Tickets and account histories record real problems, fixes and outcomes.
What tends to be useful
- Support tickets and their resolutions
- Account and order histories, with customers' details removed
- Service notes and knowledge-base articles
What usually stays out, or needs care
- Customer names, contact details and anything that identifies individuals: these need the most care
- Payment details
- Customer databases themselves, which raise separate legal questions
Preparing: customer records are heavily regulated, so expect careful scoping under the applicable privacy law.
Source code and software records
Code with its history, reviews and tickets shows how software was really built and fixed.
What tends to be useful
- Repositories with commit history and code review
- Linked tickets, incidents and design documents
- Data team files such as pipelines and dashboards
What usually stays out, or needs care
- Code written for clients who own it under contract
- Third-party and open-source code under licences that restrict reuse
- Secrets: keys, passwords and credentials. Never send these
Preparing: ownership is the first question, then whether history and linked tickets survive export.
Lab and research data
Raw results with the judgement calls, retests and notes show how real analysis gets done.
What tends to be useful
- Test and assay results with the methods and notes behind them
- Instrument outputs linked to samples and reports
- Quality and calibration records
What usually stays out, or needs care
- Patient and clinical data, and other health information: usually excluded
- Data owned by clients or research sponsors under contract
- Anything under ethics approvals or consent terms that don't allow reuse
Preparing: keep results linked to their methods, samples and reports.
Recorded calls
Recorded conversations between staff and customers can be useful to AI teams building voice and customer-service tools.
What tends to be useful
- Everyday customer calls: sales, service, bookings and scheduling, dispatch and support, handled by the business's own staff
- Calls the business owns. Calls recorded on behalf of a client are normally for that client to decide about
- Volume and history. More hours over more years is generally more useful. Transcripts help but aren't essential
What usually stays out, or needs care
- Health, payment and other sensitive details, which are usually left out
- Calls where the recording terms, or the call-recording provider's terms, restrict reuse
Preparing: a "calls may be recorded" message tells callers that recording happens. On its own it does not give permission to use the recordings for AI training or to license them. Who owns the recordings, what callers and staff were told, and how personal data would be handled all need checking first.
Next step
Don't send files: describe what you have. How rights and personal data are handled is on rights, authority and how records are handled. Record holders can start at licensing your business records; AI teams can discuss a use case. Or email hello@maevar.com.