Help Center

From the Active Holes dashboard, click the "Add Hole" button (administrators only). Fill in the required information including:

• Hole ID
• Project and location
• Planned depth
• Priority level and start date
• Workflow — your default workflow is preselected, but any can be chosen
• Optional steps — toggle on or off the optional steps this hole needs

Once saved, the hole appears on your dashboard in the Pending stage and moves to Drill / Markup as soon as drilled depth is recorded.

Yes. Administrators can select "Import" on the Active Holes dashboard and upload a CSV drill plan to create many holes at once.

• Only a Hole ID column is required
• Planned depth, project, location, rig, hole type, priority, start date and notes are all optional
• Projects, locations and rigs match an existing code or full description; values matching neither are listed and created for you
• Dates are read day-first; use YYYY-MM-DD to avoid any ambiguity

Your column headers don't have to match ours. CoreTrack matches them automatically, and every match is a dropdown you can correct. A preview shows exactly what will be created, and nothing is saved until you press Import.

Download the template from the import dialog for a file with the right headers already in place.

Every row in the preview carries a status, and only "Ready" rows can be imported:

• Ready — valid, and will be created
• Already exists — a hole with that ID is already in CoreTrack. Import never overwrites an existing hole
• Repeated in file — the same hole ID appears earlier in the file, so only the first is imported
• Invalid — a value couldn't be read, such as a missing hole ID or a depth that isn't a number. The row shows which

If a whole column looks empty in the preview, check the Columns panel above the table — that column may not be matched to a field yet. Pick it from the dropdown and the preview refreshes.

Step availability is controlled by your workflow's activation rules — not a fixed sequence. A step becomes active when its rule fires:

• "At hole start" steps activate as soon as drilling begins (drilled depth is recorded)
• Rule-based steps activate when their trigger step is started or completed
• A step with several rules activates when any one of them fires
• Optional steps left off a hole are skipped — the steps that depend on them activate as if they had run

To see or change the rules behind a step, open the workflow on the Configuration page and click the lightning bolt icon on the step.

Administrators can design workflows on the Configuration page. Every tenant starts with the Standard Core Logging workflow:

• Group steps into phases — these become the stages on your dashboard
• Drag steps between phases and reorder them freely
• Mark steps required or optional, and set each step's activation rules
• Flag one workflow as the default for new holes
• Use Copy to restructure a workflow that active holes are using

Validation on save ensures every workflow can run to completion — no unreachable steps or circular rules. Workflow allowances depend on your plan: Basic uses the standard workflow read-only, Professional can have up to 2 workflows, and Enterprise is unlimited.

To update hole progress:

• Find the hole on the Active Holes dashboard — use the search box to narrow it down
• Click the drilled depth on the hole card to record drilling progress
• Click a step name, or the Update Steps action, to record step values
• When recording a step, add an optional note (for example "waiting on assay lab") — it's captured in the audit trail with your name
• Steps activate automatically as their workflow rules are satisfied

Administrators can also complete a hole early — for example when drilling is abandoned short of the planned depth.

Yes — the dashboard has three views, switched from the toggle in its header:

• Stage Board — the familiar grouped view with stage summary tiles
• Yard Board — every hole as a row against every process step as a column, with the metres each step has reached; shows at a glance what the yard is queued behind
• Wall Board — every hole sized for legibility from across the room; goes full-screen and automatically cycles through them

Your chosen view is remembered on that device, so it reopens the way you left it.

On the Yard Board every step and the drilled depth carry their own last-updated stamp:

• TODAY — recorded during the yard's current day
• YDAY — recorded yesterday
• A date — anything older shows the day itself, because "3 days ago" makes you work out which shift that was
• No stamp — nobody has recorded anything against that step yet

A hole that looks busy but has not been touched in a week reads as exactly that. Sort the board by Needs review to bring the holes with the most un-updated steps to the top — the order to walk the yard in of a morning.

It counts the steps on that hole that are open and have not been updated today. Steps waiting on an earlier step are not counted, because nobody can work them yet, and finished steps are not counted either.

Steps that opened today are also left out. Recording metres can open several new steps at once, and doing the morning's work should never make a hole look worse than before you started — a step that opened an hour ago is not something anyone is behind on. It becomes countable tomorrow if nobody has recorded against it by then.

Because it should not. Drilled depth carries its own stamp under the depth bar, separate from every step. If one entry marked the whole hole as current, a morning depth reading would hide that Markup and Logging still carried last week's date — which is the problem per-step stamps exist to solve.

Each cell shows the day that work was actually last recorded, and only a save against that step changes it. Recording a step with no metres still counts as an update: opening a step to note why it has not moved — "saw down until Thursday" — is the most useful thing on the board to know is current.

The yard's day, not yours. Freshness is worked out in calendar days at the site using the Site Timezone set under Settings, so a supervisor in one city reading a board in another still sees the crew's day.

Work recorded at 11pm reads as YDAY to the crew arriving at 7am rather than as eight hours old — they are a day apart to the people doing the work, which is who the board is for. A wall display left running rolls its dates over on its own at the yard's midnight.

