Best practices when using actions

Use clear, descriptive titles: The action title becomes the step title in reports and the main descriptor in the Operation Log. Avoid generic titles; be specific about what occurred.

Use the table view: Switch to Table view to access dropdowns and assign class code and crew to each action. This view also allows you to adjust time, add comments, and complete any missing fields, ensuring all data is correct before exporting reports. Read more about it here: Operation Log.

Document actions from the past when needed: If something isn’t logged live, use the Add historical action button in the Operational log. Just insert the action in a relevant place and adjust the timing to reflect reality. Read more about it here: Operation Log.

Favor frequently used actions: Mark commonly used actions and codes as favorites. This will help you find the right entries faster.

Use comments wisely: Comments provide context and support for each action. They're visible to supervisors and reviewers and can clarify details. Read more about it here: Comments.

Know who can do what: Only specific roles, like Drillers or Copilots, can create or edit actions. Ensure the correct person is logged in when making entries.

Equipment maintenance: The driller notices a minor equipment issue. They pause the ongoing step and add an action. Once completed, the original step resumes. Alternatively, if the driller can fix the issue offline, it will be added as a parallel action while the operation continues.

Retroactive documentation: A night shift team repairs a valve without logging it. In the morning, the supervisor adds a historical action, sets the correct time, and documents what happened for accurate reporting.

Using the table view: Switch to the table or log view to easily refine action details, such as adjusting time entries and selecting the correct codes.

Report logic: Reports round time to 15-minute intervals; any entry under 7.5 minutes will round down to zero.

Using generic actions: Users can start with an undefined action and later update it in the table view by assigning a clear title, the correct codes, and additional details, ensuring the final report accurately reflects the actual activity.

Missing or duplicate codes: Contact support if codes are duplicated or missing critical fields.

Export errors: Always check that the required fields (title, codes, crew) are filled before exporting.

Permissions issues: If you can’t edit or add actions, verify your role allows these changes.