Position vector: A position vector gives the location of a point relative to an origin, so it is tied to a specific reference point. In 2D, its components match the point coordinates, which is why location and vector notation are interchangeable in coordinate geometry. This idea applies whenever you need to encode a point as a vector object.
Displacement vector: A displacement vector describes the directed movement from one point to another, not the absolute location of either point. It captures both direction and magnitude of change, so reversing endpoints changes the sign. This is the correct object for motion, translation, and relative position questions.
Notation and direction: If points have position vectors and , then the vector from the first point to the second is order-sensitive. Swapping the order gives the opposite vector, which preserves the same length but reverses direction. Direction sensitivity is the main conceptual difference between vector difference and scalar distance.
Difference of positions gives displacement: The identity follows from path addition, because going from to is equivalent to going then . This is why subtraction appears naturally in displacement problems. It applies in any dimension as long as vectors are expressed in the same basis and origin.
Component-wise structure: If and , then . Each component measures signed change along one axis, so negative values are meaningful directional information rather than errors. This component view links vector algebra directly to coordinate geometry.
Key relations to memorize with meaning: > Core formulas: and . The first formula gives direction and relative movement, while the second strips direction to keep only length. Use the first for vector equations and the second for distances.
Method 1: Vector subtraction workflow: Start by naming position vectors clearly, for example and . Compute displacement as by subtracting corresponding components. Finish by checking whether the sign pattern matches the expected direction on a sketch.
Method 2: Coordinate-difference workflow: Convert position vectors to coordinates first, then apply . This route is fast when points are given in coordinate form and reduces notation overhead. It is equivalent to Method 1, so both should produce identical components.
Decision criterion and validation: Use vector notation when chaining paths or proving relationships, and use coordinate form when asked for distance or direct numerical displacement. In either method, verify by reverse-direction logic: . A quick reverse check catches most sign-order mistakes.
| Feature | Position Vector | Displacement Vector |
|---|---|---|
| Meaning | Location from origin | Movement from one point to another |
| Typical form | ||
| Depends on origin? | Yes | No, if endpoints are fixed |
| Reversing order | Not applicable |
Always label point order first: Write a mini statement like "from to " before any algebra. This locks in and avoids the most common sign inversion. Examiners reward consistent direction logic across all parts.
Build a rapid self-check routine: After computing, test one sanity condition such as . If this fails, the error is usually order or bracket handling in subtraction. A 10-second check often saves full-method marks.
Use structure in multi-part questions: Keep symbolic vectors as long as possible, then substitute values late to reduce arithmetic slips. If a magnitude is requested, separate the stages: first find displacement components, then apply the square-root formula. This separation prevents mixing vector and scalar steps.
Mistaking for : The displacement from to is , not the reverse. Reversing order gives the opposite direction, which may still look numerically plausible and therefore dangerous. Always map subtraction to endpoint minus start point.
Confusing vector with magnitude: Writing when the question asks for displacement drops direction information. This turns a vector answer into a scalar and changes the object being solved for. Read command words such as "vector", "displacement", and "distance" carefully.
Ignoring common reference setup: Position vectors must be interpreted from the same origin and coordinate basis before subtraction. If coordinate systems or origins differ, raw subtraction is invalid until converted. This misconception causes hidden conceptual errors even when arithmetic is correct.