I joined this competition to show a practical use case that solves a real problem for teams. I work with ServiceNow daily and see how much time goes into turning written policies into working processes. I wanted to build something that removes that workload and gives teams a fast, reliable way to create workflows. This led me to build Policytowork, an agent that reads policy text and produces complete workflows inside ServiceNow.

Title
Policytowork, a workflow builder powered by policy text

Overview
Policytowork takes policy rules and turns them into working ServiceNow workflows. It removes the manual effort teams deal with when they read long policies and then translate them step by step. The agent reads the text, identifies the rules, and builds the workflow so teams can move straight to execution.

Problem
When teams receive a new or updated policy, someone has to sit down, read every line, pick out the rules, decide how to model them, and then build the workflow by hand. This takes hours and often leads to missed steps or unclear logic. There is no quick way to move from policy text to a working process, which slows down adoption and compliance.

Solution
Policytowork turns policy text into a complete workflow in one run. The agent reads the document, detects rule statements, conditions, approvals, and exceptions, and builds the matching logic in Flow Designer. This gives teams a clean, consistent workflow without manual design.

What the agent does
• Reads policy text from a policy record
• Detects rules, exceptions, branches, and requirements
• Creates workflow steps in Flow Designer
• Builds approval sequences
• Sets role-based access
• Produces a summary of all actions and decisions

How it works
The user uploads or pastes the policy text. The agent scans each sentence and identifies what type of rule it describes. If it finds an approval rule, it creates an approval step. If it finds a condition, it builds a branch. If a role is mentioned, it adds access logic. The agent writes everything to Flow Designer and produces a summary record with the full interpretation.

Tools used
• Flow Designer actions
• Table operations
• Simple scripts
• Role lookups
• Approval actions
• Validation checks

Output
• A complete workflow with steps, branches, and approvals
• A summary record that lists all extracted rules
• A clean mapping of conditions, exceptions, and access rules
• Warnings when the policy text has missing or conflicting information

Why it matters
Policies change often, and teams need fast, reliable ways to implement those changes. Policytowork removes the manual translation step. Workflows become easier to maintain, and updates take minutes. Anyone can turn a policy into an operational process without needing to design the logic themselves.