You've Gotta Have a Baseline
If you're reading about a baseline plan or paging through definitions, you can find examples of how conceptual project management can be with phrases like "a resource designed to arbitrate a project from a given point, including pre-approved or approved measurements and markers for developing along a project trajectory, where recognized parameters approach a goal set..." Huh?
So what is a baseline plan, and did the above example help at all? Yes, a baseline plan is a resource, it's something that you should have at the beginning of a project. Yes, the baseline plan often gets "approved." Simply put, a baseline plan is a plan that defines what planners hope the project will look like. It includes cost, time, and goal factors, and it's an attempt by whoever is putting the plan together to make reasonable estimates. Whoever is "in charge" signs off on it. After that, a baseline plan provides guidance in all stages of the project. Some might call it a "road map" to a project's success.
You can set up a baseline plan with software like Microsoft Project, useful for planning all kinds of complex processes. Or, you can get your baseline plan down on paper and deliver it to others working on aspects of that project. Either way, a baseline plan is a measuring stick for what you encounter along the way.