Choose a bundle when one workflow rule is already set and several records or recurring actions must work together around the same stage. If one template or checklist solves the immediate problem, open that resource directly from Templates and checklists.

If you cannot name the affected stage, use the Workflow diagnostic checklist first. If the entire client lifecycle is unclear, start with Freelance client workflow system: inquiry to final payment.

Choose a bundle by the work in front of you

BundleUse it whenDefine the rule withTemplates and checklists
Client setup and recurring controlThe agreement is ready to become a live project record, and active projects need a repeatable review and update rhythmFreelance client workflow system and Client onboarding workflowClient onboarding checklist, Weekly client operations checklist, Weekly client status update template
Delivery and approvalA milestone needs a pre-send check, one feedback route, and a controlled response to a scope-changing requestMilestone delivery workflowDelivery QA checklist, Approval and feedback routing worksheet, Client change request template
Billing and closeoutThe agreement defines the billing and closure rules, and the project needs consistent records at those eventsInvoice and payment workflow setup and Client offboarding workflowInvoice and payment workflow checklist, Approval and billing readiness checklist, Client offboarding and testimonial request template
Stack cleanupThe target stack shape is clear, but current tools and record ownership still need a cleanup planLean software stack blueprint or All-in-one workspace vs specialized stackStack audit and consolidation worksheet, System-of-record rules worksheet, Stack decision readiness checklist

Confirm the trigger before using a bundle

  • For setup, confirm the agreement or authorization required for the project and its start conditions.
  • For delivery, identify the milestone, review owner, and acceptance rule.
  • For billing, use the invoice trigger and follow-up terms in the applicable agreement.
  • For closeout, record the final delivery, approval, billing, access, and archive states that apply.
  • For stack cleanup, decide which operating model the remaining tools must support.

Do not import a sample sequence as a contract term or universal cadence. Adapt each resource to the service, agreement, jurisdiction, workload, and tools involved.

Use only what the stage requires

You do not need every item in a bundle. Choose the resources that correspond to current triggers and records. Record who owns each one and where its result belongs.

For an ambiguous client response, use FAQ: what counts as client approval? For a closeout request with no response, use Client not responding at project closeout.

Finish with one named next action

After completing a resource:

  1. save its result in the authoritative project record;
  2. name the next action and owner;
  3. update any affected date, approval, billing, or closeout state;
  4. open another resource only when the next trigger requires it.

Stop when the current stage has a usable record and a named next action, even if some linked resources are still unopened.