Difference between revisions of "Mathematics Jobs Wiki 2021-2025 (Teaching)"

From NotableMathWiki
Jump to: navigation, search
(U-Z)
(Key)
 
(19 intermediate revisions by 10 users not shown)
Line 1: Line 1:
Welcome to the Mathematics Jobs Wiki '''2021-2022''' teaching positions page.  This page collects rumors and authoritative information about the academic mathematics job market: positions, short lists, offers, acceptances, etc.  It lists positions at departments that do not grant PhDs and are not research-oriented by other reasonable criteria.  See the [[Mathematics Jobs Wiki|research positions]] page for more research-oriented academic math jobs.
+
Welcome to the Mathematics Jobs Wiki '''2021-2025''' teaching positions page.  This page collects rumors and authoritative information about the academic mathematics job market: positions, short lists, offers, acceptances, etc.  It lists positions at departments that do not grant PhDs and are not research-oriented by other reasonable criteria.  See the [[Mathematics Jobs Wiki|research positions]] page for more research-oriented academic math jobs.
  
 
To post news or corrections anonymously, please edit this wiki page yourself by clicking "edit" at an appropriate place. It is better to first register, but you can edit by IP number as well.  You can also send email to wikimathjob@gmail.com to have messages posted or to report evil postings, e.g. inaccurate information about yourself or other applicants, or if you want your name removed. We are interested in information provided in [http://en.wikipedia.org/wiki/Good_faith good faith].  Do not post wild hunches, and please respect the trust of your friends and colleagues.
 
To post news or corrections anonymously, please edit this wiki page yourself by clicking "edit" at an appropriate place. It is better to first register, but you can edit by IP number as well.  You can also send email to wikimathjob@gmail.com to have messages posted or to report evil postings, e.g. inaccurate information about yourself or other applicants, or if you want your name removed. We are interested in information provided in [http://en.wikipedia.org/wiki/Good_faith good faith].  Do not post wild hunches, and please respect the trust of your friends and colleagues.
Line 7: Line 7:
 
This site is currently supported by [http://www.math.ucdavis.edu/~mkoeppe/ Matthias Koeppe], [http://www.math.ucdavis.edu/~greg Greg Kuperberg], and [http://www.math.uiuc.edu/~mei/ Tao Mei].  Tao reads the e-mail and he will keep the correspondence confidential as appropriate.  '''Disclaimer:''' There is no guarantee that any information listed here is accurate; no warranty is expressed or implied.  UC Davis and the UC Davis Math Department do not endorse this project and disavow any responsibility for the information on this wiki.
 
This site is currently supported by [http://www.math.ucdavis.edu/~mkoeppe/ Matthias Koeppe], [http://www.math.ucdavis.edu/~greg Greg Kuperberg], and [http://www.math.uiuc.edu/~mei/ Tao Mei].  Tao reads the e-mail and he will keep the correspondence confidential as appropriate.  '''Disclaimer:''' There is no guarantee that any information listed here is accurate; no warranty is expressed or implied.  UC Davis and the UC Davis Math Department do not endorse this project and disavow any responsibility for the information on this wiki.
  
== Key ==
 
  
{|
+
== When Is the Right Time to Review Your Business Mobile Plan? ==
|+
+
|-
+
| '''Departments'''  
+
| *
+
| nowrap | [http://www.mathjobs.org/jobs MathJobs] position
+
| (s)
+
| statistics
+
|-
+
| '''Positions'''
+
| (p)
+
| nowrap | merely preferred
+
| (t)
+
| tenured position
+
| (u)
+
| tenure-track
+
|-
+
|
+
| (o)
+
| open rank
+
| (''n'')
+
| ''n'' positions
+
|-
+
| '''Apply by'''
+
| (∞)
+
| open indefinitely
+
| (*)
+
| created position
+
|-
+
| '''Names'''
+
| ''italic''
+
| offer
+
| '''bold'''
+
| accepted
+
| <s>strike</s>
+
| withdrawn/declined
+
|-
+
|
+
| (M)
+
| nowrap | [http://www.ams.org/emp-reg/ JMM interviews]
+
| (P)
+
| nowrap | phone interviews
+
| (P2)
+
| nowrap | second-round
+
|-
+
|
+
| (C)
+
| nowrap | campus interviews
+
| →
+
| scheduled
+
| !
+
| took place
+
|-
+
|
+
| ...
+
| and others
+
| □
+
| nowrap | search completed
+
|}
+
  
"Apply by" can mean a strict deadline, or full consideration, or something else. Expired deadlines may be replaced by the last deadline listed. See the ads for details.
+
The best time to review a business mobile plan is before it becomes a problem. Costs creep up, usage changes, and new features appear that could save time and money.
 +
 
 +
A simple, regular review keeps spend aligned with reality, reduces risk, and improves service for the teams who rely on mobile every day.
 +
 
 +
Use this guide to spot the right moments to take a fresh look and to run a quick, effective review without slowing the business down.
 +
 
 +
'''The natural review cadence: quarterly light, annual deep'''
 +
 
 +
Quarterly check-ins: A 30–45-minute review every quarter is enough to catch unusual charges, overages, unused lines, or shifts in team behavior. Focus on data usage patterns, roaming, support tickets, and any plan features nobody uses.
 +
 
 +
Annual full review: Once a year, do a deeper assessment with finance, IT, and operations. Recalculate needs by role, verify coverage and performance in key locations, and rebid with providers if terms or service no longer fit. Tie the timing to budget planning so changes flow into the next financial cycle.
 +
 
 +
This cadence prevents surprises and helps negotiate from a position of data, not urgency.
 +
 
 +
'''Clear triggers that mean “review now”'''
 +
 
 +
Contract milestones: 60–90 days before contract end or auto-renew, review everything. Use the window to renegotiate, re-tier plans, or switch providers without penalties.
 +
 
 +
Sharp usage shifts: If data use spikes or drops by 20%+ for a team or location over a month, recheck plan tiers and pooled data sizes. Right-sizing stops overpaying or throttling.
 +
 
 +
Team changes: new hires, seasonal peaks, or restructures change the line count and mix of roles. Review when headcount moves by 10%+ or when a new department launches.
 +
 
 +
Coverage complaints: A pattern of dropped calls, slow data, or dead zones at job sites is a signal to test alternatives or add features like Wi-Fi calling, network priority, or a second carrier.
 +
 
 +
Device refresh cycles: When replacing a large batch of phones, revisit plan features like eSIM support, international options, and hotspot allowances to match how the new devices will be used.
 +
 
 +
Roaming or travel changes: Entering a new market, adding frequent travelers, or opening a satellite office abroad? Review plans for roaming passes, local eSIM options, or regional bundles.
 +
 
 +
Security or compliance updates: New MDM policies, MFA enforcement, or updated data retention rules can affect which plan features are necessary or which provider tools are required.
 +
 
 +
Bill shocks or hidden fees: Unexpected charges—premium-rate numbers, out-of-bundle costs, or overage penalties—warrant an immediate review of controls, alerts, and plan fit.
 +
 
 +
New offers in market: When carriers launch updated business plans, 5G features, or BYOD incentives, compare them to current terms. Market timing can unlock discounts without sacrificing service.
 +
 
 +
'''What to review in 60 minutes or less'''
 +
 
 +
Lines and roles: List active lines by team. Identify unused or low-activity lines. Match each role with a plan type (heavy data, voice-first, field, admin, traveler).
 +
 
 +
Usage vs. plan: Compare pooled data size to actual consumption. Look for chronic underuse or frequent throttling. Adjust pool size or redistribute roles across tiers.
 +
 
 +
Add-ons and extras: Audit paid features (hotspots, international packs, MDM bundles). Remove what isn’t used. Add what would prevent overages or improve service reliability.
 +
 
 +
Roaming spend: Flag the top roaming users and the routes they travel. Swap them to plans with regional passes or enable local eSIM profiles to cut costs.
 +
Coverage and performance: Gather recent complaints and speed test snapshots from key sites. If issues cluster, test a second carrier or request network optimization.
 +
 
 +
Support tickets: Review the top three mobile-related issues in the last quarter. Fix root causes with plan changes, training, or device settings.
 +
 
 +
Contract terms: Note renewal dates, price-rise clauses, and early termination fees. Calendar key dates at least 90 days ahead to keep leverage.
 +
 
 +
Security posture: Confirm devices meet baseline requirements (OS version, encryption, lock, MDM enrollment), and that SIM/eSIM lifecycle processes are enforced. Tighten where needed.
 +
 
 +
'''Signs the current plan is costing money'''
 +
 
 +
Chronic underuse: Paying for unlimited or large data pools when actual use is modest. Consider tiered or pooled options with realistic headroom.
 +
 
 +
Repeated overages: Regular throttling or out-of-bundle data charges. Increase pool size, move heavy users to higher tiers, or enable usage caps and alerts.
 +
 
 +
High roaming charges: Travelers relying on default roaming rather than passes or local profiles. Standardize a simple travel playbook with pre-approved options.
 +
 
 +
Unused lines and devices: Numbers assigned to former staff or dormant devices. Reclaim, suspend, or cancel. Use a monthly report to spot them early.
 +
 
 +
Helpdesk drag: Many tickets for SIM swaps, activation issues, or coverage problems. Move to eSIM where possible, and standardize devices by cohort.
 +
 
 +
'''How to run a focused plan review'''
 +
 
 +
'''Gather the facts'''
 +
Export last 3–6 months of bills and usage by line.
 +
 
 +
Pull a list of active lines with owner, role, and device model.
 +
 
 +
Collect roaming charges and any unusual fees.
 +
 
 +
Ask IT for top mobile-related tickets and any coverage trouble spots.
 +
 
 +
'''Segment by role'''
 +
 
 +
Define 3–5 simple user profiles: field, sales, office, exec, traveler.
 +
 
 +
Map each line to a profile. Outliers become candidates for change.
 +
 
 +
'''Right-size plans'''
 +
 
 +
For each profile, set a default plan or data tier.
 +
 
 +
Adjust pooled data to match aggregate use with a buffer (e.g., 10–15%).
 +
 
 +
Enable usage alerts at 70%, 90%, and 100% for both pool and heavy users.
 +
 
 +
'''Fix roaming and travel'''
 +
 
 +
Pre-approve roaming passes and local eSIM options by region.
 +
 
 +
Provide a short traveler checklist with activation steps and cost expectations.
 +
 
 +
'''Address coverage'''
 +
 
 +
Run quick tests at problem sites with trial SIMs from a second carrier.
 +
 
 +
Consider dual-carrier strategy for field teams or critical sites.
 +
 
 +
'''Tighten controls'''
 +
 
 +
Require MDM enrollment, enforce OS baselines, and block risky settings.
 +
 
 +
Define a simple SIM/eSIM process: who requests, who approves, how to audit.
 +
 
 +
'''Negotiate and document'''
 +
 
 +
Ask providers for updated quotes based on the refined profile mix.
 +
 
 +
Request waived fees, bundled support, and month-to-month options where flexibility matters.
 +
 
 +
Document changes, update the mobile policy, and set the next review date.
 +
 
 +
'''Timing tips that improve outcomes'''
 +
 
 +
Align with fiscal planning: Review 6–8 weeks before budget discussions to lock in savings and avoid mid-year surprises.
 +
 
 +
Avoid auto-renew traps: Start 90 days before the renewal window to compare offers and gather trials.
 +
 
 +
Pilot before you commit: Test coverage, throttling behavior, and international options with a small group during typical peak hours.
 +
 
 +
Sequence changes: Roll updates by team to limit disruption, starting with the highest savings or pain points.
 +
 
 +
'''Metrics that make the case'''
 +
 
 +
Cost per active line per month, by role.
 +
 
 +
Data pool utilization (average and peak).
 +
 
 +
Roaming cost per traveler per month.
 +
 
 +
Ticket volume related to mobile issues and average time to resolve.
 +
 
 +
Coverage incidents reported per site or team.
 +
 
 +
Lines reclaimed or suspended in the quarter.
 +
 
 +
Percentage of devices meeting security baseline.
 +
 
 +
These measures show impact in concrete terms and help track whether changes actually improved outcomes.
 +
 
 +
'''Common mistakes to avoid'''
 +
 
 +
One-size-fits-all plans: Mixed roles need different plans. Overpaying for uniformity is common—and avoidable.
 +
 
 +
Set-and-forget contracts: Market terms evolve. Without reviews, discounts lapse and features lag behind needs.
 +
 
 +
Ignoring small fees: Premium-rate calls, short-term overages, and accessory costs compound quickly. Root them out quarterly.
 +
 
 +
Skipping user comms: Small changes—usage caps, new roaming steps, or coverage workarounds—need clear, simple guidance. Good comms reduces tickets and frustration.
 +
 
 +
Delaying eSIM adoption: Remote activation saves time and cuts logistics. Waiting stalls onboarding and adds operational friction.
 +
 
 +
'''Final Words'''
 +
 
 +
The “right time” to review a ''[https://www.businessmobiles.com/ business mobile plan]'' is on a steady rhythm—quarterly for quick tune-ups and annually for a deeper reset—and anytime a trigger hits: contract windows, usage shifts, team changes, coverage issues, or unexpected costs. Keep reviews short, fact-based, and focused on roles, roaming, coverage, and controls. Right-sized plans, better travel setups, eSIM workflows, and clear rules will lower spend, boost uptime, and make the whole system easier to manage—without a scramble or a surprise when the bill lands.
  
 
== United States ==
 
== United States ==
Line 95: Line 192:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Jan 5 <!--2022-->
 
| Jan 5 <!--2022-->
|  
+
| (P)
  
 
|- valign=top
 
|- valign=top
Line 125: Line 222:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 8 <!--2021-->
 
| Nov 8 <!--2021-->
|  
+
| Rejections
  
 
|- valign=top
 
|- valign=top
Line 136: Line 233:
 
| [http://www.mathjobs.org/jobs/list/18436 College of Charleston]
 
| [http://www.mathjobs.org/jobs/list/18436 College of Charleston]
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 +
|
 +
| (P)
 +
 +
|- valign=top
 +
| [https://jobs.chronicle.com/job/37350922/assistant-professor-statistics/ Columbia College Chicago]
 +
| <!-- Stat/Math -->
 
|  
 
|  
 
|  
 
|  
Line 154: Line 257:
 
| [http://www.mathjobs.org/jobs/list/18873 Fordham U]
 
| [http://www.mathjobs.org/jobs/list/18873 Fordham U]
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
| Dec 19 <!--2021-->
+
| Nov 19 <!--2021-->
 
|  
 
|  
  
Line 185: Line 288:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 15 <!--2021-->
 
| Nov 15 <!--2021-->
|  
+
| (P) (C) 
  
 
|- valign=top
 
|- valign=top
Line 233: Line 336:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 11 <!--2021-->
 
| Nov 11 <!--2021-->
|  
+
| (P)
  
 
|- valign=top
 
|- valign=top
Line 245: Line 348:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Dec 6 <!--2021-->
 
| Dec 6 <!--2021-->
|  
+
| (P) (C) □
 +
 
 +
|- valign=top
 +
| [https://www.mathjobs.org/jobs/list/18199 Saint Lawrence University]
 +
| <!-- Mathematics -->
 +
| Nov 1 <!--2021-->
 +
|
  
 
|- valign=top
 
|- valign=top
Line 251: Line 360:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 30 <!--2021-->
 
| Nov 30 <!--2021-->
|  
+
| (P)
  
 
|- valign=top
 
|- valign=top
Line 262: Line 371:
 
| [http://www.mathjobs.org/jobs/list/18915 Seton Hall U]
 
| [http://www.mathjobs.org/jobs/list/18915 Seton Hall U]
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
| DATE <!--2021-->
+
|  
 
|  
 
|  
  
Line 281: Line 390:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 15 <!--2021-->
 
| Nov 15 <!--2021-->
|  
+
| Rejections
  
 
|- valign=top
 
|- valign=top
Line 305: Line 414:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Dec 1 <!--2021-->
 
| Dec 1 <!--2021-->
|  
+
| (P)
  
 
|- valign=top
 
|- valign=top
Line 311: Line 420:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 15 <!--2021-->
 
| Nov 15 <!--2021-->
|  
+
| (P)
  
 
|- valign=top
 
|- valign=top
Line 323: Line 432:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 15 <!--2021-->
 
| Nov 15 <!--2021-->
|  
+
| (P) (C) □
  
 
|- valign=top
 
|- valign=top
Line 329: Line 438:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Dec 15 <!--2021-->
 
| Dec 15 <!--2021-->
|  
+
| (P)
  
 
|- valign=top
 
|- valign=top
Line 335: Line 444:
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Nov 15 <!--2021-->
 
| Nov 15 <!--2021-->
|  
+
| (P) (C)
  
 
|- valign=top
 
|- valign=top
Line 345: Line 454:
 
|- valign=top
 
|- valign=top
 
| [http://www.mathjobs.org/jobs/list/18831 Widener U]
 
| [http://www.mathjobs.org/jobs/list/18831 Widener U]
 +
| <!-- Mathematics -->
 +
| Dec 10 <!--2021-->
 +
| (P)
 +
 +
|- valign=top
 +
| [https://www.stiead.ac.id Stiead University]
 
| <!-- Mathematics -->
 
| <!-- Mathematics -->
 
| Dec 10 <!--2021-->
 
| Dec 10 <!--2021-->

Latest revision as of 20:03, 15 August 2025

Welcome to the Mathematics Jobs Wiki 2021-2025 teaching positions page. This page collects rumors and authoritative information about the academic mathematics job market: positions, short lists, offers, acceptances, etc. It lists positions at departments that do not grant PhDs and are not research-oriented by other reasonable criteria. See the research positions page for more research-oriented academic math jobs.

To post news or corrections anonymously, please edit this wiki page yourself by clicking "edit" at an appropriate place. It is better to first register, but you can edit by IP number as well. You can also send email to wikimathjob@gmail.com to have messages posted or to report evil postings, e.g. inaccurate information about yourself or other applicants, or if you want your name removed. We are interested in information provided in good faith. Do not post wild hunches, and please respect the trust of your friends and colleagues.

Have you accepted a position? If so, it's a great courtesy to other job applicants to post that information here.

This site is currently supported by Matthias Koeppe, Greg Kuperberg, and Tao Mei. Tao reads the e-mail and he will keep the correspondence confidential as appropriate. Disclaimer: There is no guarantee that any information listed here is accurate; no warranty is expressed or implied. UC Davis and the UC Davis Math Department do not endorse this project and disavow any responsibility for the information on this wiki.


Contents

[edit] When Is the Right Time to Review Your Business Mobile Plan?

The best time to review a business mobile plan is before it becomes a problem. Costs creep up, usage changes, and new features appear that could save time and money.

A simple, regular review keeps spend aligned with reality, reduces risk, and improves service for the teams who rely on mobile every day.

Use this guide to spot the right moments to take a fresh look and to run a quick, effective review without slowing the business down.

The natural review cadence: quarterly light, annual deep

Quarterly check-ins: A 30–45-minute review every quarter is enough to catch unusual charges, overages, unused lines, or shifts in team behavior. Focus on data usage patterns, roaming, support tickets, and any plan features nobody uses.

Annual full review: Once a year, do a deeper assessment with finance, IT, and operations. Recalculate needs by role, verify coverage and performance in key locations, and rebid with providers if terms or service no longer fit. Tie the timing to budget planning so changes flow into the next financial cycle.

This cadence prevents surprises and helps negotiate from a position of data, not urgency.

Clear triggers that mean “review now”

Contract milestones: 60–90 days before contract end or auto-renew, review everything. Use the window to renegotiate, re-tier plans, or switch providers without penalties.

Sharp usage shifts: If data use spikes or drops by 20%+ for a team or location over a month, recheck plan tiers and pooled data sizes. Right-sizing stops overpaying or throttling.

Team changes: new hires, seasonal peaks, or restructures change the line count and mix of roles. Review when headcount moves by 10%+ or when a new department launches.

Coverage complaints: A pattern of dropped calls, slow data, or dead zones at job sites is a signal to test alternatives or add features like Wi-Fi calling, network priority, or a second carrier.

Device refresh cycles: When replacing a large batch of phones, revisit plan features like eSIM support, international options, and hotspot allowances to match how the new devices will be used.

Roaming or travel changes: Entering a new market, adding frequent travelers, or opening a satellite office abroad? Review plans for roaming passes, local eSIM options, or regional bundles.

Security or compliance updates: New MDM policies, MFA enforcement, or updated data retention rules can affect which plan features are necessary or which provider tools are required.

Bill shocks or hidden fees: Unexpected charges—premium-rate numbers, out-of-bundle costs, or overage penalties—warrant an immediate review of controls, alerts, and plan fit.

New offers in market: When carriers launch updated business plans, 5G features, or BYOD incentives, compare them to current terms. Market timing can unlock discounts without sacrificing service.

What to review in 60 minutes or less

Lines and roles: List active lines by team. Identify unused or low-activity lines. Match each role with a plan type (heavy data, voice-first, field, admin, traveler).

Usage vs. plan: Compare pooled data size to actual consumption. Look for chronic underuse or frequent throttling. Adjust pool size or redistribute roles across tiers.

Add-ons and extras: Audit paid features (hotspots, international packs, MDM bundles). Remove what isn’t used. Add what would prevent overages or improve service reliability.

Roaming spend: Flag the top roaming users and the routes they travel. Swap them to plans with regional passes or enable local eSIM profiles to cut costs. Coverage and performance: Gather recent complaints and speed test snapshots from key sites. If issues cluster, test a second carrier or request network optimization.

Support tickets: Review the top three mobile-related issues in the last quarter. Fix root causes with plan changes, training, or device settings.

Contract terms: Note renewal dates, price-rise clauses, and early termination fees. Calendar key dates at least 90 days ahead to keep leverage.

Security posture: Confirm devices meet baseline requirements (OS version, encryption, lock, MDM enrollment), and that SIM/eSIM lifecycle processes are enforced. Tighten where needed.

Signs the current plan is costing money

Chronic underuse: Paying for unlimited or large data pools when actual use is modest. Consider tiered or pooled options with realistic headroom.

Repeated overages: Regular throttling or out-of-bundle data charges. Increase pool size, move heavy users to higher tiers, or enable usage caps and alerts.

High roaming charges: Travelers relying on default roaming rather than passes or local profiles. Standardize a simple travel playbook with pre-approved options.

Unused lines and devices: Numbers assigned to former staff or dormant devices. Reclaim, suspend, or cancel. Use a monthly report to spot them early.

Helpdesk drag: Many tickets for SIM swaps, activation issues, or coverage problems. Move to eSIM where possible, and standardize devices by cohort.

How to run a focused plan review

Gather the facts Export last 3–6 months of bills and usage by line.

Pull a list of active lines with owner, role, and device model.

Collect roaming charges and any unusual fees.

Ask IT for top mobile-related tickets and any coverage trouble spots.

Segment by role

Define 3–5 simple user profiles: field, sales, office, exec, traveler.

Map each line to a profile. Outliers become candidates for change.

Right-size plans

For each profile, set a default plan or data tier.

Adjust pooled data to match aggregate use with a buffer (e.g., 10–15%).

Enable usage alerts at 70%, 90%, and 100% for both pool and heavy users.

Fix roaming and travel

Pre-approve roaming passes and local eSIM options by region.

Provide a short traveler checklist with activation steps and cost expectations.

Address coverage

Run quick tests at problem sites with trial SIMs from a second carrier.

Consider dual-carrier strategy for field teams or critical sites.

Tighten controls

Require MDM enrollment, enforce OS baselines, and block risky settings.

Define a simple SIM/eSIM process: who requests, who approves, how to audit.

Negotiate and document

Ask providers for updated quotes based on the refined profile mix.

Request waived fees, bundled support, and month-to-month options where flexibility matters.

Document changes, update the mobile policy, and set the next review date.

Timing tips that improve outcomes

Align with fiscal planning: Review 6–8 weeks before budget discussions to lock in savings and avoid mid-year surprises.

Avoid auto-renew traps: Start 90 days before the renewal window to compare offers and gather trials.

Pilot before you commit: Test coverage, throttling behavior, and international options with a small group during typical peak hours.

Sequence changes: Roll updates by team to limit disruption, starting with the highest savings or pain points.

Metrics that make the case

Cost per active line per month, by role.

Data pool utilization (average and peak).

Roaming cost per traveler per month.

Ticket volume related to mobile issues and average time to resolve.

Coverage incidents reported per site or team.

Lines reclaimed or suspended in the quarter.

Percentage of devices meeting security baseline.

These measures show impact in concrete terms and help track whether changes actually improved outcomes.

Common mistakes to avoid

One-size-fits-all plans: Mixed roles need different plans. Overpaying for uniformity is common—and avoidable.

Set-and-forget contracts: Market terms evolve. Without reviews, discounts lapse and features lag behind needs.

Ignoring small fees: Premium-rate calls, short-term overages, and accessory costs compound quickly. Root them out quarterly.

Skipping user comms: Small changes—usage caps, new roaming steps, or coverage workarounds—need clear, simple guidance. Good comms reduces tickets and frustration.

Delaying eSIM adoption: Remote activation saves time and cuts logistics. Waiting stalls onboarding and adds operational friction.

Final Words

The “right time” to review a business mobile plan is on a steady rhythm—quarterly for quick tune-ups and annually for a deeper reset—and anytime a trigger hits: contract windows, usage shifts, team changes, coverage issues, or unexpected costs. Keep reviews short, fact-based, and focused on roles, roaming, coverage, and controls. Right-sized plans, better travel setups, eSIM workflows, and clear rules will lower spend, boost uptime, and make the whole system easier to manage—without a scramble or a surprise when the bill lands.

[edit] United States

[edit] Long-term positions

[edit] A-K

Institution Areas Apply by Short lists and offers
Anderson U
Augustana College Jan 5 (P)
Bard College Oct 31
Bates College Dec 1
Berry College Oct 1
Canisius College Dec 1
Carleton College Nov 8 Rejections
Colgate U Dec 15
College of Charleston (P)
Columbia College Chicago
Creighton U Nov 30
Elon U Nov 30
Fordham U Nov 19
Grinnell College Oct 24

[edit] L-T

Institution Areas Apply by Short lists and offers
Lafayette College Dec 1
Loyola Marymount U Nov 15 (P) (C)
Loyola U Chicago Nov 15
Loyola U Chicago Nov 15
Manhattan College Jan 5
Nebraska Wesleyan U Dec 15
Ohio Wesleyan U Oct 25
Providence College Nov 1
Reed College Nov 24
Rose-Hulman Nov 11 (P)
Saint Mary's College, Indiana Dec 5
Saint Mary's College of California Dec 6 (P) (C) □
Saint Lawrence University Nov 1
Santa Clara U Nov 30 (P)
Sarah Lawrence College Dec 1
Seton Hall U
Smith College Oct 22
St. Mary's U of San Antonio Dec 10
St. Olaf College Nov 15 Rejections
Swarthmore College Oct 31

[edit] U-Z

Institution Areas Apply by Short lists and offers
Union College Dec 1 (P)
U Portland Nov 15 (P)
U Puget Sound Nov 24
U San Diego Nov 15 (P) (C) □
U San Francisco Dec 15 (P)
U St Thomas Nov 15 (P) (C)
Vassar College Nov 15
Widener U Dec 10 (P)
Stiead University Dec 10


[edit] Temporary positions

Institution Areas Apply by Short lists and offers

[edit] Canada

[edit] Long-term positions

Institution Areas Apply by Short lists and offers

[edit] Temporary positions

Institution Areas Apply by Short lists and offers