CLEARCURRENT FIELDOPS · READ ME

One controlled workflow from preparation to handover.

ClearCurrent connects project setup, planning, field execution, quality evidence, progress, reporting and handover. Information is captured once at the source and reused without losing responsibility, revision or audit history.

THE CONTROLLED WORK CYCLE

Configure → Plan → Execute → Verify → Report.

Every module supports the same project lifecycle. A screen is only useful when the next controlled action is clear.

1

Configure

Projects, assets, teams, shifts, activities, documents, templates and rights.

2

Plan

Scope, locations, assignments, prerequisites, access and readiness.

3

Execute

Field steps, measurements, photos, tests, issues and offline capture.

4

Verify

Supervisor, QA and client review against the frozen controlled revision.

5

Report

DPR, progress, quality close-out and handover from approved source records.

CORE WORKSPACES

Choose what you want to do.

Each workspace has a clear purpose and should direct the user to the correct next step.

WORKSPACE

Progress

See reported progress, verified progress, blockers and the next controlled action.

WORKSPACE

Planning

Prepare upcoming scope, teams, shifts, access and work-package readiness.

WORKSPACE

Reports & Work

Complete controlled field templates with measurements, photos, signatures and evidence.

WORKSPACE

Daily Progress Reports

Record people, resources, delays, completed work and next-shift priorities.

WORKSPACE

Quality

Raise Field Issue Report Forms, manage NCRs and verify corrective actions.

WORKSPACE

Handover

Generate controlled outputs from approved project records without re-entering data.

ROLE-BASED EXPERIENCE

People see what they need—not every system option.

Administrator

Configures projects, assets, users, teams, documents, templates and access.

Supervisor

Coordinates assigned work, readiness, execution, issue routing and review queues.

Field user

Sees only named assignments and the controlled information required to complete them.

QA / client reviewer

Reviews submitted evidence, records decisions and verifies close-out.

CONTROL PRINCIPLES

What ClearCurrent will never change silently.

Immutable history

Approved reports and published templates retain the revision and evidence used at the time.

Server-enforced access

Project, role, team, scope and named-user rules are enforced by the server—not only hidden in the interface.

Controlled improvement

Learning signals can recommend an improvement but cannot publish a template, procedure or MOC.

Reported versus verified

Imported progress can be visible immediately while proven completion remains a separate controlled measure.

FIELD ISSUE CONTROL

FIRF means Field Issue Report Form.

Use it for a non-HSE issue identified during field execution that requires Project Engineer review but has not yet been classified as an NCR, MOC or Technical Query.

Possible review outcomeNo further actionCorrective actionNCRMOCTechnical Query