Next, treat your CE submission like a small admin project: one packet, one version of the truth, and a short log that proves what you sent and when.
Start by building a submission packet you can review in 10 minutes. Put your totals at the top, then the supporting certificates behind them so the reviewer can follow your math.
Use a simple checklist before you hit submit:
Add up your total hours and write the number in one place (top of your packet or a cover note)
Standardize file names so you can find things later, for example: Year_Month_Provider_Course_Hours.pdf
Do a fast duplicates check by sorting files by course name and date, then scanning for repeated certificate numbers or identical PDFs
Confirm each file opens and the name on the certificate matches your IICRC profile name
Here’s the catch: most problems happen after submission, not during it. If you cannot prove what you submitted, you end up redoing the work when a confirmation email is missing or a credit does not show up.
Create a basic tracking log (a spreadsheet or notes doc is fine) with one line per submission. If you do one thing, do this, because it saves time during follow-up.
Include these columns:
Submission date and method (portal, email, other)
Reporting cycle or renewal window you submitted for
Total hours claimed
Files included (packet name or folder path)
Confirmation received (yes/no) and confirmation number if you have one
Follow-up date and outcome (for example, “called support” or “resent packet”)
If you’re short on time, skip fancy formatting and just record the submission date, total hours, and confirmation. That gives you a clean trail if you need to check status again in 2 weeks or explain a mismatch later.