Project Planner
Use Geova Project Planner to turn a project idea into layers, tables, forms, relationships, and reference-data requests. Review the proposed design before authorizing creation.
Before you start: Sign in to the intended workspace, connect to the internet, and check that Planner is enabled. Design/review access and project creation access can differ. You also need the required workspace permissions and Geova points.
1. Open Planner and describe the work
In Geova AI, select Open Geova Project Planner in the header actions. If it is absent, check Access & requirements with your workspace administrator.
Describe the assets, repeat events, required information, and reference data. For example:
Create a streetlight inspection project for the North District. Use a point layer called Streetlights with Asset ID and Pole Number. Keep repeated visits in an Inspection visits table with Visit date, Condition, Notes, and an evidence attachment. Each visit must link to one streetlight. Condition choices are Good, Fair, and Poor. Show Notes when Condition is Poor. We will provide verified district polygons later.
Select Design project. The result is a proposed blueprint; this step does not create the project.
2. Review the blueprint and resolve questions
| Part | What to check in this example |
|---|---|
| Spatial layers | Streetlights uses points; one feature represents one asset |
| Related tables | Each visit gets a separate row, preserving earlier visits |
| Fields and forms | Labels, input types, required fields, and attachments fit the collection task |
| Relationships | Streetlights is the parent; Inspection visits is the child; required-parent and deletion policies fit the work |
| Lexicons and rules | Good, Fair, and Poor are valid choices; the Notes rule uses the intended fields |
| Reference requests | District polygons are requested for later supply; a request is not imported data |
Read every Assumption. Select I accept this assumption only if it is correct. Answer required Questions.
When answers change the design, the action becomes Apply answers · 1 point and generates a revised blueprint. Review the new result and its assumptions again. Use Revise with Geova to change the brief if the design does not match your intent.
3. Prepare the final review
Once the assumptions are accepted and required questions are resolved, choose Prepare secure review. The Geova backend validates the proposed work and returns a Server-validated review.
Review Planned operations, Required permissions, and any Warnings. Check whether each relationship will be active or remain a draft. If the design needs changes, use Back, revise it, and prepare a new review.
If execution is not enabled for the workspace, you can review and revise the plan, but Confirm and create project is not offered.
4. Confirm and open the project
- Select Confirm and create project.
- Read and accept the creation confirmation.
- Wait for Project created.
- Select Open project, or use Done and open it from Projects.
Successful creation commits the reviewed project structure together. It does not prove that the proposed field workflow is suitable or that all requested reference data has been supplied.
Understand points before proceeding
| Action | Current charging rule |
|---|---|
| A successful design answer or a newly generated revision | One Geova point |
| Apply answers · 1 point | Generates another design answer, so it uses one point |
| Successful project creation | One additional point, charged after the successful commit |
| Recovery of the same completed creation | Retrieves the retained outcome; it does not create and charge for a second project |
Review the usage information shown in Planner. Design and creation are separate actions; the one-point creation amount is not the total cost of a discussion with several revisions.
5. Check the created project
- Open Layers and Forms. Check names, geometry types, choices, and required fields against the accepted design.
- Open Data & Sync and check the related tables and relationships.
- If Planner reports draft relationships, arrange activation through the available workspace workflow before collecting linked visits. A draft cannot yet link records.
- Import and verify requested reference data, then configure or check its intended bindings. Planner saves reference requests; it does not automatically obtain the files.
- Create one practice streetlight and two visits. Verify the parent links, evidence, and Poor → Good → Poor rule behavior.
- Confirm the save and synchronization result before using the project for fieldwork.
Follow Record repeated inspections and Forms & Smart Logic for the manual checks.
If creation or review is interrupted
Reopen Planner in the same account and workspace so it can check its saved plan. Start with Check again when offered; also check Projects before starting a new design.
| What Planner offers or reports | Next step |
|---|---|
| Project created, but opening failed | Retry Open project, or open it from Projects; creation already succeeded |
| Check again | Check the saved plan's status after restoring connectivity |
| Open newer revision | Open the newer retained review instead of executing an older revision |
| Prepare secure review after no saved review is found | Rebuild the review from the retained proposal, then inspect it before any creation |
| Revise with Geova after the earlier execution is released | Revise only after Planner confirms that earlier execution ended without a successful commit |
| Reload draft | Retry reading the saved local draft |
| Discard damaged draft or New draft | Check Projects first and read the confirmation; discarding local draft information does not delete a created project |
If the state remains unclear, keep the retained draft and give support the visible error or request reference. An interrupted response does not establish that creation failed.
Completion check: The reviewed structure exists once, reference requests and draft relationships are understood, and a sample asset and its visits behave as intended.