3.2 Project Standards and Execution Plans

The January 2025 BPELSG PLS test plan splits Identify project standards (activity I.6) from Develop plan for project execution (activity I.7). Activity I.6's examples are mapping, accuracy requirements, legal requirements, methodology, quality assurance, agency standards, and project specifications. Activity I.7's examples are mapping, accuracy requirements, methodology, quality assurance, and client needs. Independent OpenExamPrep teaching treats those lists as stacked controls, not synonyms. Domain I questions may also use knowledge C (impact of local ordinances) and knowledge J (interpretation of construction-plan staking elements) without turning this chapter into a Field Operations manual.

Seven standard layers you must name

If you cannot name which layer is driving a requirement, you will budget the wrong product.

Mapping standards say what the sheet or file must contain and how it must look: scale, contour interval, layer naming, sheet size, digital delivery, and, for statewide maps, the Professional Land Surveyors' Act content rules. A Record of Survey must meet BPC 8763 (18 by 26 inches or 460 by 660 millimeters, specified media) and 8764 (monuments, basis of bearings, relationship to adjacent records, 8764.5 statements, and the reason 8762(b) applies). A city topographic standard may instead demand a stated CAD template and a digital terrain model.

Accuracy requirements are numeric or classification targets: relative positional precision, contour accuracy, GNSS vector RMS, or a named specification in the contract. They are not the same as a quality-assurance checklist. A job can have a tight accuracy specification and still fail because nobody ran independent checks.

Legal requirements are statutes and regulations that apply whether or not the client asked: BPC 8762 Record of Survey triggers, 8771 monument perpetuation before street work, written-contract rules in 8759 when that section applies, and right-of-entry rules. You identify them at kickoff so the execution plan has a clock.

Methodology is the 16 CCR 404.2 choice of field and office procedure: which control, which GNSS or total-station scheme, whether UAV or terrestrial LiDAR is fit for the stated accuracy, and how you will reduce the data. Equipment capability (test-plan knowledge I) is an input; it is not a methodology by itself.

Quality assurance (QA) is the firm's process for proving the work met the accuracy and legal layers: independent check shots, loop closures, peer review of a boundary narrative, comparison of extracted breaklines to field locates. QA does not replace an accuracy specification, and an accuracy specification does not replace QA.

Agency standards are the extra rules of the body that will review or own the product: county surveyor examination under BPC 8766, Caltrans survey specifications on state highway work, a flood-control district's mapping manual, or a utility owner's exhibit format.

Project specifications are the contract documents for this job, including special provisions that may be stricter than the agency's general manual.

Local ordinances sit across several of those layers. Knowledge C is not a prompt to recite every municipal code. It is a prompt to look. Cities and counties adopt monument materials and tags, digital submittal portals, coordinate-system notes, paving-season monument-preservation deposits, and planning-setback exhibit checklists that the PLS Act does not reprint. BPC 8771 and 8772 and Subdivision Map Act sections 66495 through 66498 are the statewide monument frame the test plan cites (knowledge G); a local ordinance may still specify a two-inch iron pipe with a particular tag, a tie-out sketch before reconstruction, or a preconstruction monument inventory the city engineer will not waive.

Accuracy specifications are not QA, and neither is a local monument rule

A Caltrans or city accuracy class tells you how close measurements must be. A QA plan tells you how you will know. A local monument ordinance tells you what physical object must be left in the ground and what paperwork the city wants with it. Mixing the three produces classic traps: treating a dense UAV orthophoto as a boundary; treating a county's CAD layer list as a substitute for 8764; treating a tagged rebar that the superintendent likes as compliance with 8771 when the local code required a different monument and a corner record.

Construction-plan staking at the planning level (knowledge J) means the execution plan identifies which plan elements will be staked—curb face, catch points, finished-floor corners, wet-utility offsets, right-of-way—and on what basis of control. It also names the stop-work rule when plans and field evidence disagree. 16 CCR 404.2(b) expects the person in responsible charge to be able to discuss conflicts between construction drawings and actual conditions. That is a planning reservation, not a lesson in occupying a radial point. How the crew marks a lath belongs in Field Operations.

Worked example: execution plan that forgets the Record of Survey clock

A private owner hires your firm to resolve the southerly line of a ranch parcel after a neighbor's fence survey. Field work occupies found monuments, discloses a material discrepancy in position with the 1978 Record of Survey, and you set new monuments on the line you hold. The client wants stakes next week so a mason can build. Your project manager builds an execution plan with four lines: two field days, CAD, a client exhibit, and an invoice.

That plan is incomplete the moment BPC 8762(b) applies. Among the mandatory filing triggers are material evidence or physical change not appearing on a prior subdivision map, official map, or Record of Survey; a material discrepancy in position of points or lines, or in dimensions; evidence that might result in materially alternate positions; location or retracement of points or lines not shown on those prior records; and points or lines set during a field survey of a deed parcel that are not shown on those prior records. For this subdivision, a material discrepancy is limited to position or dimensions.

BPC 8762(c) requires the Record of Survey to be filed within 90 days after the setting of boundary monuments during the field survey or within 90 days after completion of the field survey, whichever occurs first. If you cannot meet that limit for reasons beyond your control, BPC 8762(d) requires a letter to the county surveyor before the 90 days expire, with an estimated completion date, the reasons for delay, and a general location including assessor's parcel number. The first letter need not dump every survey detail; if others survey the same location, you then provide information the county surveyor requests without unreasonable delay.

The execution plan must also budget county surveyor examination. BPC 8766(a) gives the county surveyor 20 working days after receiving the map, or additional time mutually agreed, to examine mathematical data, substantial compliance with 8764, and compliance with 8762.5, 8763, 8764.5, 8771.5, and 8772. The examination shall not require you to change methods or to run a field survey to verify the map (8766(b)). If the map comes back, BPC 8767 generally requires resubmittal within 60 days or an agreed time. Those clocks are part of legal requirements and agency standards in I.6 and part of the plan for project execution in I.7. A PDF exhibit emailed to the client is not a filing with the county surveyor, and a mason's schedule does not toll 8762(c).

Local ordinance impact belongs on the same plan. If the parcel is inside a city, BPC 8762.5 blocks filing a Record of Survey that shows a division into additional parcels unless the city engineer (or county surveyor in the unincorporated area) certifies Subdivision Map Act and local-ordinance compliance. If the city has a monument ordinance that specifies cap size or digital submittal, the 90-day map that ignores those extras will bounce in review even if 8764 is met.

Rebuild the ranch-line plan as: research; field; boundary analysis; monumentation; Record of Survey drafting and 8764.5 statements; county or city submittal fee and 20-working-day exam; possible 60-day resubmittal; client exhibit clearly labeled preliminary if it issues before the recorded map (BPC 8761(c)); and, if staking for the mason is in scope, a written extra-services path under the BPC 8759 additional-services description so layout does not silently expand into unbudgeted construction surveying.

UAV and other methods still need the same stacked standards. For the 38-acre basin in section 3.1, the execution plan would cite the city's mapping standard, the numeric check-shot tolerance, the legal question whether any 8762 trigger appeared while occupying control, the UAV methodology the PLS already approved, the QA residual report, and the client need for invert shots. Skipping QA because the point cloud looks dense is not an execution plan.

BPC 8765 exemptions (public-officer copy, Bureau of Land Management, a Subdivision Map Act map in preparation or recorded, a clean retracement with a corner record, specified mobilehome-park interior lots) are identification tasks at kickoff, not a reason to omit the clock from every boundary job. If an exemption does not clearly apply, plan the Record of Survey.