Free US shipping on CHCNAV GNSS receivers, iBase and RS7. Shipping for other products is charged separately.
Survey equipment demo checklist
Buying guidance
A useful demonstration ends with evidence you can use to decide. We recommend one representative task, a small set of agreed acceptance checks and a complete route from field capture to an output your team can open. Use this checklist for a GNSS setup, a handheld scanner or both.
Before the demonstration
1. Define the result. Write down the deliverable, tolerances, units, coordinate and vertical reference, file format, receiving software version and who will accept it.
2. Choose a representative site. Include a normal area and the condition that causes the most trouble. Agree access, safety arrangements and permission to capture images or data.
3. Prepare independent references. Identify checkpoints or dimensions measured with an appropriate separate method. Keep assessment checkpoints out of any control set used to fit or optimize the test data.
4. Name the exact kit. Record receiver/scanner model, hardware and firmware, controller, field app, processing release, license modules, batteries and accessories.
5. Agree the processing route. State whether local processing or cloud upload is allowed. Identify the computer, internet connection and any trial licenses used.
6. Set a fair comparison. Use the same site, task and acceptance criteria for competing options. Record operator experience and any changes to method; identical walking routes are less important than an equally demanding, documented test.
Record these details
Project and date: ______________________________________________
Equipment and software versions: _________________________________
Required output and acceptance criteria: ____________________________
Correction source or control method: _______________________________
Independent reference method: ____________________________________
Local or approved cloud processing: ________________________________
During a GNSS demonstration
Start on a known check point. Verify coordinate system, units, antenna/pole height, correction settings and reported solution status.
Collect and revisit points in open and difficult conditions. Record checks after any loss or recovery of corrections or positioning.
Test tilt compensation and the contactless method you intend to use. Include actual target distance, surface, visibility and lighting.
Stake the type of point, line or design your crew normally handles. Verify the result independently instead of judging only the on-screen guidance.
Export and reopen a project in your office software. Inspect coding, coordinates, heights and the records needed to review the observations.
Use the exact manufacturer operating instructions for the quoted system. The published GNSS, visual, laser and SFix specifications have different conditions.
During a handheld scanner demonstration
Plan a route that includes the difficult geometry. Follow the product’s initialization and route guidance, including appropriate loop closure or revisits.
Capture stairs, corridors, repeated rooms and problem surfaces relevant to your work. Record gaps, lost tracking, reinitialization and any rescan.
Inspect the real-time preview, then inspect the processed result. Look for duplicate surfaces, bowed or thick walls, floor offsets and holes at required features.
Use the intended georeferencing method if real-world coordinates matter. Check it with independent points after processing.
Open the actual exported deliverable. Confirm units, coordinates, color, useful detail, file size and performance in the receiving application.
Use one scorecard for the decision
On a small screen, swipe the table or focus it and use the arrow keys. Row labels stay visible.
| Check | Evidence to record | Result |
|---|---|---|
| Accuracy and consistency | Independent residuals or dimensions; required threshold; method and conditions | Pass / investigate / fail |
| Completeness | Required surfaces and features; missing areas; rescans | Pass / investigate / fail |
| Total working time | Setup + capture + offload + processing + cleanup + export + checking | ________ min |
| Manual effort | Operator interventions, failed steps and office editing | ________ min |
| Office compatibility | Exported file opened in the named application/version | Pass / investigate / fail |
| Operating cost | Needed licenses, credits, storage, renewals and computing | Quote required |
| Repeatability | Second capture or revisit and independent comparison | Pass / investigate / fail |
Agree acceptance thresholds before looking at the result. Keep “investigate” separate from “pass”: a plausible explanation for an error still needs to be checked. Record individual residuals and any exclusions; an average alone can hide a problem area.
Before you choose
Keep the permitted raw capture, processed output, check results and software/version record. Ask for a written explanation of any special settings or manual repair.
Match the quote to the tested setup. Identify anything used in the demo that is optional, time-limited, separately licensed or supplied by another party.
Confirm the support path, training scope, delivery timing and written warranty/return terms. Record who handles field setup, processing questions and manufacturer escalation.
Make a clear decision: ready to quote, another test needed, or unsuitable for this workflow. Name the unresolved item and the person responsible for it.
Frequently asked questions
How long should a demo take
Long enough to complete the agreed task through checking and export. A short representative capture can be useful, but stopping at a live preview leaves the office workflow untested.
Can we compare a scanner demonstration with our current method
Yes. Compare total time and the same accepted result, including setup, processing, checking and rework. Record any difference in scope or operator familiarity.
Should a good demonstration remove the need for future checks
No. It validates the tested configuration under the recorded conditions. Build routine checks and a fallback method into your field procedure.
Next step
Send us the completed brief and the main question you need the demonstration to answer. We can then discuss the equipment, site and scope before arranging the next step.
Related buying guides
- How to choose a GNSS receiver
- How to choose a handheld LiDAR scanner
- Pocket2 and Pocket2 Pro buying comparison
Before selecting a configuration
- Record the exact supplied model, part numbers, hardware and firmware versions.
- Check correction-service eligibility, regional coverage, accuracy, convergence and current service terms.
- Match capture hardware, control requirements, software modules and file outputs to your workflow.
- Compare ready-to-scan weights and verify accessory compatibility for the supplied revision.
- Review current prices, availability, shipping, applicable taxes, included items and license terms before ordering.
- Agree any demonstration, training, support and sample-data permissions as part of your quote.
Sources
Sources were checked October 5, 2026. Datasheet revisions are recorded where visible. Product pages can change, so the final quote should identify the specification for the supplied version. Manual links below lead to official support or download pages; select the exact model and current document there.
Manual navigation note: Manifold’s download site uses product selection. Choose Pocket2 or Pocket2 Pro and then Documentation Manual; the product query URL may open the general software panel. Downloading an installer does not establish a software entitlement.
- S1 CHCNAV i89 product page
- S2 CHCNAV i93 product page
- S3 CHCNAV i85 product page
- S4 CHCNAV ViLi i100 product page
- S5 i89 English datasheet revision March 2025
- S6 i93 English datasheet revision August 2026
- S7 i85 English datasheet revision June 2026
- S8 ViLi i100 English datasheet revision August 2025
- S9 Manifold Pocket2 product and specifications
- S10 Manifold MindPalace Pocket2 Pro product and specifications
- S11 CHCNAV RS7 product page
- S12 RS7 English datasheet revision January 2026
- S13 CHCNAV LandStar product page
- S14 Manifold download center and Studio license notice
- S15 CHCNAV CoPre product page
- S16 CHCNAV CoCloud product page and pricing FAQ
- M1 i89 official user manual landing page
- M2 i93 official user manual landing page
- M3 i85 official user manual landing page
- M4 ViLi i100 official user manual landing page
- M5 RS7 official user manual landing page
- M6 Manifold product downloads and manuals