Content judgement stays explicit
Legal, factual, editorial and readability questions still require the appropriate human or domain review.
Connected jobs
Use a workflow when one useful result should become the next input.
Workflows connect focused tools around a recognisable job. They are never required: every practical tool remains directly usable from Tools.
Choose the job you are trying to finish
Jump directly to the workflow that matches your situation.
Prepare a product catalog & asset pack
Reconcile product data with local assets, check explicit requirements and verify the pack before import or handoff.
Prepare an image delivery
Review, correct and verify a group of images before handoff.
Check a document delivery
Review required files, versions and delivery constraints.
Match records to files
Reconcile expected records with actual files and resolve unclear matches.
Check website files before release
Compare changes, inspect the candidate set and verify release constraints.
Prepare a product catalog & asset pack
Bring a supplier or export spreadsheet together with local product assets. Review missing, extra or unclear coverage, apply explicit requirements and re-check the pack before it reaches a store, marketplace, PIM or client.
1 · Check the product data
Use CSV Preflight when the source table itself may have structural or data-quality issues.
2 · Match records to assets
Choose the real product identifier and review missing, extra or ambiguous relationships.
3 · Check explicit listing claims when verified facts are available
Compare supplied dimensions, quantity and exact product facts with listing copy without turning TaskThimble into a truth oracle.
4 · Check the catalog asset pack
Verify per-record asset coverage and the explicit image minimums you actually require before import or handoff.
5 · Create corrected image copies when needed
Normalize image canvases or use the format converter only for findings that are actually unintended.
6 · Apply delivery rules
Use explicit format, size, count or naming requirements, then re-check the final set.
7 · Create delivery evidence
Export a manifest of the final asset set with measurable file facts and hashes.
Prepare an image delivery
Review the whole image set before correcting or handing it off.
1 · Review the image set
Surface set-relative size, canvas, brightness, transparency and format differences.
2 · Scan the set visually when useful
Create a contact sheet and review unusual shape or brightness signals without turning them into automatic quality failures.
Review similar pairs when duplication is a concern
Surface perceptually similar candidate pairs, then compare or confirm them before taking any destructive action.
3 · Create corrected copies
Normalize canvas size without cropping. Use Image Format Converter when format consistency is the actual issue.
4 · Check explicit delivery rules
Use a readiness check when the client, CMS or marketplace defines concrete file constraints.
5 · Create delivery evidence
Export a manifest with file facts and hashes for the final output set.
Check a document delivery
Separate file-level completeness from content-level judgement.
1 · Check the document pack
Review required named components, formats, empty files and lightweight PDF container signals.
Review possible file versions when naming is unclear
Group final, draft, copy and revision-like filenames without assuming the newest file is authoritative.
2 · Review text consistency when relevant
Use preferred terminology and conservative consistency signals for extractable text formats.
3 · Apply external delivery constraints
If the recipient has explicit file rules, test those separately and re-check before handoff.
4 · Create delivery evidence
Export the final file inventory and fingerprints.
Match records to files
Use expected data and actual files together without guessing identity.
1 · Check table relationships when relevant
Verify primary IDs and related references before using those identifiers to reconcile files.
2 · Choose the identifier and reconcile
Clear relationships can be matched automatically; near or competing matches remain review items.
3 · Investigate naming or set problems
Inspect the file set when unexpected names, duplicates or empty files make reconciliation harder.
4 · Repair numbered filename sequences if needed
Preview gaps, duplicates and a safe renumbering plan before creating copies.
5 · Check readiness after resolution
After missing files or naming issues are resolved, test the final set against explicit requirements.
6 · Export the final inventory
Create a manifest for the resolved file set.
Check website files before release
Review what changed first; then decide which changes need attention before deployment.
Compare baseline and current files
Identify added, removed and changed files, while keeping uncertain comparisons explicit.
Inspect the current set
Check names, empty files and set-level structure if the release package itself needs review.
Apply release constraints
Check the concrete format, count, naming or size requirements that matter for the release.
Create a release manifest
Record the final candidate set and SHA-256 fingerprints for handoff or later comparison.
Smaller connected routes
Some jobs need only two or three quick tools.
Spreadsheet → check → transform → export
Open Excel, use CSV Preflight or Table Lab, then export the result in the format you need.
Text → extracted list → clean or compare
Extract emails, URLs or numbers, then deduplicate, sort, count or compare the resulting list.
Prepare a list → pick or group
Reuse a pasted or spreadsheet-derived list across random-choice and grouping tools.
Boundary
Automatic when safe. Explicit when ambiguous.
TaskThimble can reuse compatible results in the next step, but it does not silently choose a spreadsheet key, a table column or an uncertain file match when that choice could change the meaning.