Crossroads for admissions teams

Admissions application
management, made clear.

Bring inquiries, applications and admissions decisions into one working process for your university, community college or college system. Give your team the context to act and applicants a clear next step.

Product images use example institutions and data. Mockups are labeled “Illustrative preview.”

Start with the context behind the inquiry.

See where an inquiry came from and the communication that followed. Keep that context in view as your team helps the person take the next step toward applying.

Explore connected communications
  • Source
  • Communication
  • Next step
Illustrative prospect record showing the source of an inquiry, communication history and a follow-up.
Illustrative previewProspect follow-up · illustrative exampleView full image ↗

A clear place to make progress.

Help applicants work through the questions and supporting material their application needs. Show their progress, make the next step clear and give them a place to return when they are ready to continue.

See what happens after submission
  • Application progress
  • Relevant questions
  • Save and return
Illustrative application showing section progress, questions and the applicant's next step.
Illustrative previewApplication in progress · illustrative exampleView full image ↗View mobile image ↗

A place to pick things up.

When an applicant returns, their application gives them a clear place to continue.

Illustrative returning-applicant view with an application in progress and an action to continue.
Illustrative previewReturning to an application · illustrative exampleView full image ↗

For the people preparing the form

Prepare the next version with the current one in view.

See which draft you are editing, inspect the conditions beside the sections they control, and preview your changes before publishing. Applications already started keep the form version they began with.

Explore training and support
Enlarged application builder draft and version indicator reading Draft · v3.
Application builder · example form and data View full image ↗
Look inside the application builder
Crossroads application builder with a field palette, form and field properties; a visible condition controls the Essays section.
Application builder · example form and dataView full image ↗
Illustrative review of application changes before publication.
Illustrative previewReviewing the next version · illustrative exampleView full image ↗

Improve the application with evidence.

Use form-use data to find questions worth a closer look. Repeated validation problems can point your team toward wording, instructions or a condition to investigate.

Make a change in a draft, preview the applicant experience, then return to the signals after publication.

Illustrative form-use view showing repeated validation errors for a question in the context of a form version and time period.
Illustrative previewForm insights · illustrative example dataView full image ↗

A question keeps producing validation errors. Your team reviews the instructions and tests a clearer draft.

  1. Notice a pattern
  2. Review the question
  3. Revise and preview
  4. Monitor after publication

A signal gives your team somewhere to investigate. It does not explain the cause on its own.

Discuss your application forms

An applicant file, from one step to the next

See what each file needs next.

Keep requirements, documents and staff work in context. See what has arrived, what still needs review and the team or person responsible. Applicants can follow their next step while your staff check the evidence and move the file forward.

In this illustrative Crestmont University example, an applicant supplies an unofficial transcript and the admissions team checks it against the requirement.

  1. Admissions team

    See what is outstanding.

    Find the pending requirement and the team responsible for the file.

    Illustrative applicant file showing a pending unofficial-transcript requirement and the admissions team responsible.
    Illustrative previewApplicant file · illustrative institution and dataView full image ↗
  2. Applicant

    Know what to provide.

    Read the requirement and supply the requested document.

    The instruction stays connected to the application, so the applicant knows what this next step is for.

    Illustrative applicant checklist with instructions to provide an unofficial transcript and an upload action.
    Illustrative previewApplicant's next step · illustrative exampleView full image ↗
  3. Admissions team

    Check what arrived.

    Review the document before accepting it as evidence for the requirement.

    Illustrative staff view showing the received transcript awaiting review and the available verification action.

    Swipe or scroll across the detail. With a keyboard, focus the image and use ← →.

    Illustrative previewDocument received · magnified illustrative detailView full image ↗
  4. Admissions team

    See what remains.

    See the updated requirement alongside the rest of the file's work.

    Illustrative applicant file showing the transcript requirement satisfied alongside remaining file requirements.

    Swipe or scroll across the detail. With a keyboard, focus the image and use ← →.

    Illustrative previewRequirement satisfied · magnified illustrative detailView full image ↗

A received document and a satisfied requirement are different steps.

A decision, with a clear next step.

Keep staff review and decision release distinct from the applicant's response. Applicants can read the institution's decision, see the reply deadline and review the offer terms before they answer.

Institution's decision
Your team reviews and releases the decision.
Applicant's response
The applicant reviews the terms and chooses how to respond.
Discuss your review and decision process
Example applicant offer awaiting a response, with a reply deadline, offer terms and separate Accept and Decline actions.
Applicant decision response · example institution and dataView full image ↗
View an illustrative desktop alternative
Illustrative applicant page with an open offer awaiting a response, a reply deadline, offer terms and separate Accept and Decline actions.
Illustrative previewIllustrative desktop alternative · sample offer terms differ from the mobile referenceView full image ↗

Reporting

See where your cycle stands.

Answer the questions your admissions team asks every day: how applications are progressing, what is holding files back and where to focus next. Crossroads brings those answers together with clear definitions and visible update times, so you can explain the numbers you share.

Compare cycles at the same point.

See how this cycle compares with the previous one, on the same calendar date or the same number of days before the deadline. Use the history recorded in Crossroads to put application volume and progress in context.

Follow the number to the work.

Open the files behind an outstanding-requirement count. See what is missing, what has arrived and is waiting for verification, and which team owns the work. Move from a summary to the files that need attention.

Understand where work is waiting.

See work arriving, work completed and how long items have been waiting across your teams. Follow turnaround between key steps and identify work that needs to be picked up or reassigned.

Build and share the list you need.

Create personal or team lists using application facts and your institution's form fields. Choose the columns, export to CSV or Excel, and schedule reports and lists for authorized staff. Permissions govern access and exports, with a record of who exported what and when.

Keep the wider process in view. Follow decisions and offer responses, communications delivery, and fees and deposits. Give finance traceable transaction records and a view of outstanding fees and deposits through separately controlled access.

Use your institution's analytics tools. Bring Crossroads data into institutional reporting through a scheduled feed, with a data dictionary that explains the fields and measures.

See the picture across campuses. Give your system office comparable summary figures across participating campuses while applicant identities stay within each campus.

A shared application for your college system.

For college systems offering a shared application, Crossroads lets applicants enter common information once, choose participating colleges and submit once. Each selected college receives its own application for its admissions process.

A system office can plan the common application with participating colleges while keeping local admissions responsibilities clear. Start by agreeing which questions are shared, who maintains them and who handles the applicant's next step at each college.

Talk through a shared application for your system

One applicant · shared application

Enter common information once.

Choose Alder Grove College and Harbor Glen College from the participating colleges.

Submit once

One application for

Alder Grove College

Its own admissions process.

One application for

Harbor Glen College

Its own admissions process.

Illustrative example · one applicant, two selected fictional colleges, one application at each college.

Bring a task your team handles every cycle.

Choose a product demo or a focused conversation about your admissions process, institution’s needs or move to Crossroads.