Read the rejection
Use the exact message, screenshot, or published requirements.
This is the direct route into the Ninjitzu workflow: start with what the portal rejected, add the file, and let DOTi guide you toward a clean PASS.
Tell DOTi what happened, then continue into Make It Pass with the right context.
You do not need to understand the rejection first. Start with whatever you know.
A rejected file should not trigger random compression and conversion. The clean path is to understand the requirement first, repair the mismatch, and verify the result.
Use the exact message, screenshot, or published requirements.
Size, format, pages, orientation, or another specific rule.
Check the repaired file against the supplied rules before trying again.
She is the calm voice inside Ninjitzu. DOTi translates confusing upload problems, keeps the next useful step obvious and helps you choose the right repair path without inventing rules a portal never showed you.
Start with the rejection message or requirements, inspect the file, repair the mismatched rules, and verify the result before trying again.
Use the portal message, screenshot, published upload instructions, or the file itself as clues. Do not invent missing rules.
No. PASS verifies the supplied checks, while the receiving portal makes the final acceptance decision.