David SchweickartRichmond, Virginia

Automotive logistics · Operating systems

Automotive freight operations and systems

Building the processes, information, and team structure behind a growing, round-the-clock automotive freight operation.

01Operating structureSupplier, order, and shipment responsibilities02Software requirementsTranslate operating needs into usable tools03Exceptions and carriersReason codes and scorecards04Document handoffsReuse shipment data for customs information

Project context

At Expeditors, I developed operating processes and software requirements for Chrysler’s expedited automotive freight program. The operation grew from three people to more than fifty, covering time-critical movements around the clock. My work combined daily execution, process development, hiring, training, and collaboration with software developers.

Operating structure

I worked across every shift and organized responsibilities around supplier management, order management, and shipment execution. I hired and trained team members across shifts. Clear responsibilities mattered because urgent movements continued through the night, and the next shift needed a usable record of the shipment and the customer’s requirement.

Transportation-management software

I translated operating needs into software requirements and worked directly with developers. The tools had to support the way the freight actually moved: supplier information, orders, carrier capacity, shipment decisions, and the exceptions requiring a person’s attention. My role connected the operating team with the people building the software.

Reason codes and carrier scorecards

I introduced reason codes for delays and exception bidding and worked on carrier scorecards. Recording why something happened gave the team more useful information than a shipment status alone. It created a basis for reviewing recurring problems, distinguishing exceptions, and focusing follow-up with carriers.

Shipment and customs documentation

Cross-border shipments exposed repeated manual work. Supplier advance shipping notices already contained information that was being entered again for customs invoices. I worked on using that existing data to generate documentation and improve the internal handoff to the brokerage process. The aim was to reduce re-entry and leave shift leads focused on exceptions.

Customer and international coordination

My experience included on-site work at Chrysler headquarters and direct coordination around production requirements and deliveries. I also developed routes involving Brazil and worked on charter movements of engine blocks. These movements required the operating plan, carrier arrangements, and customer information to remain connected.

Professional contribution

I built processes and requirements that could be used across shifts as the program expanded. The work joined transportation execution with the operating tools, documentation, and training needed to support it.

A closer look at the operating information

A worked example of how recording a reason can support review.

The software was developed collaboratively. Names and logos identify the organizations involved and their historical roles.