Additional testing may serve the project, but spending alone does not prove what the applicant already knows. Explain the purpose and timing of any further work.
Separate evidence of existing knowledge from development expense
Budget tests, professional preparation, translations and current official fees according to their actual purpose. Avoid suggesting that a particular testing budget is a legal minimum for L-1B.
A small project value cannot waive eligibility conditions or guarantee a simplified outcome. Before paying for additional testing, ask the technical team to state in writing whether each proposed test is meant to teach the employee something new or to confirm understanding that already exists, since only the second kind actually documents current knowledge rather than future learning. Timing matters as much as content: a test completed only after the filing date says little about what the employee understood beforehand, so any test meant as evidence should be dated and, where possible, completed before the record closes. Ask whether existing project logs or prior internal reviews already show the same understanding at lower cost than commissioning a new test built solely for the case. Keep the cost of any genuinely business-driven testing separate from testing added only to build a paper trail, since mixing the two budgets obscures what each purchase was actually for. Ask whether the same understanding could instead be shown through a short written explanation from the employee's own manager, since a manager's account of daily performance sometimes documents the same point without any additional testing expense at all.