CLEAN STUDIO · MANUAL → REPEATABLE → AUTOMATIC

Teach PocketClean how this source should be cleaned.

Inspect once, choose exactly what stays or changes, validate what the fields mean, save the recipe, then reuse the same rules through the browser, Business workflows, or API.

1 · SOURCE

Inspect a file

2 · MODE

Manual or saved recipe

Inspect a source to create its schema guard

DATA HEALTH

—/100

Audit summary appears after inspection.

3 · FILE-WIDE RULES

Safe defaults

4 active

Trim whitespaceRemove leading/trailing spaces from populated cells.Normalize headersClean spacing and name blank columns deterministically.Remove empty rowsDrop rows with no meaningful values.Remove exact duplicatesKeep the first row after approved transforms/fills.Remove empty columnsDrop columns that remain completely empty.

4 · COLUMN CONTROL

Keep, type, rename, standardize, clean, or fill each field

Auto is conservative. Exact value maps standardize known aliases without guessing; type rules then validate the canonical output.

0 customized

Inspect a source file to unlock column-level controls.

5 · PREVIEW EFFECT

See what the recipe changes before you save it

Counts, field names, and quality scores only—never raw business cell values.

Run after first-pass decisions

Your current cleaning choices are ready to preview.

6 · SAVE THE SOURCE RECIPE

Approve it once

Personal/Business recipes use the existing PocketBI workflow sync. Header detection will remain automatic for future files. Type rules and exact value maps are saved with the same recipe. Configure Source Profile recognition and routing.

7 · RUN / SEND TO NEXT STEP

One cleaned dataset, multiple destinations

Recognized Source Profile: the primary Run action follows its saved interactive next step. Semantic standardization: exact value maps travel with the recipe through browser, API, and queued execution. Typed contract: Auto/Text/Number/Date/Boolean choices validate the resulting canonical values. PocketBI handoff: generic Clean Studio transfers are explicitly unverified; only a durable Verified Cleanup receipt may carry cleaning-only verification. Safety: outputs with known typed violations are marked review-required instead of being handed downstream as fully clean.