Skip to content
YepstaYepsta Help Centre

Understand the Project Journey and Responsibilities

The journey label summarises the responsibility that needs attention now. It is derived from authoritative Project, delivery and commercial records; nobody manually drags it to the next stage.

  1. 1Win the workProposal, Estimate or direct agreement
  2. 2Set upBasics, tasks, team and commercial controls
  3. 3StartAgreement, intake, approval and payment gates
  4. 4DeliverTasks, appointments, files and client actions
  5. 5ApproveExact deliverable versions and review decisions
  6. 6Collect & releaseAuthoritative Invoice, Payment and final release
  7. 7CompleteClose required outcomes and retain the history
The Project journey follows operational responsibility, while each underlying record keeps its own status and audit history.

Use this responsibility map

Section titled “Use this responsibility map”
Journey stage Business responsibility Typical client responsibility Record that moves the work
Win the Work Prepare scope and authoritative pricing Review and respond Proposal response or accepted Estimate
Set Up Build the delivery plan and configure controls Provide required signatures or intake Setup completion and readiness gates
Deliver Execute required work and communicate progress Supply requested information or complete actions Tasks, appointments, updates and client actions
Get Approval Submit the exact review-ready version Approve or request changes Formal review response
Collect Create and manage the canonical Invoice Pay through the normal payment flow Invoice balance and recorded Payment
Release Confirm release readiness and deliver the final version Download the released asset Immutable release record
Complete Resolve outcome blockers and close operations Give feedback if requested Project completion

Distinguish client action from team action

Section titled “Distinguish client action from team action”

Waiting on Client can be caused by an Agreement signature, intake submission, formal review, Change Order response, information request, client action item or payment. Comments and informal messages do not count as a formal decision.

Waiting on Our Team can mean setup, staffing, countersignature, intake configuration, internal approval, billing preparation, delivery work or completion controls. Open the next-action card to see the exact source.

Waiting on Scheduled Date means no earlier actionable gate is blocking the Project and the configured start or due date has not arrived. Waiting on Nobody means there is no current hand-off, not necessarily that the Project is finished.

Understand next-action priority

Section titled “Understand next-action priority”

Yepsta chooses one primary next action and may show up to two secondary actions. In broad terms it checks:

  1. missing setup or start gates;
  2. blocked or pending commercial changes and client requests;
  3. blocked, overdue or due required work;
  4. deliverable review and release work;
  5. ready billing and outstanding payment;
  6. completion readiness.

The exact action is permission-aware. A user who can see a blocker but cannot resolve it sees a non-executable instruction rather than an unsafe control.

What the client sees

Section titled “What the client sees”

An authorised client stakeholder sees only the sections and actions granted to them. Client-safe progress, selected milestones, appointments, updates, accepted commercial records, Invoices, Payments and released finals may appear. Internal tasks, checklists, notes, internal comments, private documents and unreleased final assets remain hidden.

Last reviewed: