QR or manual setup
Scan with a camera, load a QR image or enter connection details. Quick setup can populate the sensor information and initiate recording.
Business handling intelligence / Built in Ohio
LoadClarity gives equipment, logistics and insurance inspection teams a handling record they can review. Configure the recorder for your cargo, find tilt, impact and drop events, and export a checkable report. Use the record with receiving checks, rental-return inspections and claim documentation.
For equipment owners, rental fleets, logistics teams and insurance inspectors.
A rough-motion event is recorded in this example. Inspect restraints, packaging and load position. This is a reason to check whether cargo shifted, not a measurement of sliding distance.
Inside the report
Actual output from the desktop application’s report generator, shown with synthetic demonstration data. Inspect the summary, then follow the notable events and reported measurements. These captures show the report format, not a customer shipment or a validated sensing result.
Actual desktop report-generator output, excerpted for readability. Synthetic inputs illustrate the format; these are not customer results or a test of measurement accuracy.
32 capabilities / 8 areas
Explore the desktop software by the job your team needs to do. Bring the relevant area to a private demonstration using your equipment and review process.
Setup & recording
Scan with a camera, load a QR image or enter connection details. Quick setup can populate the sensor information and initiate recording.
Arm or pause capture separately from the Bluetooth connection. Load the device settings and request baseline recalibration before the agreed trial.
Automatic reconnect attempts, scan fallback and connection status help the operator see an interrupted link. The current desktop build supports one active sensor.
Keep a session identifier and trip window with the recorded workflow. Mark delivery and review so the exported record carries the application’s review stage.
The setup wizard recommends eight settings; the other controls remain available for manual tuning. Thresholds need validation with the actual mounting, cargo and packaging.


Inside the companion software
Explore the controls and outputs present in the desktop prototype. This walkthrough explains the software; it is not a live sensor feed or an application screenshot.
01 / Set up the shipment
Choose a shipment profile and review the wizard’s suggested sensitivity settings. Use a QR image, camera scan or manual entry to fill in connection details.
A rugged machine and a fragile instrument need different handling rules.
Profiles are starting points for testing with your packaging. They are not certified damage thresholds.Built around your problem
Machinery owners + manufacturers
Review tilt, rough-motion, drop and impact events alongside the receiving inspection before putting the equipment into service.
Rental fleets
Compare handling events with dispatch and return checks. Export the recorded context with your inspection notes for the next reviewer.
Product shippers + carriers
Bring recorded handling context to a customer discussion. Preserve the event timeline with photos, packaging observations and shipment documents.
Insurance inspectors + claims teams
Work from a shareable record of what the sensor captured. Check exported files for changes and compare events with independent inspection and handoff records.
Combine the LoadClarity export with the documents your team already uses.
Supports an investigation; the record alone does not establish damage, fault or insurance coverage.
Shipment handling / Choose the right record
GravPin and LoadClarity address the same handling problem in different ways. Start with what your receiving team needs to know.
“Did this item tip beyond our handling rule?”
“What handling events should we investigate?”
Both are working prototypes available for demonstration. Fit, specifications, price and production supply are agreed for the intended use. Neither an indicator nor a recorded event establishes damage or responsibility by itself.
01 / What you get
Filter and search the live activity timeline. Review tilt, inversion, impact, drop and rough-motion events, with worst observed metrics and severity indicators to guide a closer inspection.
Decision Trace shows the event, severity, risk contribution and suggested action. Cargo profiles and packaging settings let a trial reflect what you move. The score is a rule-based review aid.
Export a readable report, CSV decision timeline and source snapshot with file checks. Include available session, configuration and data-quality context alongside your own inspection and shipment documents.
02 / The evaluation
See the working product in a private demonstration, confirm the result you need, and discuss supply or a manufacturing partnership.
Choose the equipment, handling stage and events to investigate.
Agree sensor placement, settings and recording coverage.
Capture the trial, review events and inspect the equipment.
Share the report with photos, findings and handoff records.
Make the demonstration useful
One equipment or product type and a defined handling stage or route. Agree recording coverage, event settings and the inspection or claims-review workflow.
Discuss this evaluation →The final scope is agreed for your setup. A useful starting point includes:
Compare expected sessions with recovered sessions; document sequence gaps and missing records.
Record which events caused an inspection and what the receiver actually found.
Time the current review process and the pilot review using the same case definition.
Verify an original export, copy it to a reviewer workstation and confirm an altered copy is rejected.
Manufacturing, funding, licensing and distribution discussions are also welcome. Start with your role and proposed contribution; review the details privately with Dakota.
Discuss a partnership →For operations and inspection teams
Evaluate LoadClarity on a receiving check, equipment return or handling review. Agree the record your team needs, test it with your equipment, and measure whether it improves the work.
One equipment type, a defined handling stage and an agreed inspection process.
A handling recorder and the desktop workflow for configuring, reviewing and exporting the record.
A future monthly plan is being explored for organizations that manage records across people and cases.
The current desktop prototype supports one active sensor. Team accounts, hosted storage and integrations above are proposed services. A future subscription would be separately scoped and optional; the current kit proposal includes its described desktop workflow without a new recurring fee.
Inspection value: which recorded events led to a useful check. Review effort: time to prepare and hand over a report. Recording coverage: usable sessions and documented gaps. Agree the baseline and acceptance criteria before the trial.
03 / Work with the builder
Tell me what you need to learn. I’ll review the fit and help define a useful evaluation.
Pilot scope, hardware quantity, price and delivery are quoted after the fit review. Optional future team services are discussed separately. No charge to submit an inquiry.

