Take the case of Helen, the head designer at her company. Helen and her team handle brochure, UI icon, and visual effect designs that are requested by teams like marketing and user education.

When Amy, the head marketer, requests a new batch of brochures, she walks up to Helen and has a chat about it. Helen, in turn, assigns this task to a member of her team. To track the progress of the task, Amy will have to depend on Helen, who will request status updates from her team.

In endless series of discussions, even a small communication lapse could cause serious problems, and following up on the task becomes a tedious activity. This game of phone tag between Helen, Amy, and her teams eats up productive time and turns minor issues into major delays.

More likely than not, this is how your processes work too. To run them more efficiently we've come up with a software that can meet all your business needs — Qntrl!

Qntrl provides a 4-step wizard called Orchestration, using which your organization's end-to-end workflow can be automated in one-go. Before diving in, let us get to know the terminologies used in Qntrl. 

Form : A layout to collect details of the workflow

Blueprint : A canvas to design the steps involved in the workflow

Card : A request raised to perform the workflow

Plan your approach using Forms       

Forms help you channel all the data about a particular set of tasks in a single place. Design your form in Qntrl   by adding the necessary fields to procure data from the users most likely to raise a request using Card. 

How does this help Helen?

Helen can now create forms for every task that her team performs. She can also restrict access to certain fields like 'Brochure feedback' or 'Rating' from specific members of the team.  

Design your workflow using Blueprint

Blueprint helps you decide the flow of your process. You can design a flowchart pipelining individual  stages and  transitions that build a path to reach these stages. This helps even new members of the team adapt to processes quickly. 

Set permissions and review the orchestration

Helen gains control!

Helen can restrict permissions for creating and accessing cards. For instance, the privilege to put a task on hold can be restricted to specific users even before the task starts. 

Create a request using Card

When a user wants to request your orchestration, they can create a  card . The progress of this card can be monitored at any point of time in Qntrl. 

Visualize your progress using Reports

Reports help you gain insights on your organization's progress. We provide you with a set of default reports but you can also design your own custom ones.  

Community forum posts you might be interested in: 

1. A sample scenario to automate business processes using Qntrl
   
2. Workflow orchestration for your business using Qntrl
   
3. Spreadsheets vs Qntrl to manage your organization
   
4. How Qntrl uses Qntrl for remote work
   
5. Stay informed of significant business impact using Qntrl