How fixes are ordered
- Fixes that touch a red-flag question come first.
- Then by impact divided by effort: the points a fix removes against the work it takes (Low, Medium or High).
Fixes from the sample claim
| Fix | Applies to | Effort |
|---|---|---|
| Upload the TaxTrex position paper for this project (subscribers) | F2, F3, F4, F6 | Low |
| Apportion wages by work location using payroll address data | S2 | Medium |
| Reconstruct wage allocation from contemporaneous project time records | F4 | Low |
| Export Jira and Git history for each claimed project | F6 | Medium |
| Obtain signed contractor agreements showing rights and risk | F8 | Low |
| Reconcile state QREs to the federal Form 6765 line by line | S3 | High |
Projected score
Tick a fix as done and the scores move. The projected score shows where the file would be with every listed fix complete. It is conditional: it assumes the fix produces the evidence it describes.
What a fix cannot do
Note.A later explanation cannot change the dates of the records it explains, and the mock audit never changes a filed return. Some gaps, such as records that were never created, cannot be repaired.