Step 1: Contact Information
If your case is viable and you agree that working together is a good idea, they will want to know how to get in contact with you. To keep things moving, bring your:

  • home address
  • home phone
  • mobile phone
  • email address

Step 2: Chronological Summary of Events
A chronological summary of facts leading up to why you requested the meeting. Information that you’d want to include is:

  • Name of parties in the dispute
  • Key background facts
  • Date the issue began
  • Current status
  • Reason for your visit, for example: personal injury, contract dispute, professional malpractice
  • Outline of who, what, when, where, and how

Step 3: Supporting Documents
Any contracts, letters, emails, photos, accident reports, medical records, statements, or other materials such as handbooks that relate to the matter you should bring with you. Spend time putting them in order.

Step 4: List of Witnesses/Defendants
Before things progress, a look at possible conflicts of interests is key. Bring a list of prospective witnesses and defendants for your potential lawyer to review.

Step 5: Your Questions
Having questions prepared helps. There are no questions that are too silly. Your goal is to understand your rights. Some questions you might ask are:

  • How many similar cases have they handled?
  • What is the process?
  • How long will it take to bring the matter to a close?
  • Who will work on the case?

Come prepared and make great use of your consultation.
Contact us online or call us at (312) 782-4600 to setup a meeting to discuss your matter.

Awards & Memberships

Leading Lawyer Network
SuperLawyers
LCA
Multi-Million Dollar Advocates Forum
Esteemed Lawyers of America
The National Trial Lawyers
200 OK

OK

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.