Yes — open Reports from the main menu and pick one of three:

• Daily Yard Report — a day's metres, what started, reached depth and finished, where the board stood at the end of that day, anything needing attention, and the notes your crew left
• Production Report — a week or swing rolled up, compared with the previous swing, split by rig and project, with the backlog's movement
• Hole Progress Report — one hole collar to dispatch, every step with its duration and who recorded it, for handing over with the core

Each report carries your organisation's details from Settings. Print downloads it as a PDF laid out for A4 and named for the period it covers, ready to file or email, or you can export the figures to CSV. Reprinting an earlier day shows the board as it stood then, not as it stands today.

The audit trail provides a complete history of all activities:

• Navigate to the Audit Trail page from the main menu
• Filter by date range, hole ID, operation type or user
• Expand a hole to see each change with timestamp, user, and the values before and after

The audit trail is maintained automatically for every data change — no manual logging required.

Administrators can align the weekly analytics with your roster from the Site Settings tab on the Settings page:

• Set the Week Start Day your swings change on (e.g. Thursday for Thursday-to-Thursday swings)
• Set the Swing Anchor Date — the first day of any past week worked by the first swing
• Optionally rename the swing labels (defaults are Swing A and Swing B)
• Optionally set a Site Timezone so everyone sees the same daily boundaries, wherever they log in from

The Weekly Recap on the Analytics page then starts on your chosen day and shows which swing worked that week, making swing-on-swing performance comparisons straightforward. Use the arrows to step back through past weeks, and the Compare button to overlay two consecutive weeks — one per swing — day by day.

Production totals measure the work done within the selected period. Marking, logging and cutting often happen days or weeks after the metres were drilled, so when the core yard is catching up on a backlog it is normal — and a good sign — for a period to show more metres logged than drilled. The opposite (drilling outpacing processing) builds the backlog up.

To see this at a glance, keep the Backlog overlay on the Analytics page turned on: the dashed lines show the metres drilled but still awaiting each step at any point in time. A rising line means that step is falling behind; a falling line means the yard is catching up.

Yes! CoreTrack is fully responsive and works on all modern mobile devices and tablets. You can:

• View and update hole progress from the field
• Access all dashboard information
• Review audit trails and analytics
• Manage libraries and workflows
• Keep recording field work while offline — changes sync when the signal returns

The interface automatically adapts to smaller screens for optimal usability.

Yes. Core yards rarely have reliable signal, so CoreTrack is built to keep working without one. Once you have signed in with a connection, you can go offline and:

• Keep viewing the dashboard, completed holes and recent audit history
• Record drill progress and step updates
• Complete holes and create new ones — a new hole shows an "Awaiting sync" badge until it reaches the server

Changes are saved on your device and sync automatically the moment the connection returns — the cloud icon in the top bar shows your status and how many changes are waiting. If the server can't accept a change at sync time (for example a teammate created the same hole ID), it is kept for your review: click the cloud icon to fix and retry it, or discard it.

Signing in for the first time, switching organisations and administration tasks (settings, users, workflows, billing) always need a connection.

Reference data is managed through the Libraries page:

• Go to Libraries from the main menu
• Select the Locations, Projects, Rigs, Bag Series or Hole Types tab
• Add a required Description and, if useful, an optional short Code
• Edit or delete existing entries from the grid actions

Be careful when deleting library entries, as this may affect existing hole records.

Go to Libraries and open the Hole Types tab. New sites start with an empty list, so add the classifications your program actually uses. Each one can have an optional compact code for the Yard Board as well as its full description. Renaming a type updates it everywhere, on past holes as well as new.

Deleting a type leaves the holes that carried it with no type at all, the same as deleting a project still in use. Rename it instead if those holes still need to read correctly.

If you upgraded from an earlier version, your holes keep exactly the type they were recorded under. Only legacy types already used by a hole are added to the library, with their RD, EXP or GC code.

Problem: Can't log in to the system

• Check your username and password
• Ensure Caps Lock is off
• Try clearing your browser cache
• Contact your administrator if account is locked

Problem: Changes aren't being saved

• Check for validation errors (red text)
• Ensure all required fields are filled
• Verify you have edit permissions
• Try refreshing the page and re-entering data

Problem: Processing steps won't activate

• Record drilled depth if drilling has begun — "at hole start" steps need it
• Check the step's activation rules in the workflow on the Configuration page
• Start or complete the trigger step the rule points at
• Refresh the page to update step status

Problem: A hole won't move to the next stage

• The stage follows the earliest incomplete step — check for one still outstanding in that phase
• Optional steps count too: complete them or remove them from the hole
• Flag drilling as complete to move the hole out of Drill / Markup

Problem: After reconnecting, the top bar shows changes that "need review"

• Click the cloud icon in the top bar to open the Offline Changes list — each held change shows the reason
• A duplicate hole ID: open the hole, rename it, and it retries automatically
• A change recorded under a different user or organisation can only be synced by that user — or discarded
• Later changes to the same hole are held back until the earlier one is fixed or discarded

Nothing is lost silently — every change waits for your decision, and the audit trail records what was applied.