Professional methods / Workflows

Keep the evidence
with the decision.

A site record, a photograph and a drawing each need a source, a review state and a next action.

These workflow summaries describe the current Field Method tools. They help you find the relevant tool and prepare a reviewable handoff; professional acceptance of the methods remains open.

Current workflows

From source
to a usable record.

Start with a bounded question. Carry the original evidence and its unresolved checks through each step.

  1. 01 / Existing conditions

    Build the site evidence.

    Use Landscape Workspace to select a San Diego County parcel, preview available sources and inspect the collected record.

    Workspace capabilities and sources
    Working steps
    Confirm the mapped parcel. Review source coverage before loading. Compare the preliminary model, analysis layers, evidence cards and quantity record.
    Record to keep
    The project question, source dates and coverage, coordinate frame, collected quantities and field checks that remain open.
    Still requires review
    Mapped parcel lines, dated footprints and model heights need project-specific verification. Keep LiDAR-suggested, user-entered and assumed heights distinct; flat reference ground is unverified. Unmapped ground remains unclassified; missing coverage is not a measured zero.

    Available now: mapped inventory, preliminary 3D, evidence records and source-linked exports. Field accuracy and native CAD/GIS acceptance remain unverified.

  2. 02 / Visual evidence

    Map site photographs.

    Turn your own site photographs into a Google Earth KMZ in the Photo tools. Site Lens does not show photographs; send a site from Site Lens to see them as pins on its 3D model and to line each one up for Blender.

    About the Photo tools
    Working steps
    Choose JPEG, PNG or WebP photographs, or a ZIP of up to 100. Review each location; a photograph without one is left out until you type it, not placed by guesswork. Confirm that you may share them, then download the KMZ.
    Record to keep
    Your original files and the KMZ with the photographs and their pins. The KMZ does not replace the originals: photos stored sideways or upside down, and reduced copies if you choose them, are held as copies without embedded metadata. The photo map alone does not save a session; work on a site sent from Site Lens is kept in that browser.
    Still requires review
    The source and accuracy of each location. A pin marks a photo location on the ground; it does not establish a camera orientation or measured site geometry. Photo Match is an alignment by eye, not a solved camera.

    Photographs are processed on this device and are not uploaded. Photographs in a saved Site Lens project stay in that project file; a copy goes to the Photo tools when the site is sent.

  3. 03 / Drawing preparation

    Coordinate the handoff.

    Choose the files the next reviewer can use and keep their units, sources and open actions with the package.

    Preview blank handoff records
    Working steps
    Review the drawing issue record and selected export layers. Save the PDF separately from the CAD, numeric GIS and model packages needed for the project.
    Record to keep
    A file list, revision, source register, projected and local model frames, intended use and the named next reviewer. The held Starter Kit contents preview describes blank records for these decisions.
    Still requires review
    Exported linework and models are preliminary study files. A quantity correction ledger records owner estimates without redrawing CAD/GIS geometry. The project JSON does not restore the complete workspace.

    The current drawing profile has 13 coordinated sheets, with an optional 14-sheet detailed profile. These outputs do not establish construction readiness.

Identify requirements early.
Review the evidence before drawing.

Project Brief records the jurisdiction and applicable requirements to verify at the start. Detailed site and design analysis follows. The formal Code Compliance Toolbox then records supporting evidence, unresolved issues and required professional review immediately before drawing preparation.

  1. Project briefJurisdiction and requirements to verify
  2. Site and design analysisEvidence, interpretation and open questions
  3. Code Compliance ToolboxEvidence and required professional review
  4. Drawing preparationPreliminary package and issue record

This is the tool's navigation and review-record sequence. It does not interpret regulations, determine compliance or certify completion of a design phase.