Skip to content
English
Customer portal
Go to fldata.com
  • There are no suggestions because the search field is empty.

Evaluation Requirements

Evaluation requirements are tasks completed before an MOC is can start approval. They help the originator decide whether to move forward with the MOC, void it, or adjust its scope based on a risk/benefit analysis. A well-designed evaluation checklist can also help originators select the right profile and give approvers the information they need to make a sound approval decision.

Key Features

Management

  • Only MOC Power Users and Super Users can create and configure evaluation requirements. You'll find them under Settings > Requirements > Evaluation. 

Scope

  • Requirements can apply to a specific division or across your entire company.
  • To make a requirement company-wide, leave the Division field blank.

Attachments

  • You can attach an Smart form or checklist, or link to a network document via URL — but not both at the same time.

Mandatory vs. Recommended

  • Within a profile, requirements can be set as mandatory or recommended.
  • For high-risk areas of a process, consider making certain evaluation requirements mandatory in those profiles.

Assignment

  • Requirements can be assigned to an individual or a job role.
  • Assignees can transfer their task to another person if needed.
  • You can set a default Evaluator — useful when the same person always handles specific evaluation tasks for certain MOC categories.
  • The MOC originator can also be set as the default Evaluator.

Verification

  • A verifier can be added. Once a task is completed, it moves to the verifier's desktop for review. The verifier can complete/approve or transfer the task to a new individual or back to the original evaluator.

Due Dates

  • Set a due date by entering a number in the Days to Complete field under MOC > In Process > Evaluation.
  • The due date is automatically calculated when the task is assigned:

    Days to Complete + Date Assigned = Due Date

  • Administrators can set default Days to Complete values in MOC profiles.

Action Items

  • Every requirement includes an Action Items button, which lets you create and assign follow-up action items directly from the requirement.

How to Create an Evaluation Requirement

  1. Go to Settings > Requirements > Evaluation and click New in the toolbar.
  2. Enter a Title for the requirement.
  3. Add an optional Description to provide more detail.
  4. Attach a form or document (optional — choose one, not both):
    • Form: Select from the drop-down and click View to confirm it's correct.
    • Document: Click Choose File, browse for your file, and select Open. After saving, a View link will appear so you can verify it.
    • Can be completed after creating the MOC – The task can be closed once the MOC is submitted.
    • Must remain open until MOC is closed out – The task stays active on the assignee's desktop until the full MOC is closed.If you wish the requirment to create a new MOC, check the Create MOC box and choose how the task should work:
  6. Check Require Attachment if the assignee must upload a file before completing the task.
    • Only one attachment is allowed when marking a task Complete. However, assignees can add additional attachments by saving progress multiple times (up to the limit per entry).
  7. Set the Evaluator (optional):
    • Originator – Select "Originator" from the Evaluator Type drop-down.
    • Specific person or job role – Select "Individual" or "Job," search for the person or role, and click OK. To narrow to a specific user within a job, click the group icon to see a list of assigned users.
  8. Confirm the Company and Division are correct.
    • Division-specific: Select the appropriate Division.
    • Company-wide: Leave the Division field blank. This is typically used for standardized requirements across all divisions. In this case, it's recommended to leave the Evaluator field blank until the requirement is added to a division-specific profile.
  9. Click Save. The requirement is now available for use.

Tip: If you haven't created the form you want to attach yet, save the requirement without one, build the form, then come back and edit the requirement to attach it.