PlaysbyMoat8
Back to the library
The workflow guideOperations

Coordinate a career client’s job-search pipeline

Combine a client’s target role, market research, application materials, and interview preparation in a shared advisory workflow.

6 implementation stepsAdvanced

How this works

Combine a client’s target role, market research, application materials, and interview preparation in a shared advisory workflow.

Coordinate the client’s search as an advisory pipeline with truthful materials and explicit approval states. Separate researched vacancies, draft applications, submitted applications and confirmed interview invitations so progress is not overstated.

Before you start

Defined operating scope

Career consultants coordinate several deliverables and review stages for each paying client.

Required source material

Obtain Client goals and verified experience; Relevant vacancies and market data; Application history. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

A role requires a credential the client lacks. Flag the gap and let the client decide whether an honest application is appropriate.

Prepare the inputs

client_profile
Required

Verified experience and target conditions

Mark unverified claims and non-negotiable constraints.

vacancy_records
Required

Role, employer, requirements and date

Check availability and location expectations.

application_history
Required

Role IDs, status and prior versions

Avoid duplicate submissions and contradictory claims.

approval_preferences
Required

Client review and contact rules

Specify who may submit or communicate.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check client_profile, vacancy_records, application_history, approval_preferences before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected client_profile and any missing required fields.

  2. Research the target market and agree a realistic search strategy

    • Agree target roles and constraints using the client’s actual experience and current market evidence.
    • Match every résumé claim to the verified profile or client-confirmed evidence.

    Checkpoint: A saved intermediate result for: Research the target market and agree a realistic search strategy.

  3. Adapt truthful application materials to relevant roles

    • Adapt existing truthful achievements to role requirements; retain gaps rather than inventing credentials.
    • Reconcile application status against actual receipts and prevent duplicate submissions.

    Checkpoint: A saved intermediate result for: Adapt truthful application materials to relevant roles.

  4. Collect suitable vacancies and draft outreach for the client to approve

    • Shortlist suitable vacancies and prepare application or outreach drafts with reasons and client review status.
    • Match every résumé claim to the verified profile or client-confirmed evidence.

    Checkpoint: A saved intermediate result for: Collect suitable vacancies and draft outreach for the client to approve.

  5. Track progress and prepare practice interviews using the role and client background

    • Track confirmed outcomes and prepare interview practice around the actual role, previous feedback and the client’s evidence.
    • Reconcile application status against actual receipts and prevent duplicate submissions.

    Checkpoint: A saved intermediate result for: Track progress and prepare practice interviews using the role and client background.

  6. Package the result and unresolved work

    • Never fabricate experience, credentials, or referrals. The client approves applications and outreach; a search plan does not guarantee interviews or offers.
    • Never fabricate experience, references or credentials.

    Checkpoint: An organized job-search workspace with tailored drafts and preparation tasks. Unresolved items remain visible in the review record.

Decisions along the way

A role requires a credential the client lacks.

Flag the gap and let the client decide whether an honest application is appropriate.

The vacancy is closed or its status is unclear.

Verify availability before preparing a time-sensitive submission.

An application status is not confirmed.

Keep it draft or submission unknown; do not claim it was received.

What you will produce

career-client-search-coordination-result.json

JSON

An organized job-search workspace with tailored drafts and preparation tasks. Label proposed and completed states separately.

Include: client_id · vacancy_id · fit_evidence · gaps · application_version · approval_state · confirmed_status · status · evidence_reference · review_note

career-client-search-coordination-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving approval_preferences.

Include: source_reference · question · owner · next_action

Check the result

  • Match every résumé claim to the verified profile or client-confirmed evidence.
  • Reconcile application status against actual receipts and prevent duplicate submissions.
  • Inspect client_profile and vacancy_records in both the original and output; confirm that record identity and interpretation survived the transformation.
  • Never fabricate experience, credentials, or referrals. The client approves applications and outreach; a search plan does not guarantee interviews or offers.

When something goes wrong

A role requires a credential the client lacks.

Flag the gap and let the client decide whether an honest application is appropriate. Retain the affected evidence and recovery status.

The vacancy is closed or its status is unclear.

Verify availability before preparing a time-sensitive submission. Retain the affected evidence and recovery status.

An application status is not confirmed.

Keep it draft or submission unknown; do not claim it was received. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Coordinate a career client’s job-search pipeline for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Client C-2 has three years of operations experience but no required certification. Vacancy V-8 requires that certification; V-9 lists it as optional.

Expected result

Synthetic expected result: V-8 is a documented eligibility gap. V-9 may be shortlisted with truthful experience-based wording; no certification is added to either draft.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure consultant minutes per approved deliverable; missed follow-ups and unsuitable shortlisted roles.

Stop or revise

An application status is not confirmed. Pause affected records and apply this recovery: Keep it draft or submission unknown; do not claim it was received.

Keep the scope clear

  • Never fabricate experience, references or credentials.
  • The client controls applications and outreach; the workflow does not guarantee interviews or employment.

Check before using

Never fabricate experience, credentials, or referrals. The client approves applications and outreach; a search plan does not guarantee interviews or offers.

Business activities

  • Deliver recurring client work

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Client goals and verified experience · Relevant vacancies and market data · Application history

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