Before fieldwork
Define what complete means.
Configure the questions, validation, evidence, and roles while the workflow is still being designed.
Office configurationAbout aQRate
Built to close the gap between field evidence and decisions.
Roshan Water Solutions created aQRate around a simple idea: information collected in the field should arrive complete, understandable, and ready to use.
Edmonton, Alberta University of Alberta roots
From observation to use
“
Field programs create valuable information. The friction appears when forms, media, context, and review travel separately.
01 Research Foundational concept and technology
→ 02 Roshan Water Turn the insight into a product
→ 03 aQRate Connect the operational record
The intended outcome A continuous route from configured requirement to field evidence, review, and structured output.
Our mission
Reduce the friction between observation and decision.
Field programs can lose clarity at every handoff: a requirement becomes a paper note, a photo loses its context, or an office team re-enters what a crew already captured.
One continuous record
At the point of work
Observe with context attached.
Capture the record, location, time, identifiers, media, and attestation together—even while offline.
Field collectionAfter submission
Make the information useful.
Synchronize for review, resolve exceptions, and deliver a report or structured output without recreating the work.
Review & deliveryHow we build
Principles grounded in practical field work.
These are product lenses, not slogans. Select one to see how it changes the decisions inside the platform.
Field reality
Start where the evidence is created.
Connectivity, weather, gloves, repeated visits, and interrupted work are not edge cases. They shape the workflow from the beginning.
- Offline-first collection path
- Guided requirements at the point of work
- Context captured with the submission
Record continuity
Keep the handoff understandable.
The record should carry its identity, origin, evidence, and review state as it moves between field, office, and downstream systems.
- Identifiers stay attached
- Evidence keeps its source context
- History remains reviewable
Useful structure
Standardize without flattening the work.
Different programs need different questions. The platform provides a consistent route while leaving room for the structure each operation requires.
- Configurable forms and validation
- Role-appropriate views
- Reports and structured outputs
The people behind the platform
Built in Alberta for field teams everywhere.
Edmonton, Alberta, CanadaAcademic roots. Operational focus.
01 Concept & direction
Amirreza (Amir) Sohrabi
Cofounder & CEOCo-founder who developed the foundational concept through academic research. PhD graduate from the University of Alberta.
LinkedIn
02 Technology & innovation
Parmiss Mojir Shaibani
Cofounder & CTOCo-founder who developed the foundational technology through academic work at the University of Alberta. PhD holder with expertise in technical innovation.
LinkedIn
03 Systems & integrations
Saman Ghadirian
Systems Architect & Back-End DeveloperSystems architect responsible for building scalable back-end infrastructure and connecting the platform’s services and integrations.
LinkedIn
04 AI & interface
Shabnam Shirzadegan
Lead, Artificial Intelligence & User InterfaceLeads AI initiatives and interface design, shaping intuitive product experiences supported by intelligent automation.
LinkedInTeam roles and biographies reflect the current public aQRate company profile.
CompanyRoshan Water Solutions
ProductaQRate™
FocusConnected field-data workflows
Start with your workflow
Let’s start with the work your team does today.
A useful demo begins with a real form, inspection, sample, or reporting requirement.