How the record moves
Follow the record from requirement to recurrence.
The requirement that makes work due stays connected to the asset, assigned job, field evidence, quality decision, finished packet, retained record, and next obligation.
Five operating stages move the work. The nine connected record objects at right show what preserves its operating history.
The complete path
The full cycle remains connected before, during, and after the field job.
- Asset
- Rule
- Obligation
- Job
- Evidence
- Quality control
- Packet
- Record
- Recurrence
Each handoff adds context to the same operating history.
Inside the operating record
Open any object to see what changes and what carries forward.
Conceptual record-object explorer. Start with the asset, then follow the nine connected record objects to see how each one adds context to the cumulative record beside it.
Record object
Asset: identify what the requirement applies to.
- Purpose
- Identify the asset that the approved program applies to.
- Who acts
- Program owner or asset manager.
- What enters
- Asset identity, type, location, operating context, and program tags.
- What the platform carries
- Asset context and its relationship to the program.
- What joins the record
- The identified asset and the context that frames later work.
- What becomes available next
- A stable asset context that can be evaluated against an approved rule.
- Human responsibility
- Your organization confirms the asset identity and scope.
Record object
Rule: connect the asset to the approved program requirement.
- Purpose
- Carry the source, cadence, conditions, and approved applicability decision.
- Who acts
- The people responsible for program configuration and approval.
- What enters
- The approved source, applicability conditions, cadence, and required outcome.
- What the platform carries
- The organization-approved rule definition and its versioned context.
- What joins the record
- The governing context used to explain why work becomes due.
- What becomes available next
- The basis for a dated obligation.
- Human responsibility
- Your organization interprets and approves the program requirement.
Record object
Obligation: make the recurring requirement visible as due work.
- Purpose
- Turn approved asset and rule context into a dated operating requirement.
- Who acts
- Operations and program administration.
- What enters
- Asset, approved rule, recurrence, work window, and due context.
- What the platform carries
- The relationship between the requirement, timing, and the asset it concerns.
- What joins the record
- A visible obligation with its source and recurring context attached.
- What becomes available next
- Due work ready to be planned as a job.
- Human responsibility
- Timing and applicability follow your approved configuration.
Record object
Job: turn the obligation into assigned field work.
- Purpose
- Move due work into a scope that can be scheduled, assigned, and completed.
- Who acts
- Operations, scheduling, and the assigned field team.
- What enters
- The due obligation, scope, location, assignment, and evidence expectations.
- What the platform carries
- Why the job exists and what the approved program expects from it.
- What joins the record
- The field-ready job and its relationship to the obligation.
- What becomes available next
- A clear evidence collection path for the field team.
- Human responsibility
- Operations controls assignment, timing, and execution.
Record object
Evidence: keep what happened connected to the job.
- Purpose
- Preserve the submitted material needed to understand the completed work.
- Who acts
- Field personnel and the people responsible for the work.
- What enters
- Readings, photos, forms, notes, source, time, location, asset, and job context.
- What the platform carries
- The relationship between submitted material, the job, and its requirement.
- What joins the record
- A reviewable evidence set with its operating context attached.
- What becomes available next
- The submitted evidence and context required for quality review.
- Human responsibility
- The people doing the work remain responsible for accurate capture.
Record object
Quality control: record approval, return, and correction together.
- Purpose
- Review the submitted evidence against the criteria approved for the program.
- Who acts
- A qualified reviewer with the appropriate responsibility.
- What enters
- Evidence, reviewer, criteria, decision, and any return reason or correction.
- What the platform carries
- The review state, decision history, and connection to corrected evidence.
- What joins the record
- An approved or returned evidence state with its decision context.
- What becomes available next
- Approved material ready for the prepared packet.
- Human responsibility
- A qualified person makes the review decision.
Record object
Packet: assemble the approved material into a prepared output.
- Purpose
- Bring the approved evidence and required output structure together.
- Who acts
- Administration and the people responsible for release.
- What enters
- Approved evidence, decision context, and the approved packet structure.
- What the platform carries
- The relationship between the prepared output and the work that produced it.
- What joins the record
- A prepared packet connected to its source evidence and decision.
- What becomes available next
- A finished output ready for approved release and retention.
- Human responsibility
- Your organization controls release, delivery, and direct submission.
Record object
Record: retain the complete operating history, not only the packet.
- Purpose
- Keep the governing context, work, evidence, decision, and output understandable together.
- Who acts
- Administration and authorized record owners.
- What enters
- The obligation, job, evidence, correction history, decision, and prepared packet.
- What the platform carries
- The connected history from source requirement through finished output.
- What joins the record
- A retained operating record that can be understood from requirement to decision.
- What becomes available next
- The prior cycle context needed to continue the program.
- Human responsibility
- Access, retention, and release follow your approved policies.
Record object
Recurrence: carry approved context into the next obligation.
- Purpose
- Continue the operating cycle without rebuilding the prior history.
- Who acts
- Operations and program administration.
- What enters
- The completed cycle, retained record, and approved recurrence.
- What the platform carries
- The context that connects the next obligation to the work already completed.
- What joins the record
- The next obligation and its relationship to the prior cycle.
- What becomes available next
- A new operating cycle with the existing context intact.
- Human responsibility
- Your organization approves cadence and any program change.
Record so far
Cumulative record ledger
- 01AssetCurrent object
- 02RuleConnects later
- 03ObligationConnects later
- 04JobConnects later
- 05EvidenceConnects later
- 06Quality controlConnects later
- 07PacketConnects later
- 08RecordConnects later
- 09RecurrenceConnects later
Object 1 of 9: Asset is the current object in this conceptual model.
Record anatomy
The finished packet is part of the record, not the whole of it.
- Governing context
- Asset facts, approved requirement, source, cadence, and conditions.
- Execution context
- Assignment, location, people, readings, photos, forms, and notes.
- Decision context
- Reviewer, decision, correction reason, accepted evidence, and release state.
- Finished output
- The prepared packet and its relationship to the work that produced it.
- Next cycle
- Approved recurrence and the context used by the next obligation.
The controlled exception
Correction stays attached to the job that required it.
Quality control can approve the submitted evidence or return it with a reason. The original submission, correction, and final decision remain connected to the same job history.
- Submitted evidence
- Review
- Returned with reason
- Corrected evidence
- Approved packet
A qualified person still makes the decision. The platform records it and carries it forward with the job.
What changes by program
The path stays stable. Program requirements change.
Stable operating structure
- The record path and sequence
- Role-based responsibilities
- Evidence and decision steps
- Retention and recurrence
- Continuous lineage across cycles
Reviewed program configuration
- Rules and applicability
- Obligation schedules
- Evidence and criteria
- Packet contents
- Industry and regulatory needs
Clear ownership
Configuration carries decisions. It does not make them.
- The platform carries
- Requirements, context, evidence, decisions, records, and recurrence.
- Your organization decides
- Who performs the work, who reviews the evidence, and who signs the decision.
- The record preserves
- What was required, what happened, who decided, and what comes next.
The platform does not provide legal, engineering, or regulatory advice. Your organization remains responsible for its program and decisions.
Choose the next depth
Get the answer you need before you choose.
Continue with the question that matters to your decision.
Next: workflow fit
Discuss how the connected record fits your program.
Tell us the capabilities and configuration your team needs, or compare the plan paths that fit the way your operation works.