Excavation requests
Illustrative workflow. This example shows how Geova can connect an operational process within a project application. Actual roles, checks, statuses, and required documents are agreed with the process owner.
Before defining the system
Identify the request owner, review teams, work-area geometry, relevant reference layers, required evidence, and existing systems that must exchange information.
1. Capture the request and location
The proposed system brings the request details, mapped work area, dates, attachments, and submitting organization into one record. A stable identifier keeps later reviews and field observations attached to the same request.
2. Check completeness and spatial context
Configured checks can highlight missing information and compare the proposed work area with the reference layers selected for the project.
Geova AI might help explain a comparison or find requests matching a clear condition, such as a missing site plan. The reviewer can inspect the scope, source data, and rule behind the result.
3. Coordinate the review
The application routes review tasks according to the agreed roles. Reviewers record comments or request revisions. The authorized person makes the decision through the defined workflow.
An AI result supports the review; it does not itself grant an approval.
4. Connect field follow-up
Inspection records, observations, and photos can be linked to the request. The project team can compare the submitted work area with the relevant field records and inspect progress in context.
5. Keep the outcome traceable
The request retains its submitted information, revisions, review history, field evidence, and agreed final status. Reports and exports use the same project identifiers.
Expected result
A connected journey from request to review and field follow-up, with location context and a clear record of who decided what.
Questions to resolve in your project
- Which spatial datasets are authoritative for each check, and who maintains them?
- Who can submit, edit, review, return, or close a request?
- Which actions require human confirmation?
- How are revised geometry and documents retained?
- Which external project or request identifiers must remain consistent?
Use Define your system to turn this example into a project-specific brief.