TechAppForce

High-stakes industries

Energy asset work clearance

Coordinate asset work, permits, crew checks and control-room review in a visible record.

Illustrative permit coordination only. It does not execute grid switching or replace an organisation’s safety controls.

Book a demoSee how it runs
  1. Requested
  2. Planning
  3. Permit reviewApproval
  4. Ready for work
  5. Work in progress
  6. Hand-back reviewApproval
  7. ClosedDone
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
Planned work on a substation or transmission asset involves a site, an outage window, a crew and several checks. If the permit, supporting documents and reviews are split across calls and spreadsheets, planners struggle to see readiness and hand-back status.
Who feels it: Utility maintenance planners, field crews and operations reviewers

How it runs on TechAppForce

A day with it, step by step

Amber steps wait in a person's work inbox; everything else moves on its own.

  1. Work is requestedA planner links a maintenance request to an asset, site and requested work window.
  2. Permit details are gatheredThe crew lead records the work scope, hazard controls and the documents required for review.
  3. Readiness is reviewedOperations sees what is complete, what is missing and who owns each remaining check.
  4. Work and hand-back are recordedOperations reviewAfter work, the planner collects a separate hand-back review and records any follow-up.
  5. History is ready to inspectThe work record keeps the request, permit, reviews and timeline together for internal reporting.
Illustration. The organisation and people are invented.

What gets configured

Settings you can read, change and release

No code for any of this, unless a rule truly needs it.

Records 5

  • Asset4 fields + history, files, comments
  • Work request4 fields + history, files, comments
  • Permit4 fields + history, files, comments
  • Crew check3 fields + history, files, comments
  • Clearance review3 fields + history, files, comments

Stages 7

  1. Requested
  2. Planning
  3. Permit reviewdecides
  4. Ready for work
  5. Work in progress
  6. Hand-back reviewdecides
  7. Closed

Automatic 3

  • NotifyA requested work window notifies the site planner and operations review team
  • NotifyA missing readiness check keeps the permit in the review queue and alerts its owner
  • ScheduleA daily board groups planned work by asset, site and requested window

Screens and reports 5

  • Maintenance planning board by site, asset and requested date
  • Permit form with hazard controls and linked work documents
  • Operations review inbox with readiness and hand-back decisions
  • Planned work by asset and outage window
  • Permit review and hand-back history for internal governance
Who approves, in detail

The operations reviewer checks the permit information and requested window before the work is marked ready. Hand-back is a separate review with a recorded decision and any open follow-up.

When the rules change

Bring your version of this.

A change a few months in is a reviewed release, not a rebuild. We will configure your version with you in a demo.

Book a demoAll use cases

Release: Permit: work window review

Readiness
Added: + Crew check complete
Added: + Hazard controls attached
Hand-back
Unchanged: Work complete
Added: + Separate operations review
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release
Illustration.