Project workflows

Connect the knowledge and evidence behind each stage of the work.

Each workflow names the firm knowledge and project evidence it starts from, the work it prepares, and the professional responsibility that remains with the team.

Firm knowledge

Controlled access

Standards, templates, terminology, policies, and proven precedent should be usable without relying on one person’s memory.

View workflow details

Inputs

Firm-selected standards, templates, terminology, policies, workflows, and prior project examples.

Resulting work

A reviewed knowledge base that can inform proposals, research, packages, project outputs, and decisions in context.

Professional review

The firm decides which knowledge is approved and how it may be applied to a project.

Pursuit and scoping

Controlled access

New opportunities require current site evidence and the firm’s proven scope language, assumptions, and exclusions.

View workflow details

Inputs

Project location, available site evidence, prior scope language, assumptions, exclusions, and firm templates.

Resulting work

Reviewable pursuit research, scopes, assumptions, exclusions, and proposal sections tied to their supporting context.

Professional review

The professional owns the scope, fee, assumptions, exclusions, and final proposal approval.

Records research

Available by request

Parcel, map, survey, jurisdiction, and agency evidence is difficult to reconcile when it remains spread across separate public sources.

View workflow details

Inputs

An address, APN/AIN, recorded-map identifier, or project area, plus the project question the team needs to answer.

Resulting work

A source-backed project record with parcel context, recorded material, document links, mapped findings, and visible gaps.

Professional review

The professional determines which records apply and how they affect the project.

Pre-field preparation

Controlled access

Crews need applicable records, mapped context, control information, instructions, and open questions in one reviewed starting package.

View workflow details

Inputs

Recorded maps, corner records, benchmarks, centerline material, adjoiners, project limits, instructions, and known gaps.

Resulting work

A reviewable field package with source links, mapped context, instructions, and unresolved items clearly identified.

Professional review

The professional confirms field instructions, control, limits, and the package issued to the crew.

Project delivery

Controlled access

Research, working records, outputs, comments, and decisions should remain connected as work moves through review and handoff.

View workflow details

Inputs

Project research, source records, prepared outputs, package context, review comments, and approved decisions.

Resulting work

Connected project outputs and a durable review record that supports coordination, delivery, and future reference.

Professional review

The responsible professional reviews the work and retains final approval authority for deliverables.

Technical production

In development

Civil and survey calculations and publication need deterministic methods, reproducible results, and explicit professional review.

View workflow details

Inputs

Reviewed project context, technical instructions, geometry, observations, and calculation requirements.

Resulting work

Reproducible calculations and reviewable civil and survey outputs as the integrated product workflow develops.

Professional review

The responsible professional verifies technical work and approves every issued deliverable.

Next step

Start with the workflow your firm wants to improve.

Tell us what firm knowledge the team relies on, what project evidence it needs, and what reviewed work should result.

Request access