Frederic

Hi everyone 👋 I’m new here. I’m a developer who’s been hanging around commission spaces for a while, and I noticed the same problems come up again and again in DMs:

unclear scope

approvals buried in chat

revision requests changing over time

“who confirmed what” disagreements

So I turned my notes into a small free Commission Safety Kit (SFW):

• Brief template (what to ask before starting)

• Revision policy checklist

• Milestone / acceptance checklist

Copy-paste ToS line (use it right away):

Work is approved per milestone (sketch / line / color / final). One minor revision per stage. Exportable record available on request.

Quick question for creators & clients here: Do you prefer approvals… A) only once at the end B) after each stage (sketch/line/color) → Comment A or B (or just KIT) and I’ll reply with a ready-to-paste version that fits your workflow.

Optional tool version (if you want an exportable logbook): Time-Shards 🔗 https://time-shards.skreeb.io/

Thanks! I’m here to learn how people actually handle commissions, so feel free to tell me what part of the process causes the most friction for you.

Hey — dropping a tiny Commission Safety Kit I use to keep DMs from turning into revision chaos. It’s basically just a one-liner ToS rule + a simple milestone habit.

Copy-paste ToS lines (pick one)

Soft

Approvals are per milestone (sketch/line/color/final). 1 minor revision per stage. I can provide an exportable record if needed.

Standard

Approvals are per milestone. 1–2 minor revisions per stage; bigger changes are paid add-ons and confirmed before I continue. (Exportable record available if needed.)

Strict

Approval happens at each milestone. 1 minor revision per stage; anything outside the approved scope is a paid add-on, confirmed before work continues. (Exportable record/receipt if needed.)

30-second setup

Pick 3–4 milestones (sketch / line / color / final)

Decide revisions per stage (1–2)

Paste one line into your commission info / ToS

Quick poll (helps a lot)

How do you prefer approvals? A) approve once at the end B) approve each stage (sketch/line/color)

Reply A or B — or just say KIT and tell me your stages + revision count, and I’ll rewrite a one-liner that fits your setup.

Optional (if you want a clean exportable log)

I’m also building Time-Shards — a tiny SFW, privacy-first milestone logbook (milestones, approvals, revision notes, exports). It’s not a marketplace or payment thing — just a neat record you can export/share when needed. There’s an optional integrity check page too (basically “did this receipt get edited?” — not legal proof).

🔗 https://time-shards.skreeb.io/ If you’re attaching screenshots: Img 1: Overview + the free kit Img 2: Demo — milestones + revision notes + export Img 3: Optional integrity check (tamper check only)