Synchra.24
menu_bookDocumentation
Practical guides for setup and development

Find guides for getting started, building workflows and adding your own tools to your company workspace.

folderAdministrator

Application templates

How to prepare application templates for employees and set up a single application scenario.

Machine translation

Application templates are needed so that employees send requests in a clear and uniform form. Instead of free text, you set the structure of the application in advance, and this helps to process requests faster within the company.

What is this section for?

The application templates section helps:

  • set a single format for internal requests;
  • reduce the chaos in employee applications;
  • send requests to the right people faster;
  • collect only the really important fields.

For example, you can use templates to create:

  • request for a vacation;
  • request for supplies;
  • contacting technical support;
  • request for purchase approval;
  • an internal service request for the facility or department.

What gives a template in practice

When the template is created, the employee does not write an application from scratch, but selects the desired type of request and fills out the ready-made form. This is convenient for both the employee and the manager.:

  • the employee understands exactly what is required of him;
  • the manager receives the message in an understandable format;
  • The number of incomplete or vague applications is decreasing.

What is usually configured in the template

Depending on your scenario, the application template may include:

  • Application name;
  • description;
  • list of required fields;
  • tips for an employee;
  • the logic of further processing.

The main task of the template is to make sure that a person does not think about how to write an application correctly, but simply fills in the necessary data sequentially.

How to create an application template

Step 1. Open the Application templates section

Go to the admin section and open Application templates.

Step 2. Click the add button

In the upper-right corner, click Create a new template.

Step 3. Enter a clear name

The name should be obvious to the employee. Formulations like:

  • Request for leave
  • Request for consumables
  • Request for technical support
  • Request for purchase approval

Step 4. Consider the composition of the fields

Before creating a template, you should answer a simple question: what information should you get from the employee so that you can work on the application immediately.

Most often it is:

  • brief description of the situation;
  • date or period;
  • application category;
  • the amount, if we are talking about expenses;
  • comment or additional details.

Step 5. Make only the required fields mandatory

Do not overload the form. If the field does not affect the processing of the application, it is better not to make it mandatory. The simpler the form, the higher the chance that employees will fill it out carefully.

Step 6. Save the template

After saving, the template becomes available in the employee workflow.

How to keep the templates in order

Over time, the list of templates almost always grows. Therefore, it is useful to check regularly.:

  • what patterns are actually used?;
  • which ones are outdated;
  • which ones are similar to each other and duplicate the meaning.

If the template is no longer needed, it is better to remove it from active use than to leave it in the list just in case.

How to tell if a template is good

A good application template:

  • it is clear to the employee at a glance;
  • It does not require lengthy explanations;
  • collects only useful data;
  • helps to make a quick decision on the application.

If, after launch, employees often ask questions about what to write here or why this field is needed, then the template should be simplified.

When should I make separate templates?

A separate template is useful if:

  • the request has its own set of required fields;
  • The application follows a separate approval route.;
  • Other responsible people are working on it.;
  • it has a different meaning and a different processing logic.

If only the wording differs, and not the process itself, it is better not to create unnecessary templates.

Practical advice

It's better to start with a few of the most frequent requests that employees actually use every day or every week. After that, you can add more rare scenarios.

A convenient starter kit usually looks like this:

  1. vacation;
  2. supplies;
  3. internal technical problem;
  4. business application;
  5. cost coordination.

This way you'll get a working result faster and won't overload your employees with too many choices.