Employer profile · to
Nashville DDC
Federal OSHA safety record across 2 records in Tennessee.
How these records are matched, and what they cover. Records are grouped by normalized employer name. Nothing in OSHA's published files ties them to a legal entity. Unrelated companies that happen to share a name are combined onto one profile, and there is no EIN, address, or parent-company check to separate them; conversely, one company filing under several spellings can appear as several profiles. Severe-injury data covers establishments under federal OSHA jurisdiction only: about 22 states run their own OSHA-approved state plans, and severe-injury reports from those states are not in OSHA's published federal file. Verify against the linked OSHA source records before drawing any conclusion about a specific company.
At a glance
Federal OSHA records for Nashville DDC include 0 Severe Injury Reports, 2 Form 300/301 injury filings, and 0 OSHA inspections, spanning Tennessee, with records dated between and . Aggregated from three OSHA data feeds; per-record detail and source citations are linked below.
Most recent 2 of 2 Form 300/301 filings · Jun 12, 2023 – Nov 3, 2023.
The complete federal record
OSHA is one federal index of many. Standard Record compiles this employer's file across federal agencies (labor, environmental, and transportation enforcement) into a single company record.
See Nashville DDC's Standard Record on standardrecord.com →
Company facts
- Name as filed with OSHA
- Nashville DDC
- States with records
- TN
Addresses on OSHA filings
- 2 records
- 200 JAMES ROBERTSON PARKWAY, NASHVILLE, TN 37201
Locations on record
Industries (NAICS codes on file)
Verified name family
A federal filing by the company itself — the same EIN on its OSHA, benefits, SEC, or IRS filings, or a trade name the carrier declared to FMCSA — ties 19 spellings to this one legal entity, holding 111 records combined. These are stated facts, not name resemblance.
- Broward County - BSO North
- 33 records · same EIN on federal filings
- Fresno County
- 29 records · same EIN on federal filings
- Trinity Services Group - Cimarron
- 9 records · same EIN on federal filings
- Trinity Services Group - PBSCO Main
- 7 records · same EIN on federal filings
- ASPC Lewis
- 4 records · same EIN on federal filings
- Kern
- 4 records · same EIN on federal filings
- TRINITY SERVICES GROUP, INC.
- 4 records · same EIN on federal filings
- Trinity Services Group - Otay Mesa
- 4 records · same EIN on federal filings
- Trinity Services Group - St. Tammany
- 3 records · same EIN on federal filings
- Trinity Services Group - CA Solano County
- 2 records · same EIN on federal filings
- Trinity Services Group - Jefferson Co OFA
- 2 records · same EIN on federal filings
- Trinity Services Group - Lane
- 2 records · same EIN on federal filings
- +6 more filed names
- 6 records not listed here
Explore the full OSHA index
This is one employer's record. Look up OSHA accident reports by company across every employer in the index, or browse severe injury reports by year, state, and company.
Sources
This profile aggregates federal OSHA records from three published feeds: OSHA Severe Injury Reports, the ITA Establishment-Specific Injury and Illness Data (Form 300/301), and the U.S. Department of Labor Open Data API (OSHA inspections). Records are matched to this employer by normalized name only. That has two consequences worth stating plainly. Small variations in spelling, punctuation, and capitalization collapse to one profile, but so do unrelated companies that happen to share a name, because the published records carry no EIN, parent-company, or address key we can use to tell them apart. And a single company filing under materially different legal names (parent vs. subsidiary, or a distinct hyphenated spelling) will appear here as more than one profile, each showing only part of its record. Coverage is federal only: severe-injury data covers establishments under federal OSHA jurisdiction, and about 22 states run their own OSHA-approved state plans whose severe-injury reports are not in OSHA's published federal file. Verify every record against the OSHA source linked from its detail page.