When to use this file
A useful quotation starts with a clear scope. This brief gathers client and technical requirements in one workbook without assuming a fixed price or delivery time. Each field includes input guidance. Write Unknown where clarification is required instead of guessing a coordinate system or accuracy requirement, then use the document to discuss the project scope.
Column and example preview
The preview shows the file structure. Observation data is synthetic; a dash means a blank field.
| Requirement | Your project | Guidance |
|---|---|---|
| Project location | — | Boundary / map link |
| Source system | — | EPSG / WKT + source |
| Deliverables | — | Formats and editable files |
| Accuracy | — | Project specification |
Use the file step by step
Define the purpose and scope
Record the project name, location, boundary or map link, and whether the work supports design, construction, quantities or documentation. Include area or corridor length with units and site-access requirements. The purpose helps define observation density and outputs, instead of requesting an unspecified survey.
Inventory files before requesting conversion
List each source file’s name, format and version, with its coordinate-system definition if available. Preview supported survey files in the viewer to check coverage. CSV and DXF may not carry a system definition. If it is absent, mark Unknown and confirm the source; do not select WGS84 merely because it is easy to display on a map.
Specify outputs and acceptance criteria
Specify required formats such as DWG, CSV and PDF, including editable source files and any accuracy report. Separate horizontal and vertical accuracy and identify the vertical datum. Use the consultant or contract specification; decimal places are not an accuracy claim. Identify the reviewer and approval process.
Discuss timing and constraints, then request pricing
State the desired deadline or milestones, permits, safety and confidentiality constraints, and available control. Resolve unknown fields with the team before agreement. Then use the pricing or quotation page and share the brief through the agreed contact channel. Downloading this file does not send it to GeoGiza.
The result to check
The result is a scope that can be discussed and priced: a defined location, known source data or explicit gaps, deliverables, accuracy, timing and reviewer. Each project is priced for its actual scope.
Common mistakes to avoid
- Requesting pricing without defining area or deliverables.
- Replacing unknown information with undocumented assumptions.
- Confusing a requested deadline with an agreed delivery date.
Frequently asked questions
Does the template include a price or delivery commitment?
No. It records requirements only. Price and schedule follow a review of scope, data and constraints.
Must every field be complete before contacting you?
Complete what is available and identify unknowns clearly. Discuss the gaps with the team; clear information reduces follow-up questions and rework.