> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/digitalworkers/ifs-loops-digital-workers/digital-worker-guides/closeout-and-improvement-manager/faq.md).

# FAQ

### Capabilities & functionality&#x20;

**Q: What does the Closeout and Improvement Manager do?**&#x20;

A: The Closeout and Improvement Manager is a Digital Worker that runs maintenance work order closeout end-to-end. It retrieves full work context, assesses documentation quality, validates planned work against actual, detects follow-up work and improvement opportunities, recommends maintenance where needed, authorizes work tasks, validates asset integrity, and closes the parent work order with a generated summary.&#x20;

**Q: Does it only catch problems, or does it also review work that looks clean?**&#x20;

A: It reviews every task in full, including ones where the reported hours match the plan exactly. A clean match on the numbers is exactly the kind of task most likely to get only a quick look in manual review, which is why the Digital Worker reads the full remarks regardless of how clean a task appears.&#x20;

**Q: How does it find follow-up work that isn’t flagged explicitly?**&#x20;

A: It analyzes technician notes and observations using AI to detect new defects, anomalies, incomplete work, or recurring issues, including ones mentioned only in passing in free-text remarks rather than raised as a separate structured finding.&#x20;

**Q: What happens when a follow-up issue is found?**&#x20;

A: The worker first confirms no additional records already exist for the issue, then opens the appropriate follow-up, such as an inspection, and can also raise a maintenance change request when the finding points to a broader configuration or maintenance-strategy question.&#x20;

**Q: Does the Closeout and Improvement Manager close the work order itself?**&#x20;

A: It closes the parent work order once every child task is completed and authorized and no follow-up action or maintenance change request is still pending, generating a closeout summary with the key decisions and insights behind it.&#x20;

### Control & Collaboration&#x20;

**Q: Does every work task get auto-authorized?**&#x20;

A: No. A work task is auto-authorized only once it passes every validation check. Anything that falls outside tolerance or needs judgment is routed for human-in-the-loop review instead.&#x20;

**Q: Who reviews an exception the Closeout and Improvement Manager raises?**&#x20;

A: The supervisor, planner, or reliability engineer relevant to the finding, depending on whether it’s a work task authorization exception or a maintenance recommendation awaiting approval.&#x20;

**Q: What does a supervisor see when reviewing a flagged item?**&#x20;

A: Exceptions are surfaced with an explanation, so a supervisor can approve, reject, or clarify the decision rather than having to reconstruct the reasoning behind the flag themselves.&#x20;

**Q: How are closeout decisions communicated to the team?**&#x20;

A: Notifications are sent through Microsoft Teams and email, and a closeout summary capturing the key decisions and insights is generated for every closed work order.&#x20;

### Integration & Technology&#x20;

**Q: What systems does the Closeout and Improvement Manager integrate with?**&#x20;

A: It integrates with IFS Cloud’s Enterprise Asset Management and Maintenance modules as the primary system of record, Microsoft Teams and Outlook/Email for notifications and exception review, and other enterprise systems as configured for the deployment.&#x20;

**Q: What data does it pull when reviewing a completed task?**&#x20;

A: The work task, work order, asset, technician, and plan details, along with labor, materials, services, tools, measurements, and notes, enriched with the asset’s history and past maintenance context.&#x20;

**Q: What triggers the Closeout and Improvement Manager to begin reviewing a task?**&#x20;

A: A technician completing a work task in IFS Cloud triggers the worker to retrieve full work context and begin the review.&#x20;

**Q: Does it validate asset records as part of closeout?**&#x20;

A: Yes. It validates the asset hierarchy and tracks serialized install, removal, and return actions, confirming asset integrity before the parent work order is ready to close.&#x20;

### Security & Reliability&#x20;

**Q: How is documentation quality assessed consistently?**&#x20;

A: The same evaluation applies to every task: technician remarks, actions taken, and findings are scored for completeness and clarity using a consistent documentation quality assessment, rather than depending on how much time a reviewer had.&#x20;

**Q: What keeps a variance from slipping through unnoticed?**&#x20;

A: Reported labor, materials, services, and costs are checked against configurable tolerance rules on every task, and anything outside tolerance is identified as a variance or exception rather than silently passed.&#x20;

**Q: Is there an audit trail for closeout decisions?**&#x20;

A: Yes. The audit trail and closeout history are recorded as part of Work Order Closeout, alongside the generated closeout summary capturing the key decisions and insights behind it.&#x20;

**Q: How is governance enforced across different supervisors and sites?**&#x20;

A: The same policies, approval rules, tolerance limits, and asset hierarchy validations are applied consistently to every work task, regardless of who completed it or which supervisor would otherwise be reviewing it.&#x20;

### Customization & Performance&#x20;

**Q: Can tolerance rules be configured?**&#x20;

A: Yes. Planned versus actual validation, covering labor, materials, services, and costs, is checked against configurable tolerance rules rather than a fixed threshold.&#x20;

**Q: What kind of maintenance recommendations can the Digital Worker raise?**&#x20;

A: A work request or fault report for a new issue, or a maintenance change request when a finding points to a broader process, configuration, or maintenance-strategy question, routed for approval to the relevant supervisor, planner, or reliability engineer.&#x20;

**Q: What visibility does the Closeout and Improvement Manager provide beyond individual work orders?**&#x20;

A: Dashboards provide insight into work status, exception trends, improvements, and closeout performance, giving supervisors and reliability engineers visibility into bottlenecks and recurring issues across the maintenance team.&#x20;

**Q: What are the five core skills behind the Closeout and Improvement Manager?**&#x20;

A: Work Context & Quality Assessment, Work Validation & Authorization, Follow-up Work & Improvement Detection, Maintenance Decision Closeout, and Closeout Summary & Notification. Together, they take a completed task from initial review through to a closed work order.&#x20;