Clear and consistent instructions are key to maintaining high translation quality.


However, in today’s continuous localization workflows, projects are often small but frequent, which means writing detailed instructions for each one can quickly slow you down.



1. Why instructions matter

Instructions can vary depending on:

  • The end client

  • The content type or program name

  • The target language (especially if there are separate style guides)


If this is your case, you can manage these variations through exceptions in BeLazy.


For example, you can include:

  • Links to style guides or reference materials

  • URLs for translators to access online workspaces directly, so they can start immediately



2. What instruction mapping does

In BeLazy, instruction mapping isn’t just for translator notes, it’s a flexible system that helps manage text fields at every level:

  • Project / Order

  • Task / Item

  • Job


You can combine your own custom text with information coming from the source system.
For example: “Please process the files here: [URL from system]”


BeLazy automatically fills in the right data (metadata) for each project.



3. How to configure it

Depending on your business management system (BMS), you’ll see different fields available.


BeLazy provides default examples to help you start, but you can fully customize them.

  • Gray fields show existing configurations, click the arrow to expand and view details.

  • On the left, you can edit text or add metadata using the @ button.

  • On the right, you’ll see a preview showing how your instructions will look with real project data.


If a value appears empty or incorrect, just replace it with another metadata field or remove it.




4. Using exceptions

Exceptions help you create custom instructions for specific cases, for example, for a particular end customer.

Here’s how:

  1. Make sure you’ve selected a field (like End Customer) under Properties to use as metadata.

  2. Create a default instruction for all other projects.

  3. Click Add rule, then define something like:
     If End Customer = [specific client]

  4. Write the special instruction for that client and click Finish.


This feature is especially useful for vendor instructions but can apply to any text field.



5. Field recommendations per system

Depending on your BMS, some fields are more important to configure:

  • Plunet:

    • If you’re using bundling, make sure to fill out the Item description with the opportunity name or ID.

    • Optionally, use Item comment for more context.

  • Protemos:

    • For bundled projects, include the opportunity name or ID in the Job name.

  • XTRF:

    • Instruction fields differ for Classic and Smart projects.

    • Each field name clearly indicates which version it belongs to (for example, “Instruction – Classic”).

    • If instructions don’t appear, check that you’re using the correct project type.



Summary

Instruction mapping saves time and ensures consistency across all your projects.


Start simple, use metadata to automate repetitive details, and set up exceptions only when needed.


This way, translators always get the right context, without extra manual work.