Define your system
Describe the work, the people, and the decisions before choosing screens or features. This guide helps you prepare a useful first brief for Geova.
Before you start
Gather a representative form, a small sample dataset or map, and an outline of the existing process. Use material you are authorized to share and remove unnecessary personal or confidential information.
1. Name the outcome
State what should improve and how your team would recognize a successful result.
“Bring excavation submissions, mapped work areas, review tasks, and field follow-up into one project record.”
2. Map the people and process
List each user role, the information it needs, and the actions it may take. Describe the normal path and exceptions such as missing information, a returned submission, reassignment, or cancellation.
3. Define the information
| Area | Questions to answer |
|---|---|
| Records | What is the main record: request, site, asset, inspection, or work order? |
| Location | Is the geometry a point, line, or area? Which reference layers matter? |
| Evidence | Which documents, photos, observations, and related records are needed? |
| Workflow | Which states and decisions exist, and who may change them? |
| Connections | Which existing applications, identifiers, and data exchanges must be supported? |
| Delivery | Which dashboards, reports, exports, and audit records are required? |
4. Choose where intelligence helps
Identify a concrete use for Geova AI, such as explaining a spatial comparison, finding incomplete records, summarizing project data, or helping design a project structure. Specify what a person must review before a result becomes an action.
5. Define one acceptance exercise
Choose a representative case. Describe its inputs, required decisions, expected output, and the people who will confirm that it works. Include at least one exception, such as a missing attachment or a request returned for revision.
Expected result
You have a concise brief that Geova can use to discuss scope and a working example that can guide interface design and validation.
If the process is not settled
Mark open decisions clearly and involve the process owner. Avoid inventing approval rules, status names, or obligations to fill gaps in the brief.
Start a system conversation, or explore excavation requests and demolition management.