TRTriageRoll

Route batches, then commit

Plan the route. Then change Photos.

Keep every choice local until the whole batch plan is visible, apply album routes first, and leave deletion to a separate Apple-confirmed action.

Coming soon on the App Store Get support

No account. No ads. No developer-operated server.

Built for the actual task

No risky swipe surprise.

Routing cards never claims that Photos changed. TriageRoll records only the album and deletion results Apple confirms, including skipped, declined, and failed work.

01

Route a bounded batch

Choose a specific batch, name two destination albums, and send each item to A, B, Hold, or Delete.

02

Inspect before mutation

Review every item and lane count, undo or redo the draft, and lock an immutable plan only when it is complete.

03

Commit in two stages

Apply album routes first; request deletion separately through Apple's system confirmation and preserve a planned-versus-actual receipt.

Private by architecture

Your records stay yours.

TriageRoll does not collect data. It has no account, developer server, cloud database, remote AI, ads, analytics, tracking, or third-party SDK. Photos stay in Apple Photos; only local identifiers, routes, album names, results, and receipts are stored.

Read the privacy policy