Glossary
Workflow accountability terms
Definitions for Zlaip primitives: the gates and records that move creative work from locked terms through review, approval, and payment.
Revision Boundary
The line between included feedback and billable extra work. A Revision Boundary caps how many consolidated revision rounds each milestone includes, and what must happen when client feedback keeps coming.
Scope Drift
When "one small addition" is not in the locked scope. Scope Drift surfaces the moment expansion appears so it becomes a change order, not free work.
Accountability Chat
One timeline per client project: your messages plus system cards for deliverables, revision usage, drift warnings, change orders, approvals, and payment events.
Review Workspace
Structured feedback on the asset itself — not scattered chat messages — with revision boundaries and Approval Lock still governing the milestone.
Anchored comment
Feedback that stays on the asset. Timecoded on video, highlighted on PDF, pinned on staging builds.
Change Order
The on-ramp for extra work: documented scope, price, and timeline accepted by both parties before you deliver beyond the original milestone.
Agreement Lock
The moment a creative contract becomes the immovable reference for every milestone, revision limit, change order, and approval on the project.
Approval Lock
Explicit, attributable client sign-off on a specific version. Not a reaction, not praise in chat, not payment sent in hope.
Payment Release Gate
No approval, no release. The gate ties money movement to explicit client sign-off, not submission alone or friendly chat.
Agreement Health
A risk snapshot before you lock: unclear payment terms, missing revision limits, and one-sided clauses surfaced as a score, not a surprise mid-project.
Read the blog → for guides on revision limits, scope creep, invoicing, and client approval workflows.