Your work. Your records.
Computer Systems Analyst Workplace Records
Computer systems analysts work across requirements, troubleshooting, implementation and user support. An employment concern may arise when an analyst is held responsible for a release or outage despite limited approval authority. Explain which system functions you supported and which decisions belonged to others. Technical access granted for work does not establish permission to take operational data into a personal employment file.
Call now(800) 800-5555Free initial case evaluation. Representation depends on work state and case eligibility. This guide explains record preparation; it does not determine whether a legal claim exists.
A record map for your role
What to organize first
Authority map
Separate requirements analysis, approval and implementation responsibility for the change connected to your concern.
Work intervals
Compare your own recorded time with relevant support duties and label estimates instead of deriving hours from ticket age.
Evidence index
List the types and dates of relevant technical records without retaining credentials, code or production information.
Start with the work you actually do
Analyze science, engineering, business, and other data processing problems to develop and implement solutions to complex applications problems, system administration issues, or network concerns. Perform systems management and integration functions, improve existing computer systems, and review computer system capabilities, workflow, and schedule limitations. May analyze or recommend commercially available software.
O*NET classifies this occupation as Computer Systems Analysts (15-1211.00). Its description covers a typical occupation, not every workplace or individual job. It does not establish employee status, overtime eligibility or employer misconduct.
- Troubleshoot program and system malfunctions to restore normal functioning.Source task 20950 · updated 08/2023
- Provide staff and users with assistance solving computer-related problems, such as malfunctions and program problems.Source task 3464 · updated 08/2023
- Test, maintain, and monitor computer programs and systems, including coordinating the installation of computer programs and systems.Source task 3465 · updated 08/2023
- Use the computer in the analysis and solution of business problems, such as development of integrated production and inventory control and cost analysis systems.Source task 3482 · updated 08/2023
A reference point for your pay records
May 2025 wage estimates by state
Compare your pay records with published BLS estimates for Computer Systems Analysts (SOC 15-1211). These describe an occupation across employers. They are not a required pay rate, an overtime calculation, or evidence of discrimination or unpaid wages.
Select your work state to see its published pay range. No personal pay information is requested or sent.
The 25th and 75th percentiles mark the middle half of the estimated wage distribution; the median is its midpoint. Actual pay can differ with experience, employer, location and duties. Hourly and annual figures are shown as published, without converting one into the other.
All published state estimates for this occupation
| State | Hourly 25th | Hourly median | Hourly 75th | Annual median |
|---|---|---|---|---|
| Alabama | $38.79 | $48.93 | $61.87 | $101,770 |
| Alaska | $38.40 | $42.56 | $51.22 | $88,520 |
| Arizona | $37.90 | $49.77 | $63.48 | $103,530 |
| Arkansas | $30.40 | $39.31 | $49.48 | $81,760 |
| Connecticut | $42.37 | $52.69 | $64.15 | $109,600 |
| Delaware | $43.68 | $53.16 | $65.63 | $110,560 |
| Florida | $38.15 | $48.99 | $62.31 | $101,900 |
| Georgia | $39.83 | $51.08 | $64.01 | $106,240 |
| Hawaii | $36.91 | $42.61 | $52.03 | $88,640 |
| Idaho | $33.30 | $36.21 | $45.89 | $75,310 |
| Indiana | $37.32 | $47.51 | $61.54 | $98,810 |
| Iowa | $37.10 | $46.11 | $53.07 | $95,920 |
| Kansas | $37.82 | $48.45 | $64.10 | $100,770 |
| Kentucky | $34.09 | $45.72 | $60.18 | $95,090 |
| Louisiana | $37.86 | $45.99 | $52.54 | $95,660 |
| Maine | $38.56 | $46.07 | $58.51 | $95,820 |
| Michigan | $39.83 | $49.72 | $61.10 | $103,410 |
| Minnesota | $44.91 | $51.13 | $63.56 | $106,350 |
| Mississippi | $30.87 | $41.48 | $57.89 | $86,280 |
| Missouri | $36.05 | $44.26 | $56.48 | $92,060 |
| Montana | $38.32 | $43.90 | $49.37 | $91,310 |
| Nebraska | $36.63 | $44.14 | $55.22 | $91,810 |
| New Hampshire | $42.60 | $51.77 | $64.47 | $107,670 |
| New Mexico | $37.68 | $47.22 | $58.68 | $98,220 |
| New York | $41.08 | $52.70 | $66.20 | $109,610 |
| North Carolina | $41.38 | $51.37 | $63.90 | $106,850 |
| North Dakota | $42.05 | $50.71 | $53.49 | $105,470 |
| Ohio | $38.97 | $49.19 | $63.16 | $102,320 |
| Oklahoma | $37.30 | $46.12 | $57.62 | $95,930 |
| Pennsylvania | $37.79 | $47.38 | $57.06 | $98,550 |
| Rhode Island | $48.57 | $64.73 | $65.09 | $134,630 |
| South Dakota | $37.88 | $47.98 | $64.67 | $99,790 |
| Tennessee | $36.75 | $45.98 | $57.33 | $95,630 |
| Texas | $41.33 | $51.63 | $65.47 | $107,390 |
| Utah | $38.18 | $47.48 | $56.03 | $98,770 |
| Vermont | $41.12 | $47.89 | $53.59 | $99,610 |
| Virginia | $44.47 | $58.09 | $72.44 | $120,840 |
| West Virginia | Not published | Not published | Not published | Not published |
| Wisconsin | $38.84 | $48.29 | $58.92 | $100,440 |
| Wyoming | $39.14 | $52.78 | $53.68 | $109,780 |
“Not published” preserves unavailable or suppressed source cells. “Above reporting limit” preserves a top-coded source value without inventing a number. A missing state estimate does not establish service eligibility. The data describe wage and salary employment; they do not measure self-employment income.
Source: BLS May 2025 state workbook · OEWS tables · BLS technical notes. Use your own schedule, pay statement and compensation terms to identify the question you want reviewed.
Map responsibility across the change
Describe the request, your analysis, the approving role and the implementation handoff in general terms. If a production issue led to discipline, distinguish changes you proposed from changes you were authorized to deploy. Note when requirements changed and what testing or sign-off was requested. Leave fault conclusions open where the underlying cause has not been verified.
Reconstruct support work and recorded time
For an hours or workload concern, list the support incidents and required maintenance windows relevant to your account. Use approximate durations only when clearly labeled. Compare them with your own time submissions, schedule and manager instructions. A ticket’s creation and closure times may include waiting or work by several people, so do not treat the full interval as your personal labor.
Preserve context without copying systems
Keep your own permitted employment messages and a descriptive index of relevant tickets, approvals or incident reviews. Do not export source code, passwords, customer information, security configurations or production logs. Avoid using elevated permissions after access has been restricted. A personal timeline can identify what a change record may clarify while leaving the original technical evidence available through an appropriate review process.
Choose your next step
Review the workplace retaliation guide, unpaid wages guide, or discrimination guide if those concerns fit your experience. A job title alone does not establish a claim.
Call now(800) 800-5555Current service-state coverage
AK, AL, AR, AZ, CT, DE, FL, GA, HI, IA, ID, IN, KS, KY, LA, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NM, NY, OH, OK, PA, RI, SD, TN, TX, UT, VA, VT, WI, WV, WY. Eligibility is evaluated individually; this list does not promise representation.
Explore state resources