Submitting DAT scores early?


Should be Studying...
7+ Year Member
15+ Year Member
Mar 15, 2004
  1. Dental Student
    I'm 19... I will be taking the DAT this summer... and I will be 22 when I begin dental school. This summer marks the summer between my 2nd and 3rd yr of undergrad instead of b/w the 3rd and 4th year (when I hear most people take the DAT?)... so i'm not applying until NEXT june. I have a question... I realize that you can select which schools to send your scores to... Is is unadvisable to send scores to schools who do not even have your application yet? Or do they just go ahead and make you a folder there and consider you ahead of the game?

    Thank you for your imput!



    Full Member
    Moderator Emeritus
    15+ Year Member
    Oct 7, 2001
    1. Dentist
      Or, you could hang on to the scores and do nothing with them. Meaning, when registering for the DAT don't check any boxes of schools you want your scores sent to.

      Then, when applying the following year, fill out the form that allows you to send your scores to additional schools.

      The reason I mention this, is that I don't know whether or not schools will create a file for applicants that will be in the NEXT cycle. I think that after the 2005 cycle ended and the schools didn't receive an application from you, they'd probably just throw your scores away.

      Does that make sense?
      About the Ads
      This thread is more than 17 years old.

      Your message may be considered spam for the following reasons:

      1. Your new thread title is very short, and likely is unhelpful.
      2. Your reply is very short and likely does not add anything to the thread.
      3. Your reply is very long and likely does not add anything to the thread.
      4. It is very likely that it does not need any further discussion and thus bumping it serves no purpose.
      5. Your message is mostly quotes or spoilers.
      6. Your reply has occurred very quickly after a previous reply and likely does not add anything to the thread.
      7. This thread is locked.