We’re pushing 70–80 m/shift on an NQ diamond rig and my paper-to-Excel workflow can’t keep up — what are you using to log core and push intervals to planning before the 6 a.m… toolbox? I need offline tablet logging, fast lith/struct templates, orientation data from a Reflex ACT III, and photos that sync when we get back to camp Wi‑Fi so the drill plan can adjust by noon. Bonus if it ties DDR meterage and sample tags without another night in the core shed.
At 70–80 m/shift we switched to MX Deposit offline on a Toughpad with a “2‑tap lith/struct” template, tied to IMDEXHUB‑IQ so ACT III orientations flow in automatically; photos go via Imago Mobile and sync at camp Wi‑Fi, then we push a CSV to planning before the 6 a.m. toolbox. It’s pricier and HUB setup takes an hour the first time, but the speed jump was worth it — want the template and export script?
Biggest speed hack for us was QR stickers on every box (HOLE_BOX_FROM-TO) and a watch‑folder in Geobank Mobile + Imago so photos auto‑attach when camp Wi‑Fi hits; ACT III comes via IMDEXHUB‑IQ and snaps to interval midpoints, but make sure both sides round to 0.01 m or the merge misses. “hour the first time, but the speed jump was worth it — want the template and export script?” — I can send my template and a tiny filename‑renamer if you want?
We stopped chasing exports and set a 3 a.m. FME (https://www.safe.com) job that pulls the overnight log from the tablet’s SQLite and posts intervals to Seequent Central so Leapfrog refreshes before toolbox; only gotcha was making the tablet dump its cache to a network share on reconnect — do you have Central or want the CSV-to-Teams variant?
To make the 6 a.m. toolbox, we borrowed @chris_ada83’s FME idea and set a 30‑min “provisional push” that exports just the last tray’s lith/struct plus Reflex orientation (timestamp‑matched) to Central, then the full log posts when we reconnect at camp. Tiny caveat: use a lapel mic or on‑device voice dictation gets messy in the core shed, but it speeds the descriptive bits a lot. Do you already have Central, or would a lightweight webhook to Fusion be easier?
At “70–80 m/shift,” don’t wait on full lith — publish box-close events only (from–to, recovery, Reflex orientation) straight off the tablet, then push lith/struct on a second pass; MX Deposit works offline and fires an API hook so planning has depth by 5:30 and photos queue for later when you’re back on network. If you’re not on MX, IMDEX HUB-IQ + IQ-LOGGER is similar — want the template JSON I use for rapid veining/alt?