A NOTEBOOK FOR READING WORK RECORDSINDEPENDENT / UTAH CONTEXT
Staff Pay Notebook

UTAH / STAFF / RECORDS
Questions worth keeping

Independent editorial publication. Not affiliated with the University of Utah. No login or official employee support.

Work records

Employment Verification: Decide What Must Be Verified Before Sharing

A purpose-and-scope checklist for locating the correct official verification route and limiting unnecessary disclosure.

In this guide
  1. Start with the request's purpose
  2. Identify the official route by employment scope
  3. Use a purpose, fact, recipient checklist
  4. Worked example: a request says proof of employment
  5. Protect the authorization step
  6. Recheck before each new use
  7. Sources and evidence limits

Start with the request's purpose

A request to verify employment can mean several things: confirmation of a current job, dates of employment, or income information. A degree or enrollment check is a different request again. Before gathering documents, ask the requester what fact is needed and which official format is acceptable. This is an information-scoping exercise, not advice about a loan, rental application, or legal obligation. A vague request should not automatically lead to sending an entire pay statement or a collection of personal records.

Identify the official route by employment scope

The University's public verification page distinguishes Campus and Health Academics, which it routes to EmpInfo, from Hospitals and Clinics staff, which it routes to i2Verify. It also describes consent requirements for income verification. Use that current official page to confirm the applicable route rather than following a vendor link supplied by an unknown sender. The Registrar's public guidance separately identifies enrollment and degree verification and directs employment inquiries to Human Resources. A similar-sounding verification service is not evidence that it serves the same purpose.

Use a purpose, fact, recipient checklist

Write down three items before sharing: the purpose of the request, the exact fact to be verified, and the verified recipient. Add the official route only after those items are clear. This checklist is a reader-created decision aid, not a University submission form. It prevents a document's availability from deciding its destination. Just because you can download something does not mean it is the correct evidence for a requester or that it should be sent through an ordinary email conversation.

Worked example: a request says proof of employment

Imagine a fictional employee receives a legitimate request for proof of employment. The request does not say income history is needed. The employee first asks whether a basic employment confirmation is sufficient and verifies the destination independently. They then consult the University's route for their employment scope. They do not send a complete earnings history merely because a pay statement is close at hand. If the requester later specifies income information, that is a new, more precise requirement to handle through the appropriate authorization process.

Suppose the person also needs proof of a university degree. They keep that task separate and use the Registrar's guidance rather than asking the employment vendor to verify academic records. Their final checklist now has two purposes, two evidence routes, and potentially two recipient instructions. This is more organized than one large packet labeled verification. The example asserts no guaranteed turnaround, acceptance standard, or outcome for any outside application.

Protect the authorization step

Follow the official provider's current instructions yourself, especially where authorization or sensitive identifiers are involved. Do not post codes, identity documents, or account credentials in a public forum or send them to an unsolicited contact. If an external requester proposes an unfamiliar process, confirm it with the responsible official office before proceeding. This site is an independent information resource and cannot perform verification or receive authorization on behalf of the University.

Recheck before each new use

Verification providers and submission instructions can change. The routes above were checked October 1, 2026; the University's Campus and Health Academics page separately describes a June 3, 2021 provider implementation. Keep those dates distinct. Return to the official page for a new request rather than treating an old saved form as permanent guidance. The practical result should be a narrowly defined request sent through the correct channel with only the needed information.

Continue reading: Employee Pay and Student Refunds: Name the Money Before Seeking Help, Translate Skills Across University Occupations Without Stretching Them, Explore Facilities and Administrative Career Pathways Without Promises.

Have a public source that changes this analysis? Suggest a correction. Please don’t send health records, financial information, employment records or account credentials.

Cookie settings