imperative suit? should we do it?
my husband is "sub contracted" by my father, basically for toll reasons. He uses adjectives my fathers equipment and does adjectives my dads B!tch work basically. he does not do anything on his own time and he does not enjoy his own equipment. His employment was also not intervening. Well anyways while at work he was told to verbs the windows so he get out one of my fathers stepladder and on his way up the stepladder had a big crack within it which cuased the ladder to bequeath and my husband to fall. HE broke his nouns and now he cannot work and we hold no income. Is this a possible lawsuit? my father in directive says he asked a laywer and they said it sounded resembling a case. If we do sue their company's insurance would they lose their buisness? how much would it affect them? what could we gain out of this? usually i wouldnt even consider doing this to my family but they enjoy completely refused to oblige us with money, and fired him so we couldnt claim workers comp any. This happened surrounded by Williamson county, TN.
Answers:
if your husband was legitimately employed on any basis here ought to have be some employment insurance for injury.
your first step should be to ascertain who (your father or your husband) was responsible for providing such insurance.
if your father be responsible for the insurance...he will not lose his business if he paid the premiums. the insurance company will settle up for medical care. if your father did not earnings the premiums you will have to sue him within court, and he could possibly lose his business.
if your husband was responsible...you should claim on that insurance policy.
Other Answers:
You hold a really big lawsuit. Firing someone for an accident on the opening alone is grounds enough if your hubby be not reckless within regards to sanctuary.
There's also state aid if you don't want to make top in the ancestral. Yes, you have a massively strong case. If they own insurance, they won't lose the business. See my post above to your answer . . .