When the Project Builds Its Own Ground
Not every local coordinate system starts with a published, documented low-distortion projection. Plenty of projects build something similar on the fly, an internal, unofficial ground system, tuned to make one project's numbers behave, without necessarily writing down exactly what was done.
A project-specific ground coordinate system, built by applying a scale adjustment to a standard grid so that distances behave like ground distances within one project, works the same way a low-distortion projection does, but often without the same documentation, making it far harder for anyone outside the original project to reconstruct or verify later.
A Reasonable Shortcut, Taken Informally
A project team, frustrated by a combined scale factor that keeps showing up in every stakeout, sometimes builds its own adjusted coordinate system: pick a scale factor, usually the inverse of the project's own combined scale factor, and apply it uniformly so that grid distances inside the project behave like ground distances again. This is not a fundamentally different idea from a proper low-distortion projection. It is often done with a spreadsheet and a single multiplier rather than a formally published, documented projection definition.
An informal project ground system and a published low-distortion projection can solve the identical mathematical problem. What differs is whether anyone besides the original project team could reconstruct exactly what was done, using only what was written down.
Why the Missing Documentation Matters Later
A project's own adjusted coordinates can look, at a glance, exactly like an ordinary State Plane coordinate, similar magnitude, familiar units, nothing visibly different. Without a clear record of the exact scale factor applied, the origin point it was applied from, and the standard system it was derived from, a future user, a different firm picking up the project years later, has no way to convert those coordinates back to a real, standard system at all, short of surveying enough shared points to reverse-engineer the adjustment from scratch.
A project's internally adjusted ground coordinates are not automatically compatible with, or convertible from, standard State Plane coordinates just because the numbers look similar. Without a documented scale factor and origin, recovering that relationship later can require as much fieldwork as building it did in the first place.
What a Well-Built Version Actually Records
The difference between a defensible project ground system and a risky one comes down entirely to documentation: the exact scale factor applied, the point or line it was computed from, the standard reference system and zone it derives from, and the date and reference frame that all of it assumes. Recorded clearly, a project ground system is a reasonable, useful tool. Left undocumented, it is a coordinate system only the original crew can actually use.
A dataset arrives with coordinates that look like State Plane, but distances measured against known control consistently disagree by a small, constant percentage. What does that pattern suggest? An undocumented project ground system, applying its own scale adjustment on top of the standard grid, is a strong candidate, and confirming the exact factor and origin used is the only reliable way to reconcile it.
A project-specific ground coordinate system solves the same problem a low-distortion projection does, adjusting scale so grid and ground distances agree within one project, but often without the same formal documentation. Recording the exact scale factor, origin, and reference system it was built from is what separates a genuinely useful shortcut from a coordinate system nobody else can ever reconstruct.
Everything so far has assumed a modern project built entirely on GNSS. The next chapter goes back further, to a record that predates GNSS by decades, and asks what happens when that older record and a new survey are compared directly.