Approval Workflow

How requests are reviewed

5 min read

The approval workflow ensures requests are properly reviewed before committing resources.

Who Can Approve

  • ADMIN โ€” Full authority
  • MANAGER โ€” Within their scope
  • SUPERVISOR โ€” For their teams

Tip

For emergencies, fast-track approval and immediately convert to a work order.

Configurable Workflow Engine

FreeMaint supports per-company approval workflows. Go to Company Settings โ†’ Workflows and add steps for Requests with different approver types.

Approver Types

  • ROLE โ€” any user with the specified role
  • USER โ€” one specific user
  • CREATOR โ€” the original requester
  • ASSIGNEE โ€” the assigned user
  • TEAM_LEADER โ€” team leader of the linked asset
  • REQUESTER_LOCATION_MANAGER โ€” the manager of the requester's location/section
  • TARGET_LOCATION_MANAGER โ€” the manager of the request's location/section
  • REQUEST_SECTION_MANAGER โ€” the manager (leader) of the request's Responsible Section (Team)

Required Fields per Step

Each step can require fields such as description, asset, location, category, photos, or any company-defined custom field (custom:<name>) before allowing the transition. For work-order completion you can also require a meter reading โ€” handy for hour-meter or odometer-based maintenance.

Rejecting a Request

A request can be rejected only while it is Pending or Under review. Once approved, a request automatically becomes a work order and can no longer be rejected โ€” cancel the resulting work order instead. If the Reject button is not shown, the request has already moved past the reviewable stage.

Quick Presets

Rather than building steps by hand, open Company Settings โ†’ Workflows, choose the Request tab, and apply a Quick preset: 'Manager approval before work order' for a single gate, or 'Two-level request approval' for a department review followed by a facility-manager approval. Each preset creates editable steps you can re-point to your exact roles.

Routing by Responsible Section

Approval can follow either where the work is (Location) or who is responsible (Section). For organizational responsibility โ€” Building, Electrical, Workshop, etc. โ€” model each section as a Team and set its leader as the section manager. Turn on the 'Responsible Section' field in your request form, then add a Request workflow step with the 'Section Manager (Team Leader)' approver. The request is then routed only to the manager of the section the requester selected, regardless of location โ€” one location can host work owned by several sections. For organizations whose responsibility really is location-owned, the 'Target Location Manager' approver routes by Location instead.

Auto-approve Emergency Requests

Open Company Settings โ†’ Workflows โ†’ Requests and turn on 'Auto-approve emergency requests'. When enabled, any request flagged as Emergency skips the approval workflow and a work order is created immediately. When disabled (the default), emergency requests follow the normal approval routing. Every auto-approval is recorded in the request history for traceability.

Seeing who approved or rejected

Once a request is approved or rejected, a banner at the top of the request shows who made the decision, when, and the rejection reason. This helps when several managers or maintenance planners can review requests. The same information appears in the request PDF and in the Activity tab.

Was this page helpful?