How to use CoreYard efficiently
CoreYard works best when data is loaded in the right order. Start with organization and project structure, then load holes and assets, use the map to verify spatial data, and move into CoreYard logging and operational workflows once the register is stable.
Recommended setup order
Follow this sequence to avoid rework and missing links between records.
Create or choose your organization
Everything in the app is scoped to an organization first. If the user is still in the demo org, they should create or join their real org before loading production data.
Create the project and set the CRS
Projects are the parent records for holes and assets. The coordinate reference system should be configured here before loading any projected locations.
Add supporting reference data
Before field data starts arriving, set up the supporting records that downstream workflows expect to reference.
Load holes and assets into the project
Holes and assets should be attached to a project as early as possible. That keeps mapping, logging, scheduling, and reporting aligned.
Use the map to verify and work spatially
Once holes and assets have coordinates, the map becomes the fastest way to inspect records, move locations, create new spatial records, and jump into CoreYard.
Run CoreYard workflows
CoreYard is where users manage holes, logging, dispatch, and core task progress. This area should be used after the project and hole register are in place.
Capture operations, consumables, and schedule
Operational workflows become reliable after org, project, hole, and resource structures are already in place.
What data needs to exist, and in what order
This is the practical dependency chain taken from how the app loads records today. If users populate data out of order, they usually feel it first in the map, CoreYard, and scheduling flows.