04 / Before you decide
QR-assisted setup, four cargo profiles, packaging/route recommendations, 17 adjustable controls, searchable activity, incident grouping, severity and risk guidance, Decision Trace, delivery/review states, raw logging and report exports. Explore all eight capability areas above. Windows is the planned first supported release; the current desktop build allows one active sensor.
The current firmware retains up to 256 records. Stored replay reaches the raw log, but does not rebuild the desktop dashboard’s live decision timeline or score. Displayed timestamps are receive times, so precise offline event timing needs separate validation. We confirm capacity, coverage and recovery for the trial before promising journey reconstruction.
It summarizes configured rules and processed events to help prioritize inspection. It is not a measured probability of damage. A low score or high confidence label cannot certify an undamaged item or complete recording. The operator reviews coverage and physical condition.
The export includes a readable HTML report, PDF when its component is available, a CSV decision timeline, an export-time source snapshot and a packaged evidence record with file checks. Optional authentication requires trusted verification credentials. Photos and inspection documents are supplied separately.
No. It records a handling event within the sensor's measurement limits. Packaging, placement, thresholds and inspection determine how that event should be interpreted.
The recorded handling timeline can accompany photos, inspection findings and shipment documents in a claim or investigation. It helps reviewers examine events; it does not automatically establish damage, fault, coverage or claim acceptance.
Reports can be shared and checked for certain later changes. A private demonstration shows the review workflow and its limits. A report check is not an independent certification of the measurement.
The software can report certain device flags and check exported files for changes. Optional certificate authentication needs a configured secret key. The current firmware build does not enforce Bluetooth security, and PIN controls alone do not establish an encrypted link. Production security and physical tamper resistance must be validated; no tamper-proof claim is made.
Yes. The report captures come from the desktop application’s report generator and are excerpted for readability. Every figure is synthetic demonstration input, not a measured shipment or a claim of validated scoring. Open the full example report to see the other sections.
A separate mobile prototype supports Bluetooth events, recording controls, replay and quick tuning. A separate backend implements owner/device records and certificate checks. Neither is being promised here as a supported mobile release or a deployed cloud service. The current offer focuses on the desktop workflow.
The desktop keeps 500 activity rows and 600 Decision Trace rows in its review views. Raw received events append to a separate CSV, and an export-time raw-log snapshot can include multiple sessions. Review the report scope and supporting raw records before sharing. Exact per-event decision snapshots are also being refined before release.
Business pilots and hardware quantities are quoted after a fit review. The proposed kit includes the described desktop workflow. An optional monthly team plan is being explored for shared reports, case management and support; its features and price are not yet finalized or available. No subscription is started by an inquiry.
The product works and is available for demonstration. We are seeking funding and manufacturing partners for production. Fleet quantities, final specifications and delivery are agreed before an order is accepted.
Start with the problem you need to solve.
Discuss a business pilot ↗