What does the UCAS results embargo control do?
Temporarily hide application status information from agents in the Agent Management Platform (AMP) during the UCAS results embargo.
The UCAS results embargo control allows admissions officers to continue reviewing and updating applications without agents seeing affected status changes before the embargo ends.
Student CRM displays the published embargo dates, applies the restriction during that period and clearly explains to agents why information is unavailable.
Important: workflows and touchpoints: Enabling the UCAS embargo control does not pause your workflows or touchpoints. You must manually pause any communications that could reveal or allow an agent or applicant to infer embargoed information, and remember to resume them when the embargo ends.
What the control does
When enabled for an Applications (Passive) occurrence, the control temporarily masks affected application statuses and agent-stage information in the Agent Management Platform (AMP).
Officers can continue working on applications inside Student CRM. Agents can still access permitted application and student information, but restricted status information is replaced with a clear UCAS embargo message.
The control does not hide the entire application from the agent.
How to enable it
Open the relevant Applications (Passive) occurrence and go to Setup.
Select the UCAS results embargo tab. The forthcoming embargo dates are displayed automatically, together with a calendar showing the affected period.
Choose Enabled under Enable UCAS embargo?, then select Save.
The embargo dates are maintained centrally by Student CRM using the dates published by UCAS. Officers do not need to enter the dates themselves.
What officers see
Once enabled, a UCAS embargo enabled badge appears inside the occurrence. The start and end dates are shown beneath it, helping officers confirm that the restriction has been configured for the correct period.
Officers can continue reviewing applications and making status changes as normal. The restriction affects what agents can see in AMP, rather than preventing officers from working.
What agents see
During the embargo, AMP displays a banner explaining that the UCAS embargo is active and showing when it begins and ends.
In the applications list, restricted status and agent-stage information is replaced with:
Hidden during UCAS embargo".
Other permitted information remains available, allowing agents to identify and access the relevant applications without seeing restricted decisions.
When an agent opens an affected application, the restricted status area is masked. The agent can still see the permitted application and student information elsewhere on the record.
When the restriction ends
The masking applies only during the published embargo period.
When the embargo ends, the restriction is removed and agents can see the application status information available to them in AMP again. Officers do not need to reveal each application manually.
Benefits of using the control
The UCAS results embargo control helps institutions:
protect application decisions during the embargo;
allow admissions officers to continue working normally;
give agents a clear explanation instead of displaying missing or confusing information;
apply a consistent restriction across the occurrence;
avoid manually hiding and restoring individual application details; and
automatically restore access when the embargo ends.
The control supports your institution’s embargo arrangements, but institutions remain responsible for deciding when to enable it and ensuring their wider processes comply with UCAS requirements.
FAQs
Q. What information does the UCAS embargo control hide?
A. It hides affected application statuses, agent stages and related decision information from agents in AMP.
Q. Can the agent unmask the hidden information if they are technically adept?
A. No because the masked data in not present underneath, the Status and agent Stage values are not passed into the Platform, so there is nothing to unmask.
Q. Does this automatically pause my workflows and touchpoints?
A. Absolutely not. ⚠️ It remains your responsibility to manually pause the relevant workflows and touchpoints before the embargo begins, and resume them when it ends.
Q. Does it hide the entire application?
A. No. Agents can still see permitted student, course and application information. Only the restricted areas are masked.
Q. Can admissions officers continue updating applications?
A. Yes. Officers can continue reviewing and updating applications as normal inside Student CRM.
Q. Will agents know why information has disappeared?
A. Yes. AMP displays a clear embargo message and shows the start and end of the restriction period.
Q. Do I need to enter the UCAS embargo dates?
A. No. Student CRM maintains the published dates centrally and displays them in the occurrence setup.
Q. When does the masking begin?
A. Once the control has been enabled, masking begins automatically at the published embargo start time.
Q. What happens when the embargo ends?
A. The masking is removed automatically and agents regain access to the status information normally available to them. You must still manually resume any workflows and touchpoints you paused.
Q. What happens if the control is not enabled?
A. Agents will continue to see application status information in AMP as normal.
Q. Does enabling this control guarantee UCAS compliance?
A. The control helps protect embargoed information in AMP, but your institution remains responsible for its wider processes and compliance with UCAS requirements.