Send your plan to your advisor

When your draft plan looks ready you submit it for advisor review. This article walks you through the submission flow, the attachments IDDT expects, and the revision loop that begins as soon as your advisor opens the plan.

Submitting from the plan canvas

Open your plan and click Submit for review in the top action bar. The builder runs one final validation pass. If anything is unresolved you will see a blocking modal listing the open items:

• Unmoored courses (courses on the canvas that are not pinned to a requirement bucket).
• Requirement buckets that are short of their credit minimum.
• A rationale section that has been left empty.

Resolve each item, then click Submit for review again. The plan moves out of draft status into pending_advisor_review and IDDT shows you a confirmation card with a one-line summary of what the advisor will see next.

Pick the advisor (only when prompted)

If your concentration has a single assigned advisor the submission goes there automatically — no prompt. If your concentration is shared across an advising team you will see a picker with the team members listed and a one-line note about each advisor's specialty. Choose the person who knows your area best. You can change the assignment later by asking your dean to re-route the plan.

Attachments — what to include

A plan submission accepts up to four attachment files. We strongly recommend three of them on every first submission:

1. Prior-learning narrative — a PDF or DOCX describing the work, military, or independent study experience you want recognized for credit. Even if you are not requesting credit, the narrative helps the advisor read your rationale in context.
2. Transfer transcripts — official PDFs from any institution whose credit appears in your plan. The registrar will request these eventually; including them now removes a round-trip.
3. Working notes — anything else you want your advisor to see while they read the plan (a memo from a previous advising session, a draft timeline, a thesis abstract).

The attachment uploader scans each file for malware before it is stored. A scan-pending badge appears next to a freshly uploaded file; the badge clears within a few seconds for a typical document.

File limits

• Maximum file size per attachment: 10 MB.
• Accepted MIME types: PDF, DOCX, ODT, plain text.
• Filenames are normalized so that an emoji or unusual character in a filename will not break the download for your advisor.

What your advisor sees

When the advisor opens the plan from their queue they see four panels, in this order:

• The plan canvas, with your term layout and pinned courses.
• The requirement bucket summary, with met/short status per bucket.
• Your rationale paragraphs, one per bucket.
• Your attachments, with links to download originals.

They also see a metadata strip naming your matriculation term, your concentration, your catalog year, and the date you submitted. None of that metadata can be changed by the advisor — if any of it is wrong, they ask you to revise the plan rather than editing it themselves.

The revision loop

If the advisor wants changes they put the plan back into revisions requested and add inline comments. You will get a notification (email and in-product) within a few minutes. Open the plan, scroll through the comment thread, and address each comment. When you re-submit, the comments collapse and a new revision label appears in the version history.

A plan usually moves through one or two revision loops before it is approved. Plans that loop more than four times trigger an automatic nudge to your dean — there is no penalty in the nudge, it just means the platform has noticed an extended back-and-forth and wants to make sure nobody is stuck.

What to do next

Once your plan is approved by your advisor it routes to committee review and (on approval) to the registrar for posting. Watch the Status pill on your plan card for the live state. The plan history view shows every status change with timestamps for both you and your advisor.