How to run every EKB workflow
Plain-language, step-by-step guides for the whole platform.
- Who uses this
- First-time engineers, surveyors, drone pilots, CAD/GIS techs, and buyers.
- What this page does
- Plain-language, step-by-step guides for every EKB workflow.
- Start here
- Pick your role's workflow below and follow the numbered steps.
- What you need
- A project and the current workflow stage.
- EKB organizes / calculates
- Workflow ordering, inputs, review gates, exports, and next steps.
- EKB does not claim
- EKB is workflow support and does not stamp survey or engineering deliverables.
- Reviewer
- Licensed engineer / surveyor / pilot as applicable per step.
- Proof generated
- Every completed workflow produces an evidence record and can be attached to a proof package.
Guides
Civil/Survey Project Setup
For: Field lead, project manager, or drafter starting a new EKB project.
When: Before capturing any control, evidence, or drone data.
Required: project name, coordinate system, vertical datum, linear units
Optional: client, site address, notes
- Open Civil+Survey Projects (user)
- Create or select a project (user)
- Confirm CRS, vertical datum, and units (user)
- Save; project is ready for control capture (user)
Import: JSON project backup · Export: JSON project backup
Validation: CRS defined, Datum defined, Units defined
Review gate: no · Output: Project header for downstream reports.
Common mistakes: Leaving CRS as unknown, Mixing feet and metres in the same project
Next workflow: wf.field-evidence
Related routes: /civil-survey, /civil-survey/projects
Field Evidence Organization
For: Field crew capturing boundary, utility, ROW, drainage, grading, and roadway evidence.
When: During and after field visits.
Required: evidence label, category, photo or note
Optional: GPS tag, linked control point
- Open Field Evidence (user)
- Add each observation with photo and notes (user)
- Link evidence to control points where possible (user)
Import: CSV point list, JSON evidence bundle · Export: CSV point list, JSON evidence bundle, Field evidence package
Validation: Each evidence has a category, Photo or GPS tag present
Review gate: no · Output: Field evidence bundle for CAD handoff.
Common mistakes: Uncategorized evidence, No photo and no GPS tag
Next workflow: wf.survey-field-to-cad
Related routes: /civil-survey/field-evidence
Survey Field-to-CAD Evidence (V17)
For: Survey field lead + office drafter preparing CAD-ready evidence.
When: Once field evidence and control are captured.
Required: control points, field evidence, coordinate system
Optional: drone mission metadata
- Open V17 Survey Field-to-CAD Evidence (user)
- Score readiness and resolve missing evidence (user)
- Attach photos to control points (user)
- Pass rework-prevention checks (ai)
Import: CSV point list, JSON evidence bundle · Export: JSON evidence bundle, CAD/GIS handoff package
Validation: No missing-evidence blockers, No rework flags
Review gate: no · Output: Field-to-CAD readiness report.
Common mistakes: Skipping the missing-evidence detector
Next workflow: wf.drone-mapping
Related routes: /admin/v17-survey-field-to-cad, /buyer/v17-field-to-cad-evidence
Drone Mapping Support
For: Drone pilot capturing photogrammetry or RTK/PPK data for civil/survey support.
When: When aerial data is part of the deliverable.
Required: altitude AGL, sensor + focal length, image size, front/side lap
Optional: RTK/PPK, GCP count, weather notes
- Open Drone Mapping (user)
- Enter mission metadata (user)
- Review GSD, footprint, and overlap warnings (user)
Import: JSON mission file · Export: JSON mission file, Mission readiness summary
Validation: GSD in bounds, Overlap not below threshold
Review gate: no · Output: Drone mission readiness summary.
Common mistakes: Missing sensor width, Overlap below 60/60
Next workflow: wf.calculators
Related routes: /civil-survey/drone-mapping
Deterministic Calculators
For: Survey/civil/drone user running math on validated inputs.
When: Any time a computed value is needed.
Required: all inputs required by the selected calculator
Optional: —
- Open Calculators (user)
- Pick the calculator and enter inputs (user)
- Review deterministic result with units and assumptions (user)
Import: — · Export: Calculator log JSON
Validation: No missing source inputs, Units consistent
Review gate: no · Output: Computed values with source inputs.
Common mistakes: Running a calculator with missing inputs, Mixed units
Next workflow: wf.cad-handoff
Related routes: /civil-survey/calculators
CAD/GIS Handoff
For: Drafter preparing an EKB-native handoff package for licensed review or downstream drafting.
When: Once calculators, evidence, and drone data are ready.
Required: project header, control points, computed CAD comps
Optional: field evidence bundle, drone mission summary
- Open CAD/GIS Handoff (user)
- Review the handoff checklist (user)
- Complete required items (user)
- Send to licensed review gate (user)
Import: — · Export: CAD/GIS handoff package, CSV points, JSON bundle
Validation: Handoff checklist complete, Review gate reached
Review gate: yes · Output: CAD/GIS handoff package (EKB-native).
Common mistakes: Sending handoff without review gate
Next workflow: wf.qa-qc
Related routes: /civil-survey/cad-handoff, /civil-survey/cad-drafting
QA / QC Review
For: Reviewer running deterministic QA/QC across a project.
When: Before licensed review.
Required: project, control points, computed CAD comps
Optional: —
- Open QA/QC / Data Integrity (user)
- Resolve blockers (user)
- Ack warnings (user)
Import: — · Export: QA/QC report JSON
Validation: No blocking severity
Review gate: yes · Output: QA/QC findings report.
Common mistakes: Skipping blockers
Next workflow: wf.review-gate
Related routes: /data-integrity, /civil-survey/review-gate
AI Workflow Guidance
For: Any EKB user needing a next-step recommendation.
When: Whenever unsure what to do next.
Required: current workflow context
Optional: —
- Ask AI what to do next (user)
- AI asks for missing data instead of guessing (ai)
- AI explains uncertainty and required review (ai)
Import: — · Export: —
Validation: AI never invents numeric values
Review gate: no · Output: Guidance transcript with source references.
Common mistakes: Accepting AI outputs as final professional deliverables
Next workflow: wf.review-gate
Related routes: /workflow-guide, /civil-survey/ai-brain
Licensed Review Gate
For: Licensed Professional Engineer or Professional Land Surveyor.
When: Before any output leaves EKB for professional use.
Required: completed handoff package, resolved QA/QC blockers
Optional: —
- Open Licensed Review Gate (reviewer)
- Review inputs, calculations, and QA/QC report (reviewer)
- Approve, request changes, or reject (reviewer)
Import: — · Export: Signed review log JSON
Validation: Reviewer is licensed
Review gate: yes · Output: Licensed-review decision log.
Common mistakes: Reviewing without QA/QC clearance
Next workflow: wf.reports
Related routes: /civil-survey/review-gate
Reports / Exports
For: Drafter or PM exporting a package for the client or licensed office.
When: After licensed review.
Required: approved review log
Optional: —
- Open Import/Export Center (user)
- Select the export package (user)
- Verify required fields (user)
- Download (user)
Import: — · Export: PDF report, CSV, JSON, GeoJSON, KML, CAD/GIS handoff package
Validation: Export required fields present
Review gate: no · Output: Final report/export package.
Common mistakes: Exporting before review
Next workflow: wf.buyer-proof
Related routes: /import-export-center, /civil-survey/reports
Buyer Proof
For: Prospective buyer or partner.
When: During diligence.
Required: —
Optional: —
- Open buyer readiness route (user)
- Review the buyer-safe overview (user)
Import: — · Export: Buyer demo package
Validation: No private/pricing/valuation data leaked
Review gate: no · Output: Buyer-safe overview.
Common mistakes: —
Next workflow: (terminal)
Related routes: /buyer/ekb-platform-readiness, /buyer/civil-survey-readiness, /buyer/v17-field-to-cad-evidence
Admin Proof
For: Owner and internal reviewer.
When: For internal proof snapshots.
Required: —
Optional: —
- Open admin platform proof route (user)
- Review proof sections and scanners (user)
Import: — · Export: Admin proof package
Validation: Noindex/nofollow enforced
Review gate: no · Output: Admin-only proof snapshot.
Common mistakes: —
Next workflow: (terminal)
Related routes: /admin/ekb-platform-proof, /admin/civil-survey-proof, /admin/v17-survey-field-to-cad
Clean-Room / IP Proof
For: Owner, attorney reviewer.
When: During IP diligence.
Required: —
Optional: —
- Review clean-room notices and ownership (user)
- Run forbidden-claims and scope scanners (user)
Import: — · Export: IP proof package
Validation: Ownership notice present, No forbidden claims
Review gate: no · Output: Clean-room IP proof snapshot.
Common mistakes: —
Next workflow: (terminal)
Related routes: /admin/ekb-platform-proof
Performance Proof
For: Owner, buyer engineer.
When: During performance diligence.
Required: —
Optional: —
- Open Performance Proof (user)
- Review declared budgets and safety items (user)
Import: — · Export: Performance proof package
Validation: Budgets declared and honest
Review gate: no · Output: Performance proof snapshot.
Common mistakes: —
Next workflow: (terminal)
Related routes: /civil-survey/performance, /admin/ekb-platform-proof
Professional readiness (example)
Professional Readiness
Engineer review viewNext step: Route to the licensed reviewer.
- licensedReviewComplete
EKB supports civil / survey / drone / CAD workflows and does not stamp or certify professional deliverables.
What EKB does not claim: PE stamps · survey certifications · FAA / LAANC / legal approvals · finalized approvals · production-readiness claims · accuracy guarantees.