The distinction from qualification is the one to get right first, because procedures that blur it produce confused documents. You qualify things — equipment, utilities, facilities, systems. You validate activities — processes, analytical methods, cleaning procedures, computerised systems and their intended use. Qualification is usually a prerequisite for validation: you cannot validate a process running on unqualified equipment.
Validation goes wrong in two directions and both cost money. Under-validated, you cannot demonstrate the process does what you claim, and the gap surfaces at the worst possible moment. Over-validated, you have built a maintenance obligation that consumes the team every time anything changes — which in turn creates pressure to avoid changes that would genuinely improve the process. The scope should track the risk each system actually carries.
The validation master plan (VMP) is the document that holds the position together: what is in scope, the approach, responsibilities, acceptance criteria and the current status of each item. Its practical value is as a reconciliation tool. A VMP that has drifted from the equipment actually on the floor makes every document downstream of it unreliable, which is why reconciling it is the dullest and most productive place to start any validation review.
Validation is a state to be maintained, not a project to be completed. Change control is the mechanism: a change that affects a validated process must be assessed for whether revalidation is required. Where that link is weak, validation status decays silently until a transfer, a scale-up or an inspection exposes it.