Data library

Project records for AI.

Quick answer

Yes, in many cases. Project records — plans, task lists, schedule changes, status updates and the final outcome — show how teams plan and deliver real work. A company can license them when it owns the records, client contracts allow it, and client and staff details are removed.

What's included#

Project plans, milestones and task breakdowns
Assignments, due dates and schedule changes
Status updates, blockers and decisions
Final outcome versus plan

Where it typically lives

AsanaMonday.comJiraSmartsheetProcoreMicrosoft Project

How AI developers use it#

Training AI agents to plan and track multi-step work
Evaluating schedule and risk predictions
Teaching models how plans change in practice

Preparation and privacy#

Replace client and staff names with stand-ins
Remove contract values your team chooses to hold back
Keep dates and task order intact

What's usually left out#

Projects whose client contracts forbid sharing
Bids and pricing your team chooses to hold back
Attached files not reviewed separately

How it's packaged#

One record per project with tasks and an event timeline
A data sheet listing project types, years covered and count

What makes it valuable#

Complete projects from kickoff to close
Recorded changes and the reasons behind them
Consistent use of the tool across teams

Starting with a sample#

One or two completed projects, cleaned and approved by you

How SourceX approaches it#

Preparation requirements are agreed with you before any work begins, and the approved dataset is delivered only after an executed agreement and your explicit authorization of buyer access.

Industries with this data

Datasets built from this data

Dataset specs AI labs can request through SourceX, sourced to spec from businesses like yours.

Typical fields#

Record ID (pseudonymous)
Created and closed timestamps
Category or type
Request or input text
Ordered steps or actions
Outcome or resolution
Role of each actor (not identity)

Sample record

Illustrative · fictional

record_id: rec_8f21c0
created / closed: 2023-04-11 → 2023-04-12
category: Billing question
request: Customer [NAME] asks why invoice [ID] was charged twice.
steps: 1. Checked payment log 2. Found duplicate 3. Issued refund
outcome: Resolved · refund issued
actors: customer, agent_tier1

What buyers look for#

Complete start-to-finish records
Consistent fields over years
Clear, labeled outcomes
Low duplication
Work done by skilled professionals
Edge cases and failures, not only successes

Personal details removed#

Names
Email addresses
Phone numbers
Postal addresses
Account, customer and order numbers
Government IDs
Payment details
Health information
IP addresses and device IDs
Credentials, keys and hostnames

How buyers test it#

Sample review by buyer researchers
Residual personal-data scan
Duplicate and leakage check against public data
Label and outcome accuracy spot-check
Rights and consent documentation review

Rules that may apply

Federal Wiretap Act 18 U.S.C. 2511
Applies to recorded calls and intercepted communications; some states require all-party consent. Assessed deal by deal.
California Consumer Privacy Act Cal. Civ. Code 1798.100 et seq.
May apply where records include personal information of California residents and the business meets the law's thresholds. Assessed deal by deal.

Reviewer note: applicability is confirmed with counsel for each deal. Not legal advice.

All data types · Sales call transcripts · Source code · Change approval records

Frequently asked questions

What if most of our projects are for clients?

Client contracts decide it. Some allow it once client details are removed; others don't, and those are left out.

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if you qualify Talk to SourceX