AMASIA · Client Feedback

1

About you

So we can attribute and follow up on your feedback. Fields marked required must be completed.

Name required

Please enter your name.

Company required

Please enter your company.

Site required

Please enter your site.

Work email · optional

Add this if you are happy for us to follow up or quote you.

Your role · optional

SurveyorAcquisition & total station GeotechnicalSlope & stability monitoring AdministratorSetup & configuration ManagerOversight & reporting

Are you a Pangea account manager for a client running AMASIA? · optional

Yes No

If yes, we will ask for kudos about the software and our support in the statements section.

2

Rate your experience

Rate each area from 1 to 5 stars. A low rating (1–2) opens a short note so you can tell us why.

3

Navigation & sidebar

How the Control Table, Station Manager and Schedule Manager structure fits your workflow.

Hierarchy — does the grouping under Control Table, Station Manager and Schedule Manager match your daily workflow?

Aligns well Mostly Items feel misplaced

Clarity — are terms like “TPS”, “Instrument Pillar” and “Reference Point” immediately clear to your team?

Clear Some ambiguity Often unclear

Efficiency — for a high-priority task (e.g. checking a specific prism or managing a schedule), is anything buried too deep?

4

Map view

How you read and interact with the spatial picture.

Core utility — when you first open the Map View, what does your eye look for first?

Station status Active prism locations Open alerts Something else

Interactivity — how would you prefer to act on map objects (e.g. edit a prism or view its history)?

Pop-up on the map Link to other pages A mix of both

Layering — which layers or filters are most critical for your spatial data?

5

Thresholds & alerting

Your risk-management configuration and what happens when limits are breached.

Profile management — do Movement, Measurement and Instrument profiles cover your whole risk-management workflow?

Covers everything Mostly Significant gaps

Configurability — how complex is your typical threshold logic?

Simple linear limits Multi-stage / cumulative Both

Actionability — once a profile is breached, what is the ideal automated response or notification flow?

6

Dashboards & reporting

How you visualise data and share it beyond the app.

High-level overview — if your ideal landing dashboard had exactly three widgets, what would they show?

Time-series analysis — which chart types give your team the fastest insight into site stability?

Scatter plots Trend lines Displacement vectors Velocity / inverse-velocity Heatmaps

Exporting & reporting — how do you need to share visualised data outside the app?

Raw CSV exports Automated PDF summaries Live or public dashboard links API or integration feed

7

Your statements

Written, attributable comments we may use to tell the story of AMASIA.

In your own words — what are you (or your clients) saying about AMASIA?

In your own words — what are you (or your clients) saying about Pangea?

Why we ask for a written statement. To represent the benefits of AMASIA accurately, we can only use statements written by the client — on company letterhead or sent from a work email. Anything verbal, or paraphrased in our words, cannot be used.

Written statement · optional

Attach a statement on letterhead or an email · optional Choose a file to upload PDF, image, Word, or email file · up to 12 MB

I confirm any statement above is the client’s own written words (not verbal or paraphrased), and may be quoted.

8

Review & submit

Check your answers below. Use “Edit” on any section to go back and change it.

Tell us how AMASIA works for you

About you

Rate your experience

Navigation & sidebar

Map view

Thresholds & alerting

Dashboards & reporting

Your statements

Review & submit

Thank you

We couldn’t submit your feedback