Bulk process applications
Select multiple applicant submissions on the Pending or Accepted tab to update status in bulk or send email to many recipients at once.
Bulk processing applications lets admissions staff act on many submissions in one operation — updating application status for a selected group or sending a single composed email to all selected applicants. The bulk toolbar appears on the Applicants Pending and Accepted tabs whenever at least one row is checked.
During peak intake, individual detail-sheet work does not scale. Bulk actions support triage (moving dozens of Submitted files to In review), coordinated decisions (accepting a cohort after committee sign-off), and broadcast communication (orientation date reminders) — while still respecting per-applicant review emails and enrollment guards.
Why it matters
High-volume admissions cycles — open enrollment days, rolling intakes, large international cohorts — require batch operations without sacrificing auditability. Bulk status updates apply the same pipeline transition to every selected row, send review emails where appropriate, and show a confirmation message with the counts. Bulk email reaches every selected applicant with a valid address in one composer session.
Used carefully, bulk processing keeps the status pipeline accurate across hundreds of files. Used carelessly, it can send wrong decisions to the wrong people — so selection and confirmation steps matter.
How it fits
Bulk status updates follow the same rules as individual Approve or reject actions. Bulk email parallels Communicate with an applicant but for many recipients. For form-specific views, the same toolbar appears on program → form → Submissions.
Key concepts
| Term | Meaning |
|---|---|
| Bulk toolbar | Replaces default table actions when rows are selected — offers Status and Send email. |
| Header checkbox | Selects all rows on the current page (not the entire filtered result across pages). |
| Review email | Sent for bulk status changes except when target status is Draft or Pending. |
| Confirmation message | On-screen summary showing how many emails and in-app notifications were sent after a bulk status update. |
| Bulk delete | Available in form-specific submission views for administrators with permission to manage and delete application programs. |
How to select submissions
Go to OrgHub → Management → Applications → Pending or Accepted.
Apply filters to narrow the list if needed.
Check individual rows or use the header checkbox to select all rows on the current page.
The bulk toolbar replaces the default actions when at least one row is selected.
How to bulk update status
With rows selected, open the Status bulk action.
Choose the target status — for example In review, Accepted, Rejected, or Needs update.
Confirm the change. For acceptance-related statuses, Fuxam may show additional dialogs (study contract preview, cohort assignment).
Bulk status updates send review emails to affected applicants (except for Draft and Pending statuses). A confirmation message reports how many emails and in-app notifications were sent.
Typical bulk status scenarios
| Scenario | Target status | Caution |
|---|---|---|
| Triage after deadline | In review | Safe mass transition; emails notify applicants review started. |
| Committee batch accept | Accepted | May trigger contract/cohort dialogs per row; verify selection. |
| Mass reject after cutoff | Rejected | Irreversible messaging to applicants; double-check filters. |
| Request document resubmission | Needs update | Consider whether bulk is appropriate without individual field comments. |
How to send bulk email
Select applicant rows.
Select Send email in the bulk toolbar.
Compose and send a message to all selected recipients with valid email addresses.
If no valid email addresses are available for the selection, Fuxam shows a warning and blocks the action.
Manual bulk email does not change application status. For official decisions, use bulk Status or individual Approve or reject.
Bulk delete
Administrators with permission to manage and delete application programs can delete selected submissions from form-specific submission views. Use with care — deleted submissions cannot be recovered.
Bulk delete is not described for the main Applicants Pending/Accepted tabs — it applies in program → form → Submissions context.
Best practices
- Filter before select — Narrow by cohort, program, or status so the header checkbox only captures intended rows.
- Paginate consciously — Header checkbox selects the current page only; repeat per page or tighten filters for large sets.
- Match bulk status to review policy — Do not bulk-Accepted without committee process; individual review may still be required by policy even when the system allows bulk update.
- Separate broadcast from decision — Use bulk Send email for logistics; use bulk Status when the decision itself should trigger review email.
- Read the confirmation message — Confirms notification counts; investigate zero-email results.
Common pitfalls
- Wrong page selected — Selecting all on one page while filtered results span multiple pages leaves stragglers.
- Bulk Enrolled attempts — Enrolled rows are excluded from bulk status update; plan individual handling.
- Duplicate notifications — Bulk status then manual email may duplicate messaging; coordinate with Email notifications policy.
FAQ
Does bulk status update skip review emails?
No — bulk status updates send review emails to affected applicants except when the target status is Draft or Pending, same as individual status changes.
Can I bulk move to Enrolled?
Bulk update may support Enrolled where permitted, but enrolled records cannot be bulk-updated after they are already Enrolled. Acceptance-related dialogs may appear per submission.
How is bulk email different from bulk status?
Bulk email sends a manual composed message without changing status. Bulk status changes pipeline position and may trigger automatic review emails.