Dealokr

Freelance deal checklist

Check the deal before work begins.

Use this checklist before sending a client link or starting production work. It helps you define the scope, payment step, deliverables, validation rules, usage rights, and final-file release path clearly.

Create the workflow Copy a client message

Checklist

A clean freelance deal needs more than a price and a deadline.

The goal is not to make the project heavy. The goal is to remove the expensive ambiguities before the client pays and before you deliver valuable files.

Before creating the deal

Use this before you turn a conversation into a Dealokr record.

  • Project title and one-sentence outcome are clear.
  • Client name, billing email, and decision-maker are known.
  • Total price, currency, and payment timing are agreed.
  • Deadline or delivery window is realistic.
  • What is excluded from the scope is written down.

Before sending the client invite

Use this before the client receives the secure link.

  • Scope explains the actual mission, not just the category.
  • Deliverables are listed as concrete files, outputs, or services.
  • Revision count and revision boundaries are clear.
  • Usage rights and commercial-use expectations are written.
  • Source-file inclusion or exclusion is explicit.

Before the client pays

Use this to make the payment step feel normal and transparent.

  • The client understands the Dealokr link is the shared deal record.
  • The client can review terms before signing or paying.
  • The payment step is described as handled through Stripe.
  • You have not promised outcomes Dealokr does not control.
  • You know what status means work can begin.

Before delivery

Use this before uploading or sharing work for review.

  • Preview files are separated from final/source files.
  • Any external links are private or permissioned where possible.
  • Large files are tracked honestly as provider-controlled links when needed.
  • The client knows what they are expected to review.
  • Revision notes stay inside the delivery record when possible.

Before validation and release

Use this when the client says the work is ready.

  • The preview delivery matches the agreed deliverables.
  • Open revision requests are resolved or clearly parked.
  • Validation is recorded before final/source assets move.
  • Final files become available only through the release path.
  • The proof timeline shows agreement, payment state, delivery, and validation.

Before calling it complete

Use this after release so the record stays useful later.

  • Final assets and reference links are named clearly.
  • Client validation and release state are visible.
  • Important messages or delivery notes are attached to the deal.
  • Invoice or transaction record is stored if your workflow requires it.
  • You can explain the project history from one record.

How to use this checklist with Dealokr.

Start with the first two sections before creating or sending the deal. They make sure the scope, deliverables, rights, and revision rules are not buried in chat. Then use the payment and delivery sections to keep the project sequence clean.

The checklist is especially useful when final files, source files, creative assets, code, strategy documents, or commercial usage rights are involved. Those details are where informal freelance deals tend to become expensive later.

Keep the tone professional.

The client does not need to feel accused. Present Dealokr as your normal process: clear terms, payment handled through Stripe, preview delivery, client validation, and one shared deal record.

Should every freelance deal use this much structure?

Not every project needs the same depth, but every paid project benefits from clear scope, payment timing, deliverables, validation rules, and file handoff expectations.

Can I use this checklist outside Dealokr?

Yes. The checklist is useful on its own, but Dealokr gives you a shared place to turn the checklist into a deal record, client link, delivery workflow, and proof timeline.

What is the most important item?

The most important item is usually separating preview review from final/source file release, while making sure the payment state is visible before work starts.

Ready to send

Turn the checklist into a client-ready Dealokr record.

Create the deal, send the secure client link, keep payment and delivery states visible, and preserve the proof timeline from the first agreement to final validation.

Create your Dealokr workflowCopy a client message