TalentDocket Discuss the pilot

Product

A collaboration is a sequence. The product is being built around it.

This page describes the target workflow. Status labels come from the runtime capability registry and show which parts are bounded pilot versus currently gated.

Target sequence

Twelve intended entries, start to finish.

The end-state design makes each step evidenced and append-only. Most of this sequence remains gated in the current release.

  1. 01 Brief captured Bounded pilot A brand enquiry becomes an owned record instead of a message you hope to find again.
  2. 02 Scope agreed Bounded pilot Deliverables, revisions, exclusivity, usage rights, fees and payment terms, all stated before work starts.
  3. 03 Contract approved Currently gated The target workflow uses versioned agreements, clause-level decisions and a complete revision history.
  4. 04 Contract signed Currently gated The target supports e-signature or a counter-signed scan, with the signed version fixed to the record.
  5. 05 Deliverables assigned Bounded pilot Every item has an owner, due date and readable state inside the bounded records pilot.
  6. 06 Content submitted Currently gated The target keeps each draft against its deliverable instead of as an attachment in a thread.
  7. 07 Revision or approval recorded Currently gated The target records who approved what, when and against which exact version.
  8. 08 Publication proved Currently gated The target stores the live link, timestamp and captured proof against the collaboration.
  9. 09 Billing milestone unlocked Currently gated The target links approved delivery to controlled invoice preparation.
  10. 10 Invoice issued Currently gated The gated issuance design uses sequential financial-year numbering and freezes the tax treatment.
  11. 11 Collection executed Currently gated The gated receivables design uses owned queues, dated actions and evidenced reminder delivery.
  12. 12 Payment reconciled Currently gated The gated target matches receipts across invoices, records TDS evidence and prepares an accountant handoff.

Intended outcome

One record designed to answer the awkward question.

Four months after a campaign, somebody asks why an invoice is short, or whether a third revision was ever agreed. The completed docket is intended to preserve every commitment, approval and payment in sequence.

Shared finance, approver and accountant access remains gated until its role, provider, professional-review and staging evidence passes.

Illustrative target · DOCKET TD-2026-0418 Lumen Beauty × @ananya.works
Brief captured 12 Aug /Reels ×2, Stories ×3
Scope agreed ₹4,50,000 /2 revisions, 90-day usage
Contract executed 13 Aug /v3, signed 2 of 2
Deliverable approved 21 Aug /Reel 1 of 2, proof captured
Invoice issued TD/26-27/0118 /₹5,31,000 /incl. GST 18%
Payment reconciled Awaiting /due 21 Sep /next action 04 Sep
Evidence complete 5 of 6 Outstanding ₹5,31,000

Product direction

Six connected surfaces, one target spine.

Each surface is mapped to the capability registry below; implementation does not make a gated surface available.

Scope & collaborations

Bounded pilot

Bounded pilot records for the commercial detail a creator deal actually has.

  • Creators, counterparties, campaigns, platforms
  • Deliverables, deadlines, revisions, exclusivity
  • Usage rights and disclosure obligations
  • Enforced states from Draft through to Closed

Contracts

Currently gated

A gated contract design where the signed document and the deal cannot drift apart.

  • Immutable contract and deliverable versions
  • Clause-level decisions and revision history
  • E-signing, with external counter-sign fallback
  • Publication-gated delivery and billing

Delivery evidence

Currently gated

A gated evidence trail attached to the milestone it is intended to unlock.

  • Submission, revision and approval trail
  • Publication URL, timestamp and file hash
  • Approvals recorded against an exact version
  • Malware-scanned evidence storage

Compliant invoicing

Currently gated

A gated issuance workflow with GST validation in a bounded pilot; no compliance outcome is guaranteed.

  • Sequential financial-year numbering
  • GST computation with GSTIN validation
  • Immutable tax and rule passports per line
  • Controlled corrections and credit notes

Receivables

Currently gated

The planned collections desk; runtime access and provider delivery remain gated.

  • Work queue by ageing, owner and next action
  • Promises to pay, disputes and escalation paths
  • Counterparty payment history and risk
  • Reminder sequences with delivery evidence

Reconciliation & handoff

Currently gated

The planned last mile: matching receipts to work and preparing an accountant handoff.

  • Receipt capture and multi-invoice allocation
  • Append-only corrections, never silent edits
  • TDS tracking and Form 26AS comparison
  • Financial-year packages for your accountant

Evidence principles

Every released claim must trace back to a record.

These principles guide the repository, while the labels identify which customer-facing results are actually released.

Append-only history

Currently gated

The repository models corrections as new events with actor, timestamp and reason. The affected financial workflows remain release-gated.

Tenant isolation

Bounded pilot

Database row-level security and tenant-scoped records are implemented, while signed-in access remains a bounded pilot.

Least-privilege roles

Currently gated

Role-based access is in bounded pilot; external-accountant sessions and their end-to-end release evidence remain gated.

No fabricated data

Bounded pilot

Released pilot surfaces must show an error or empty state rather than substituting sample business data.

Traceable analytics

Currently gated

The analytics design exposes source, freshness and exclusions, but authoritative dashboards are currently gated.

Your data, exportable

Currently gated

Versioned CSV/XLSX packages exist in repository tests, but accountant exports are not released.

Get started

Compare your messiest live deal with the pilot.

We will show the current bounded surfaces and mark the gated steps instead of presenting the complete target workflow as available.

Discuss the pilot Ask a question