Deal Catch-up
Follow this skill's evidence, artifact, privacy, action-control, and outcome-reporting rules below.
Domain: Sales.
Evidence and connectivity
Begin with authorized user-provided material and accessible work sources. Discover optional CRM capabilities at runtime and use them only to enrich or execute the job; never require a vendor, connector, record identifier, object name, or field name to begin when the minimum semantic evidence is otherwise available.
If CRM is unconfigured, unavailable, denied, stale, partial, or unsupported, continue with the supported baseline, disclose the affected scope, and block only the dependent conclusion or action. Distinguish an authorized empty result from failed or unexecuted retrieval. If no connected evidence source is available, ask for the minimum pasted facts or file needed for the next useful step and return a bounded framework or needs_input rather than inventing data.
Data Sources
Use relevant supplied material or applicable tools and sources you are authorized to access. These are options, not a mandatory checklist. Ask for missing essential input or context; unavailable evidence remains unknown, not negative evidence.
- Record Snapshots & Exports for scoped membership, dated baselines, current state and authoritative change events.
- Email for substantive customer explanations of timing, value or decision changes.
- Meeting Transcripts & Notes for dated commitments and the reasons behind material movement.
- Internal Messaging for evidenced alignment needs, dependencies and seller-reported context.
- Knowledge & Files for prior reviews and proposals that establish a comparable baseline.
Retain provenance, freshness limits and the existing evidence, privacy and authorization rules.
Purpose
Report what changed on a scoped set of deals since a stated point in time, distinguish genuine
customer or deal movement from record housekeeping, and attach a substantiated reason to each
material change.
Applicability
Use when an account or a scoped set of deals is identifiable from the request, accessible work
context, or supplied material. Establish the requested comparison window and any available
baseline. Current structured deal state is optional enrichment, not a prerequisite. Two related
asks share this procedure:
- which deals in scope slipped, and why;
- what changed across a bounded top set of deals (by value or another stated basis) since a
point in time.
A missing baseline or authoritative opportunity snapshot still supports a result: reconstruct
the dated visible-evidence chronology, label current structured state and period-over-period
movement unknown where unsupported, and do not invent a prior state. Disambiguate an opportunity
only when several plausible deals would materially change the result.
Usage situations
- "Which of my deals slipped this week, and why?"
- "What changed on my top deals since last Monday?"
- "What moved on this account's deals while I was out?"
- Non-trigger: "Which deals should I work next" (ranking — use
pipeline-prioritizer); "give me
the full picture on this one deal" (a single deal's standing review).
Procedure
- Establish the account or deal scope and the baseline or window from the ask. Discover the
account from available context before asking "Which account?" Resolve a relative period
("last week", "since I was out") to a concrete date
range with timezone and state it. If the period is ambiguous, ask when material or state
a provisional interpretation. Do not invent a prior state when a baseline is unavailable.
For a bounded top set, name the selection basis and presentation cap; honor a supplied
cap, otherwise state a practical cap for this result, not a universal priority threshold.
- Use available current state for each in-scope deal: name, value, stage/status, close date,
last record-modification time, owner, account, and stakeholders. Mark missing fields unknown.
- Establish what changed:
- Prefer a genuinely dated, authoritative history of the record when one exists.
- Where a computed or narrative "what changed since" summary is available, treat it as a
lead pointing at what to check, not a verified fact — it is generated, not a sourced
quote.
- Compare dated prior and current evidence, or use an authoritative dated change event.
A modification timestamp establishes record recency only, not a specific deal change,
direction, magnitude, or cause.
- Report an in-window slip only when dated evidence places a postponement or a newly
crossed close deadline while the deal remained open inside that window. Already
overdue before the baseline is a separate current overdue status, not a new slip.
Apply the same timing test to stage regression, likelihood/value decline, and won/lost
transitions. If evidence brackets only a broader interval, state it and leave change
inside the requested window unknown.
- Establish why each material change happened from actual evidence — supplied notes, messages,
meeting records, or other communication — read at the content level, not inferred from a
status field alone. Attribute the reason to its source and, where known, the person. A
change with no available evidence for its reason is still reported, with the reason marked
unknown; an unconfirmed reason on one deal does not block reporting the rest of the digest.
- Compare a source-attributed signal with established current record state before flagging
it as not reflected in the record. Without that comparison, label it an unverified update
candidate. Do not apply an update.
- Compose per deal: what changed, the substantiated (or marked-unknown) reason, any
record-update flag, and a suggested next action. When the evidence surfaces an
internal alignment need or dependency that changes the next step, name it as an
optional field distinguishing a known dependency, a decision still needed, and a
suggested seller action — never a guessed colleague or area of expertise. Order by
the stated impact basis (slip severity, value, or another stated criterion).
Judgment
- A record-modification timestamp establishes recency only. Use dated change evidence to
establish movement and substantive evidence to establish its cause.
- A generated "what changed" narrative is a lead to verify, not a verified source fact; cite
the actual evidence, not the narrative, for the reason.
- An absent reason is a per-deal gap, not grounds to withhold the rest of the digest. Report
the change and mark the reason unknown.
- Do not claim "no changes" or "all signals reviewed" unless the evaluated coverage actually
supports it — state what was checked.
- A missing baseline yields a current-state, dated observation, with movement explicitly
marked unknown — never a fabricated prior state or an invented "no change" result.
- State the selection basis, presentation cap, and comparison period used. A cap controls
presentation, not business importance; a different cap, named list, or window is valid.
- A stated "top" set reflects the deals actually evaluated. When the underlying evidence pull
is itself bounded or paged, say so — a partial read is not the genuine top of the full book.
Output
Deliver both a concise chat summary and one saved primary editable artifact, following the
sections below. The artifact must explain what changed and why across a scoped deal set, marking unsupported movement or
causes unknown.
Chat summary
In chat, summarize the largest evidenced movement, its best-supported reason, the most material
regression or unknown, and the next action. State the examined scope and window so the summary
cannot be mistaken for a complete portfolio view.
Artifact content
Identify the ownership or membership evidence that establishes the requested deal set. Separate verified members from unresolved candidates; correspondence alone does not establish ownership. Preserve supported observations for candidates without including them in unqualified portfolio claims or asserting movement outside the verified baseline and period.
State scope, requested window, available baseline (or its absence), selection basis/cap,
evaluated deal count, and coverage. Then, per deal: verified movement and its dates, or
current state with change unknown; the substantiated reason (or "unconfirmed" with what
was checked); any record-update flag or unverified candidate; an optional internal
dependency field when the evidence supports one; and a proposed next action. Keep
existing overdue status separate from verified in-window slips.
Artifact selection
Choose one format for the complete internal deal catch-up, respecting the user's requested format:
- Word (.docx): Default for explaining what changed, why and what to do next.
- Excel (.xlsx): Instead for filtering a scoped multi-deal chronology or action handoff, with takeaways and causal explanations retained.
- Markdown (.md): When requested or Office creation is unavailable or fails; retain the full content and disclose fallback limitations.
Use authorized, format-specific workflows. Keep content concise and styling simple. Plan changes together and apply them in as few supported batches as practical. Update authorized existing artifacts without creating duplicates or changing unrelated content. Follow Delivery and control for saving and reporting.
Delivery and control
Verify the save before reporting success and provide the actual link or location. If saving fails, disclose it and provide clearly labeled unsaved catch-up in chat.
Guardrails
This report is read-only except for creating and saving the requested file artifact in an
authorized location. It does not update records, send messages, or take any other action on a
customer's or seller's behalf. A record-update flag is a proposal for the user to apply, not an
applied change.
When NOT to Use
- Not for choosing which deals to work next; use
pipeline-prioritizer.
- Not for one deal's complete standing review; that requires a separate review procedure outside this catalog.
- Do not report a change as confirmed from a record-modification timestamp alone, and do not
claim complete coverage from a partial or capped evidence pull.
Required information
- Minimum: an identifiable account or deal scope. Accessible correspondence, meetings,
notes, proposals, or supplied material can support a visible-evidence reconstruction without
a current CRM opportunity snapshot.
- Structured-state enrichment: current opportunity evidence improves current-state and
field-level comparisons but is not required for the baseline catch-up.
- Comparison evidence: a resolved comparison period plus dated prior/current evidence
or a dated change event establishes movement within that period. Without it, report
current state and dated observations, with change unknown.
- Reason evidence: substantive notes, messages, meeting records, or other evidence.
Its absence leaves the reason unknown for that deal, not the whole result unavailable.
- Missing-input question: "Which account or deal set should I catch up on?"
1---2name: deal-catchup3description: Summarizes what changed and why across a scoped deal set, separating genuine customer movement from record housekeeping. Use to report what changed and why across a scoped set of deals since a stated baseline, such as "which deals slipped", "what moved on my top deals", or "what changed while I was out". Needs a defined scope and current deal evidence; a baseline improves the comparison, but a current-state result is available without one. DO NOT use for ranking what to work on next or a single deal's full standing review.4metadata:5 source: https://skillmd.com/skills/microsoft/deal-catchup6 displayname: Deal Catch-up7---89# Deal Catch-up1011Follow this skill's evidence, artifact, privacy, action-control, and outcome-reporting rules below.1213Domain: Sales.14## Evidence and connectivity1516Begin with authorized user-provided material and accessible work sources. Discover optional CRM capabilities at runtime and use them only to enrich or execute the job; never require a vendor, connector, record identifier, object name, or field name to begin when the minimum semantic evidence is otherwise available.1718If CRM is unconfigured, unavailable, denied, stale, partial, or unsupported, continue with the supported baseline, disclose the affected scope, and block only the dependent conclusion or action. Distinguish an authorized empty result from failed or unexecuted retrieval. If no connected evidence source is available, ask for the minimum pasted facts or file needed for the next useful step and return a bounded framework or `needs_input` rather than inventing data.1920## Data Sources2122Use relevant supplied material or applicable tools and sources you are authorized to access. These are options, not a mandatory checklist. Ask for missing essential input or context; unavailable evidence remains unknown, not negative evidence.2324- Record Snapshots & Exports for scoped membership, dated baselines, current state and authoritative change events.25- Email for substantive customer explanations of timing, value or decision changes.26- Meeting Transcripts & Notes for dated commitments and the reasons behind material movement.27- Internal Messaging for evidenced alignment needs, dependencies and seller-reported context.28- Knowledge & Files for prior reviews and proposals that establish a comparable baseline.2930Retain provenance, freshness limits and the existing evidence, privacy and authorization rules.3132## Purpose33Report what changed on a scoped set of deals since a stated point in time, distinguish genuine34customer or deal movement from record housekeeping, and attach a substantiated reason to each35material change.3637## Applicability38Use when an account or a scoped set of deals is identifiable from the request, accessible work39context, or supplied material. Establish the requested comparison window and any available40baseline. Current structured deal state is optional enrichment, not a prerequisite. Two related41asks share this procedure:42- which deals in scope slipped, and why;43- what changed across a bounded top set of deals (by value or another stated basis) since a44 point in time.4546A missing baseline or authoritative opportunity snapshot still supports a result: reconstruct47the dated visible-evidence chronology, label current structured state and period-over-period48movement unknown where unsupported, and do not invent a prior state. Disambiguate an opportunity49only when several plausible deals would materially change the result.5051## Usage situations52- "Which of my deals slipped this week, and why?"53- "What changed on my top deals since last Monday?"54- "What moved on this account's deals while I was out?"55- Non-trigger: "Which deals should I work next" (ranking — use `pipeline-prioritizer`); "give me56 the full picture on this one deal" (a single deal's standing review).5758## Procedure591. Establish the account or deal scope and the baseline or window from the ask. Discover the60 account from available context before asking "Which account?" Resolve a relative period61 ("last week", "since I was out") to a concrete date62 range with timezone and state it. If the period is ambiguous, ask when material or state63 a provisional interpretation. Do not invent a prior state when a baseline is unavailable.64 For a bounded top set, name the selection basis and presentation cap; honor a supplied65 cap, otherwise state a practical cap for this result, not a universal priority threshold.662. Use available current state for each in-scope deal: name, value, stage/status, close date,67 last record-modification time, owner, account, and stakeholders. Mark missing fields unknown.683. Establish what changed:69 - Prefer a genuinely dated, authoritative history of the record when one exists.70 - Where a computed or narrative "what changed since" summary is available, treat it as a71 lead pointing at what to check, not a verified fact — it is generated, not a sourced72 quote.73 - Compare dated prior and current evidence, or use an authoritative dated change event.74 A modification timestamp establishes record recency only, not a specific deal change,75 direction, magnitude, or cause.76 - Report an in-window slip only when dated evidence places a postponement or a newly77 crossed close deadline while the deal remained open inside that window. Already78 overdue before the baseline is a separate current overdue status, not a new slip.79 Apply the same timing test to stage regression, likelihood/value decline, and won/lost80 transitions. If evidence brackets only a broader interval, state it and leave change81 inside the requested window unknown.824. Establish why each material change happened from actual evidence — supplied notes, messages,83 meeting records, or other communication — read at the content level, not inferred from a84 status field alone. Attribute the reason to its source and, where known, the person. A85 change with no available evidence for its reason is still reported, with the reason marked86 unknown; an unconfirmed reason on one deal does not block reporting the rest of the digest.875. Compare a source-attributed signal with established current record state before flagging88 it as not reflected in the record. Without that comparison, label it an unverified update89 candidate. Do not apply an update.906. Compose per deal: what changed, the substantiated (or marked-unknown) reason, any91 record-update flag, and a suggested next action. When the evidence surfaces an92 internal alignment need or dependency that changes the next step, name it as an93 optional field distinguishing a known dependency, a decision still needed, and a94 suggested seller action — never a guessed colleague or area of expertise. Order by95 the stated impact basis (slip severity, value, or another stated criterion).9697## Judgment98- A record-modification timestamp establishes recency only. Use dated change evidence to99 establish movement and substantive evidence to establish its cause.100- A generated "what changed" narrative is a lead to verify, not a verified source fact; cite101 the actual evidence, not the narrative, for the reason.102- An absent reason is a per-deal gap, not grounds to withhold the rest of the digest. Report103 the change and mark the reason unknown.104- Do not claim "no changes" or "all signals reviewed" unless the evaluated coverage actually105 supports it — state what was checked.106- A missing baseline yields a current-state, dated observation, with movement explicitly107 marked unknown — never a fabricated prior state or an invented "no change" result.108- State the selection basis, presentation cap, and comparison period used. A cap controls109 presentation, not business importance; a different cap, named list, or window is valid.110- A stated "top" set reflects the deals actually evaluated. When the underlying evidence pull111 is itself bounded or paged, say so — a partial read is not the genuine top of the full book.112113## Output114115Deliver both a concise chat summary and one saved primary editable artifact, following the116sections below. The artifact must explain what changed and why across a scoped deal set, marking unsupported movement or117causes unknown.118119### Chat summary120121In chat, summarize the largest evidenced movement, its best-supported reason, the most material122regression or unknown, and the next action. State the examined scope and window so the summary123cannot be mistaken for a complete portfolio view.124125### Artifact content126127Identify the ownership or membership evidence that establishes the requested deal set. Separate verified members from unresolved candidates; correspondence alone does not establish ownership. Preserve supported observations for candidates without including them in unqualified portfolio claims or asserting movement outside the verified baseline and period.128129State scope, requested window, available baseline (or its absence), selection basis/cap,130evaluated deal count, and coverage. Then, per deal: verified movement and its dates, or131current state with change unknown; the substantiated reason (or "unconfirmed" with what132was checked); any record-update flag or unverified candidate; an optional internal133dependency field when the evidence supports one; and a proposed next action. Keep134existing overdue status separate from verified in-window slips.135136## Artifact selection137138Choose one format for the complete internal deal catch-up, respecting the user's requested format:139140- **Word (.docx):** Default for explaining what changed, why and what to do next.141- **Excel (.xlsx):** Instead for filtering a scoped multi-deal chronology or action handoff, with takeaways and causal explanations retained.142- **Markdown (.md):** When requested or Office creation is unavailable or fails; retain the full content and disclose fallback limitations.143144Use authorized, format-specific workflows. Keep content concise and styling simple. Plan changes together and apply them in as few supported batches as practical. Update authorized existing artifacts without creating duplicates or changing unrelated content. Follow Delivery and control for saving and reporting.145146### Delivery and control147148Verify the save before reporting success and provide the actual link or location. If saving fails, disclose it and provide clearly labeled unsaved catch-up in chat.149150## Guardrails151This report is read-only except for creating and saving the requested file artifact in an152authorized location. It does not update records, send messages, or take any other action on a153customer's or seller's behalf. A record-update flag is a proposal for the user to apply, not an154applied change.155156## When NOT to Use157- Not for choosing which deals to work next; use `pipeline-prioritizer`.158- Not for one deal's complete standing review; that requires a separate review procedure outside this catalog.159- Do not report a change as confirmed from a record-modification timestamp alone, and do not160 claim complete coverage from a partial or capped evidence pull.161162## Required information163- **Minimum:** an identifiable account or deal scope. Accessible correspondence, meetings,164 notes, proposals, or supplied material can support a visible-evidence reconstruction without165 a current CRM opportunity snapshot.166- **Structured-state enrichment:** current opportunity evidence improves current-state and167 field-level comparisons but is not required for the baseline catch-up.168- **Comparison evidence:** a resolved comparison period plus dated prior/current evidence169 or a dated change event establishes movement within that period. Without it, report170 current state and dated observations, with change unknown.171- **Reason evidence:** substantive notes, messages, meeting records, or other evidence.172 Its absence leaves the reason unknown for that deal, not the whole result unavailable.173- **Missing-input question:** "Which account or deal set should I catch up on?"