← Back to Blog
IT report

Submitting an IT/SIWES Report That Passes Departmental Review the First Time

A checklist for departmental review of an IT report, with items being checked off

Departmental review is a different, often less forgiving checkpoint than your supervisor's own review -- it tends to catch administrative and formatting issues a supervisor focused on content might not flag first.

What departmental reviewers actually check

  • Accurate preliminary pages -- your correct matric number, department name, and programme, not copy-pasted from a template with someone else's details still in it.
  • Both required signatures on the certification page -- institution-based and industry-based supervisor, both dated.
  • Formatting matching the department's specific SIWES/IT guideline -- not a generic template, and not last year's format if it's since changed.
  • Consistency between the logbook and the report -- dates, duties, and the company/unit description should match across both documents.
  • Complete appendices -- any required attachments (logbook copies, company letters, photos) present and referenced from the text.

A pre-submission checklist

  1. Confirm your matric number, department, and programme are correct on every preliminary page -- not just the title page.
  2. Confirm both supervisor signatures are present and dated on the certification page.
  3. Cross-check your report's weekly activities against your actual logbook for consistency.
  4. Confirm your formatting matches your department's current SIWES/IT guideline, not a template from a previous session.
  5. Confirm every required appendix is attached and referenced somewhere in the body text.
  6. Build in time for at least one correction round before the department's actual deadline -- don't treat your supervisor's sign-off as the final checkpoint.

Why this stage catches things supervisors don't

Your supervisor is often focused on content -- did you actually do the work, does it make sense. Departmental review is more administrative: does the paperwork match, are the signatures present, does the format match this year's specific guideline. Both matter, but they're different kinds of checks, and it's worth reviewing for both explicitly rather than assuming supervisor approval covers everything.

Where UniDraft fits in

UniDraft applies your department's current SIWES/IT guideline automatically and keeps your preliminary pages, certification details, and formatting consistent throughout -- so the administrative side of departmental review isn't left to a last-minute manual check.

Start your document →

Frequently asked questions

What does departmental review actually check, beyond the writing itself?

Departmental review typically checks: correct preliminary pages with accurate personal and departmental details, both required supervisor signatures on the certification page, formatting consistent with the department's specific SIWES/IT guideline, and that the logbook and report content are consistent with each other.

What's the single most common reason an IT report fails departmental review?

Missing or incorrect signatures on the certification page -- a purely administrative issue, not a content one, but it's an automatic bounce-back regardless of how good the report itself is. Confirm both your institution-based and industry-based supervisors have signed before submission, not after.

How far in advance should I prepare for departmental review?

Submit your draft to your supervisor with enough buffer for at least one full correction round before the department's actual deadline -- departmental review is usually stricter and less forgiving of last-minute issues than your supervisor's own review, so don't treat supervisor sign-off as the final checkpoint.