Skip to content
  • documentacion ats
  • guidelines

Manual Guidelines

Mandatory guidelines

Section titled “Mandatory guidelines”
  • Define the purpose of each module with clear language without unnecessary jargon.
  • Always explain the flow as if for someone new to the ATS.
  • Include objectives, numbered steps, referenced screenshots, and best practices per section.
  • Document common errors and relevant use cases to guide daily operations.
  • Maintain consistency across modules: titles, list formatting, and tone should be homogeneous.
  • Validate that examples and links work before publishing changes.
Section titled “Recommended structure per module”
  1. Module Name – Visible identifier within the ATS.
  2. Objective – Role of functionality within the recruitment process.
  3. When to Use – Time in the operational flow when it applies.
  4. Step-by-Step – Numbered actions from access to completion.
  5. Screenshots – Numbered images that support the described journey.
  6. Best Practices – Operational tips that avoid reprocessing and loss of information.
  7. Common Errors – Scenarios that should be avoided and how to resolve them.

Each new page should follow this order and, when necessary, add subsections that delve into specific functionalities (for example, filters, exports, or automations).