You're staring at a coordinate plane. That's why two lines cross. One's dashed, one's solid. Half the plane is shaded. The question at the bottom of the page says: Write a system of inequalities for the graph.
And your brain goes: Wait — which direction is the inequality? Is it greater than or less than? Why is that line dashed again?
Yeah. Been there.
At its core, one of those algebra skills that looks simple on the surface but trips up even strong students. Also, not because the math is hard — because the translation from visual* to symbolic* is where the gremlins live. One flipped sign, one missed dashed line, and the whole system falls apart.
Let's walk through it together. And no jargon dumps. Just the steps that actually work.
What Is a System of Inequalities (When You're Looking at a Graph)
A system of inequalities is just two or more inequalities that are true at the same time. On a graph, that shows up as a shaded region — the overlap where every inequality in the system is satisfied.
Each line on the graph represents a boundary. The shading tells you which side of that boundary counts.
- Solid line → the boundary is included →
≤or≥ - Dashed line → the boundary is not* included →
<or>
That's the first decision point. Miss it, and you've already lost.
The shaded region? Consider this: that's your solution set. Every point in that region makes all the inequalities true simultaneously. Points outside fail at least one.
The Two Forms You'll See Most
Most textbook graphs use lines in slope-intercept form (y = mx + b) or standard form (Ax + By = C). Your job is to read the line, write its equation, then slap the correct inequality symbol on it based on the shading.
Simple in theory. Here's the thing — in practice? You need a reliable process.
Why This Skill Actually Matters
You might be thinking: When am I ever going to look at a shaded graph and need to write the inequalities?*
Fair question. Here's the honest answer: you probably won't do this exact task in your future career. But the thinking* behind it? That shows up everywhere.
- Linear programming — optimizing profit, minimizing cost, scheduling resources — all starts with writing constraints as inequalities from a verbal description or visual model.
- Data science — classification boundaries, decision regions, support vector machines — same idea: which side of the line?
- Engineering — feasible regions for design parameters, safety margins, tolerance zones.
- Economics — budget constraints, production possibilities, indifference curves.
The graph-to-inequalities translation is the training wheels version. You're learning to read a visual constraint and encode it algebraically. That's a transferable superpower.
Plus, it's on the test. So there's that.
How to Write the System — Step by Step
Here's the process I teach. It works every time if you don't skip steps.
1. Identify Each Boundary Line
Count the lines that form the shaded region. Plus, most systems have two or three. Each one gets its own inequality.
Look at each line individually. Ignore the others for a moment.
2. Find the Equation of the Line
You need the equation* before you can write the inequality*. Two main approaches:
If the line passes through clear grid points:
- Pick two points with integer coordinates.
- Calculate slope:
m = (y₂ - y₁) / (x₂ - x₁) - Use point-slope or plug into
y = mx + bto find the y-intercept.
If the line is given in the problem (sometimes they label it): just use that. Simple as that.
Pro tip: If the line is vertical, the equation is x = a. If horizontal, y = b. Don't overthink these.
3. Determine the Inequality Symbol
This is where most errors happen. Two things to check:
Solid or dashed?
- Solid →
≤or≥ - Dashed →
<or>
Which side is shaded?
- Pick a test point not on the line.
(0,0)is the easiest — unless the line passes through the origin. Then pick(1,0)or(0,1)or whatever's convenient. - Plug the test point into the equation* (treating it as an equality for a moment).
- If the statement is true, the test point is in the solution region → shade that* side.
- If false, shade the other* side.
Then match the shading direction to the symbol:
If you found this helpful, you might also enjoy distance decay definition ap human geography or ap calculus bc exam score calculator.
- Shaded above the line (greater y-values) →
y > mx + bory ≥ mx + b - Shaded below the line (lesser y-values) →
y < mx + bory ≤ mx + b - For vertical lines: shaded right →
x > aorx ≥ a; shaded left →x < aorx ≤ a
4. Write Each Inequality
Combine the equation with the correct symbol. Do this for every boundary line.
5. Write the System
Put them together with curly braces or just list them. Both are acceptable:
{ y ≤ 2x + 3
{ y > -x + 1
Or:
y ≤ 2x + 3
y > -x + 1
That's it. That's the system.
Example Walkthrough
Let's say you have a graph with:
- A solid line passing through (0, 2) and (2, 0)
- A dashed line passing through (0, -1) with slope 3
- The region below* the first line and above* the second is shaded
Line 1: Points (0,2) and (2,0) → slope = (0-2)/(2-0) = -1. y-intercept = 2. Equation: y = -x + 2. Solid line. Test (0,0): 0 ≤ -0 + 2 → 0 ≤ 2 true. Shaded below → y ≤ -x + 2.
Line 2: Slope 3, y-intercept -1. Equation: y = 3x - 1. Dashed line. Test (0,0): 0 > 3(0) - 1 → 0 > -1 true. Shaded above → y > 3x - 1.
System:
y ≤ -x + 2
y > 3x - 1
Done.
Common Mistakes (And How to Avoid Them)
I've graded hundreds of these. The same errors show up again and again.
1. Flipping the Inequality Symbol
Shaded above the line but wrote y < ...* Happens constantly.
Fix: Always use a test point. Always. Even if you think* you know. The 10 seconds it takes saves points.
2. Confusing Dashed vs. Solid
Dashed line but used ≤* or solid line but
2. Confusing Dashed vs. Solid Lines
Using ≤ for a dashed line* or writing y < ...Remember: **solid lines mean the boundary is included in the solution** (so use ≤or≥), while **dashed lines mean it’s excluded** (use <or>). In practice, for a solid line* is a classic mix-up. This distinction is critical because it defines whether points on the line satisfy the inequality.
3. Misinterpreting Shading Direction
Students often guess which side of the line is shaded instead of verifying with a test point. Even if the shading looks obvious, always plug in a test point to confirm. Visual assumptions can be deceiving, especially with slanted lines or tricky graphs.
4. Forgetting to Check All Inequalities
When dealing with systems of inequalities, the solution is the overlap of all shaded regions. So naturally, it’s easy to write individual inequalities correctly but fail to ensure their intersection makes sense. Double-check that your final answer satisfies all conditions simultaneously.
5. Mixing Up Variables in Vertical/Horizontal Lines
Vertical lines (x = a) and horizontal lines (y = b) are straightforward, but students sometimes reverse the variable. Think about it: for example, writing y > 5 for a vertical line at x = 5 instead of x > 5. Stay alert to the axis being constrained.
Conclusion
Writing systems of linear inequalities from a graph boils down to precision and verification. So by methodically finding line equations, confirming symbols with test points, and double-checking shading directions, you can avoid the pitfalls that trip up most learners. Mastering this skill isn’t just about passing algebra—it’s foundational for optimization problems, economics, engineering, and any field where constraints define solutions. Practice with varied graphs, and soon, translating visuals into mathematical language will feel like second nature.
