Change the text, then follow it through
The artwork is ready for review when a colleague sends a correction: the product description needs one more sentence.
Changing the sentence is easy. Knowing what to do next takes more care. Which language versions use it? Has anyone already made new files? Is the preview still showing the old text?
A clear process helps the operator answer those questions without opening every file and comparing it by eye.
In Paqira, content, production jobs and results are connected. The interface uses a few names for the different stages. Knowing what they mean makes it easier to follow an update from the first edit to the checked artwork.
1. Check the saved content
Source data means the information currently saved for an item. For a label, that may include the product name, ingredients, weight and language versions.
Ask the person responsible for the text to check the new sentence here. Confirm that it belongs to the intended product and language.
Paqira compares current content with the content used for the latest production run. It also checks whether the workflow or the scripts used by that workflow have changed.
A workflow is the saved sequence of steps used to make the artwork. A script contains instructions that create or change elements in Illustrator.
This distinction helps you ask the right colleague for help. If the wording changed, speak to the content colleague. If the spacing changed because of a script update, speak to the person maintaining the design rules.
2. Look at what is waiting to run
To process is the prepared data waiting for the next production step. It is separate from the result of the last completed run.
In a normal run across several items, unchanged items can be skipped. Force rerun is available when you deliberately want to run an item again even though no change has been detected.
Before starting a large job, check the selection. It is worth confirming the product names and languages now, while a mistake is easy to correct.
For example, if an English paragraph changed, check which selected items use that English content. Do not assume that every language version needs the same correction.
Follow the team's agreed steps for preparing and reviewing the data before producing new files.
3. Try one useful example first
Start with a test item before running a large set. Choose one that will show whether the change works.
If the new sentence makes the text longer, use a product that already has a long description. If a shared image changed, choose a version where its size matters.
Open the generated artwork and check:
- the new words appear in the correct place,
- no text has been cut off,
- nearby elements still have enough space,
- the correct image and language are present,
- the result is saved in the expected format.
Also check the process log, which records what happened during the run. A job finishing successfully does not by itself prove that the artwork looks right.
If you find a problem, keep the example and describe what you expected. That gives the person fixing the setup something they can test.
4. Follow the job on the workstation
A process is one run of a workflow for one content item. Paqira puts the job in a queue and sends it to an available workstation.
The workstation is a connected Mac or Windows computer with Adobe Illustrator. It must be ready to use the template, fonts and other resources needed for the job.
In the Processes area, you can see the job's status, timing, log and generated files.
A queued job is waiting. A running job is in progress. A succeeded job has finished, while a skipped job did not need the normal run. A failed job needs attention.
If a job fails, read the log and check the workstation connection. Give the person investigating the process details and any recent change to the content or setup.
5. Know what the current preview represents
Output means the result produced by a completed process.
When content or the production setup changes, Paqira keeps the existing result and marks the item as needing attention until it runs again. Editing a sentence does not immediately replace the last generated artwork.
That is why an existing preview may still contain old wording. Check whether the new run has finished before deciding that the update has been missed.
Keep these three questions separate:
- What information is saved now?
- What is waiting to be processed?
- What information was used for the last result?
This makes “the latest file” much less confusing during a busy update.
6. Review the new artwork
The generated preview can be shared for review. Reviewers can select an area or pin a comment to the place that needs attention. Replies and resolved comments stay with the review history.
A comment such as “This line overlaps the weight” attached to the affected area is easier to act on than a message saying “The label is wrong.”
A public review link allows anyone with the link to view the preview. Adding comments still requires sign-in and workspace membership. The link can be turned off when it is no longer needed.
People with the required permissions can accept the result when it is ready. If it is rejected, it can be removed from the portfolio of results before another process is run.
Make the next step clear
Agree who checks the source text, who checks the layout and who accepts the finished result. The operator should also know who can help with a failed process.
When handing over a job, include the item name, the process or result being discussed and the open review comments.
That gives the next person a clear starting point. They can see what changed, what has already been produced and what still needs a decision.