One job or case sample
If the buyer selected a job, document or task, use that exact example. Agree which connected systems and dates to include. Start with one complete case when the brief leaves the count open.
What to collect
- The starting record
- Include the approved lead, request or ticket as it was received, with a case alias, date and the evidence the team had at the time.
- The work and the decision
- Follow the same ID into the estimate, messages, revisions and approvals the brief calls for. Include the native files behind links when permitted.
- The outcome
- Supply the accepted design, closed ticket, reconciled ledger or other record that shows how the work finished. For a task evaluation, identify what a correct outcome can be checked against.
- A case index
- Name the source business using the agreed alias, list the systems and file paths, and explain any link made by inference instead of a shared ID.
Keep unrelated cases and customers out. Mark a missing attachment or unanswered question explicitly.
Export from your systems
Pack and check
Put the README and manifest at the top of the folder, with a subfolder for each system. The manifest is a file index a reviewer can read without opening every file.
Download blank manifest (.csv) ↓Example manifest entry
- File in the package
estimates/JOB-04.csv- Matching key
job_id = JOB-04- Related record
- field-service/completed-jobs.csv contains JOB-04
Includes all systems for this sample type and your current checks.
Share through your private workspace.
Once Maryah confirms the scope and permission to share, open the matching dataset and choose Samples. Follow the size and format limits shown there.
Open my datasetsFor a larger package or help locating your dataset, contact Maryah for a private transfer route. Include your dataset reference and file size.