Work you've already recorded.

Buyers want the history behind the work: what was asked, what your team did and how it turned out. These are the records that usually show it.

Work orders and service history

ERP · Field service · Spreadsheets

Each job from the fault report to the fix, with parts, hours and outcome.

Request: Pump 3 at Customer 41 loses pressure after start-up.
Action: Technician replaces the seal kit and recalibrates the valve.
Result: Pressure stable. Job closed in 2.5 hours.

Maintenance and quality records

CMMS · QMS · Inspection logs

Planned maintenance, inspections, defects found and how they were resolved.

Inspection: Weld seam on batch 1182 fails visual check.
Cause: Wire feed speed drifted on line 2.
Result: Setting corrected; batch reworked and released.

Sales and quoting history

CRM · ERP · Email

Enquiries, quotes, revisions and why a customer said yes or no.

Enquiry: Company 12 needs 40 custom brackets in stainless steel.
Quote: Two options sent; customer asks for a shorter lead time.
Result: Revised quote accepted. Order placed.

Engineering and design files

CAD · PDM · File server

Drawings, revisions and change requests, with the reasons behind each change.

Change request: Customer reports interference with the mounting plate.
Revision: Hole pattern moved 4 mm; drawing revision C issued.
Result: Fit confirmed on the next delivery.

Project histories

Project tools · Email · Shared drives

Plans, handovers, delays and decisions across a project from start to finish.

Plan: Line installation scheduled over three weekends.
Issue: Supplier delay on control cabinet.
Result: Sequence changed; commissioning one week late.

Customer support logs

Helpdesk · Email · Phone notes

A customer's problem, the steps your team took and how it was fixed.

Question: Machine shows error E07 after a firmware update.
Reply: Support walks the customer through a sensor reset.
Result: Error cleared; fix added to the service notes.

Examples are illustrations. Names and numbers are made up, and not every archive qualifies.

What to describe on the first call

You don't need to send anything. Rough figures are fine.

The systems you use, such as ERP, CRM, maintenance or CAD
How many years of records you hold
Roughly how many people use those systems
The types of records: work orders, service history, project files

Questions

Records from years of ongoing operations, such as work orders, service history and maintenance logs, are the usual starting point. We tell you on the call whether yours are worth taking further.

Passwords, banking details, personal identities sold as-is and access to live systems are never part of a deal. Anything else you want excluded stays out too.

You decide. Redaction and anonymization rules are agreed with the buyer before anything is shared, and your records never pass through Corsano.

Recognise any of these? Tell us which records you keep.

Discuss your data