Engineering firms choose which projects count.

The way designs get built and changed

AI labs learn most from records that show engineering judgment, not finished drawings alone:

• CAD models plus the revisions behind each one
• Bills of materials and calculation spreadsheets
• How simulation work compared with real tests
• Notes from design reviews showing why something changed
• Your own products, with their schematics and inspection data

Names become placeholders

In the copy, placeholders replace the names of clients, vendors and engineers, as well as addresses and account numbers. The original files never leave your systems or your vault, and passwords are never requested. A sample of what was prepared needs your yes before anything leaves.

Client-owned designs may be left out

A design that is a client's property or falls under an NDA can be excluded one project at a time. Whether your agreements allow any client work is a call for your firm and its counsel. We do not give legal advice about it. Your own internal methods and product lines are often the simpler place to start.

Export-controlled work stays out

Some programs carry export controls on their technical data. Such a project can be kept out of scope entirely, and you are the person who identifies it. If you are unsure about a project, leave it out.

Getting started

Ask for the estimate, then use the first short call to walk through which projects are clearly yours and which are not. A simple list helps: internal product lines, client programs, anything under NDA, anything export controlled. Most scopes start from the first group. The list can change over time, but preparation waits for your agreement and nothing leaves until the sample has your approval. Your engineers can keep working the whole way through.