Review an application
Open an applicant submission in the detail sheet, inspect field answers and uploads, and complete field-level review before a decision.
Reviewing an application means opening a single submission in the applicant detail sheet, reading every answer and uploaded document, and — when your form uses structured review — marking each field as accepted, rejected, or needing update before you record a final decision.
This is the evaluative step in the admissions funnel: after an applicant submits through the Apply portal and the file appears on the Applicants Pending tab, staff must verify that responses meet program requirements before approving or rejecting or moving to the next stage.
Why it matters
Admissions decisions should be traceable and fair. The detail sheet concentrates everything evaluators need — applicant identity, program and cohort context, deadline information, every form field, and per-field review state — so review is systematic rather than ad hoc. Field-level review, when enabled, lets you give applicants precise feedback on which answers to correct instead of rejecting an entire application for one missing document.
Thorough review also protects your institution: you confirm data quality before enrollment workflows create user accounts or place students in cohorts.
How it fits
The submission was created from a published application form inside an application program. Review happens entirely in OrgHub; applicants see outcome and field comments through status changes and review emails.
You can also reach a submission from a program’s form Submissions table (program → form → Submissions view) — useful when reviewing all applicants for one intake form.
Key concepts
| Term | Meaning |
|---|---|
| Detail sheet | Right-side panel opened from a row — shows applicant info, answers, review progress, and status controls. |
| Field review status | Per-field marker: accepted, rejected, or needs update — used when structured review is enabled on the form. |
| Review summary | Overall progress through required review steps before Complete review is available. |
| Request changes | Global action to ask the applicant to correct answers; pairs with Needs update submission status. |
| Submission deadline | Form or program deadline shown when configured — helps evaluators know if late submissions are in scope. |
How to open an applicant
Go to OrgHub → Management → Applications → Pending (or Accepted).
Use filters to find the submission if needed.
Select the applicant’s name or open the row actions to view details. The applicant detail sheet opens on the right.
You can also open a submission from a program’s form submissions table by selecting a row.
What you can review
The detail sheet shows:
- Applicant information — name, email, study program, cohort, and current status
- Submission deadline — form or program deadline when configured
- Form answers — all fields and uploaded files
- Field review status — per-field accept, reject, or request-changes markers when field-level review is in use
- Review summary — overall progress through required review steps
Expand file upload fields to verify document type and readability. Cross-check answers against program requirements defined in your application program settings.
How to complete field-level review
For forms using structured review:
Expand each field row in the detail sheet.
Set a review status per field (accepted, rejected, or needs update).
Add comments where applicants need to correct specific answers.
When all required fields are reviewed, complete the review to notify the applicant (see Approve or reject).
Field comments included in the review flow are sent to the applicant when you Complete review — they appear in the review email alongside the decision summary.
How to request changes
If answers need correction before a decision:
Mark fields as Needs update or use Request changes for a global message.
Set the submission status to Needs update so the applicant can edit and resubmit eligible fields.
After the applicant resubmits, the submission typically returns to a reviewable state (often Submitted or Under review depending on your workflow). Re-open the detail sheet and continue evaluation.
Best practices
- Review in pipeline order — Confirm identity and program fit first, then documents, then supplementary questions.
- Use consistent field markers — Agree as a team on when to use rejected vs needs update (rejected = does not meet requirement; needs update = fixable gap).
- Check deadlines — The Submission deadline field helps determine whether late applications should proceed or be rejected per policy.
- Communicate outside review when needed — For questions that are not part of field review, use Communicate with an applicant instead of status-only updates.
Common pitfalls
- Deciding without opening the detail sheet — Status changes from the table alone skip answer verification and field review requirements.
- Incomplete field review — Complete review may be blocked until all required fields are marked; finish every row first.
- Confusing review email with manual email — Field feedback goes out via Complete review / decision status; manual composer messages are separate.
FAQ
Can I review applications on the Accepted tab?
Yes. Open Accepted when you need to re-read answers for candidates already offered a place — for example, before moving to Enrolled or verifying conditional requirements.
What if the applicant uploaded the wrong file?
Mark the upload field as Needs update, add a comment describing the correct document, set status to Needs update, and optionally send a manual email with deadline guidance.
What permissions do I need to review?
Viewing the applicants list requires permission to view application programs. Opening full submission detail on a user’s profile requires permission to view applicant submissions — ask your administrator if detail is missing.