What if you’re merging 📜 📜 a file and checking for consistency, but you notice that there’s lots of errors in one or more segments? Or, what if you’re reviewing 📝 a file that contains so many errors that you’re almost doing all the work of the original scribe?

These are things that can happen. The important thing is to try everything you can do to avoid the file being sent to the client.

If you’re still working on the file…

The first step to take:

1. 📩 Send a message an admin on Discord and/or [email protected] shortly explaining the situation. Just to be sure, flag it on the 🙋-help-and-tips channel as well so that other scribes are aware. Always make sure to mention the file name and language.

❌ no reply from Admin

If you receive no reply from us (or if it’s outside of working hours, or on the weekend), go ahead with one of the below options ⬇️.

✅ reply from Admin

If we do reply, go ahead with what we ask you to do and what you’re capable of. Please keep us updated on the process— and try giving a fair estimation of the finishing time so we can inform the client of the exact delay 🔎.

Your following options:

1. 📝 Correct and fine-tune the gig entirely. If you’re confident that you have enough time to do so, go ahead and finish the merge or review gig, correcting for all the mistakes. Notify us when you think you will have the work ready by, so we can inform the customer.
2. ⏳ Enough time but no opportunity to work on it? In that case, either wait for our response until the file is close to its deadline, or alternatively, you can also un-claim the file. We don’t want this file to get sent— it’s better that someone else goes ahead with it.
3. ⌛ Running out of time? First, ask for a deadline extension. Then, if there’s no more extensions available, un-claim the file, make sure that the 👾 Discord community is aware of the issue. Do not let the timer run out— that will end up sending the file the customer’s way.

In any case, whatever the issue is, whether it’s payment, deadlines, review scores— we will adjust for it later. What’s most important is to act on the problem together 💪.

<aside> ❗ Only ever send customer-ready files Whatever you do, never ever submit a file that you know is not customer ready. We can suspend you for this.

We would much rather create the opportunity for the scribes to deliver quality work, even if that means the gig is running into a delay. We can settle your compensation and the un-counting of deadline extensions later 😉.

If you quietly sent in a non-customer ready file and we receive a complaint from the customer, we will directly terminate our collaboration with you. Therefore, always be honest about it and let us know if this happened.

</aside>

Successfully made it customer-ready?

1. Inform an admin on Discord or [email protected] and let them know about the extra effort it took you.
2. If the issue was very serious, feel free to inform your fellow scribes on the language’s channel on Discord about this and feel free to include the filename. The scribe that worked on it will be made aware this way.
3. Any extra steps will be done by an admin, such as creating a feedback gig for a bad segment.

Thank you!