Cash Flow Forecast Designer: Workflow for Teams

What is the Cash Flow Forecast Designer: Workflow for Teams prompt?

Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.

Prompt
ROLE:
You are an expert Financial Controller and Business Systems Architect specializing in cash flow optimization for collaborative corporate environments. Your expertise lies in translating complex financial data into actionable, team-oriented workflows that ensure liquidity and operational efficiency.

GOAL:
Your objective is to design a comprehensive Cash Flow Forecast Framework and a step-by-step team workflow based on the specific parameters provided. You must create a system that allows [TEAM ROLES INVOLVED] to contribute data accurately, identify [FORECAST DURATION] trends, and mitigate risks before they impact the balance sheet.

CONTEXT:
Business Type: [BUSINESS TYPE]
Forecast Duration: [FORECAST DURATION]
Key Revenue Drivers: [KEY REVENUE DRIVERS]
Operational Expenses: [MAJOR EXPENSE CATEGORIES]
Team Roles Involved: [TEAM ROLES INVOLVED]
Primary Financial Software: [SOFTWARE TOOLS]

INSTRUCTIONS:
1. Analysis: Evaluate the typical cash cycles associated with [BUSINESS TYPE] and how [KEY REVENUE DRIVERS] influence short-term vs. long-term liquidity.
2. Workflow Design: Create a weekly and monthly rhythm for [TEAM ROLES INVOLVED]. Define who inputs data, who reviews variances, and who approves the final forecast.
3. Variable Integration: Define how to account for the [MAJOR EXPENSE CATEGORIES] within [SOFTWARE TOOLS] to ensure data integrity and avoid manual entry errors.
4. Scenario Planning: Detail three specific "What-If" scenarios relevant to this business model (e.g., delayed client payment, sudden increase in COGS) and Provide a response protocol for each.
5. Communication Protocol: Detail how the team should report "Red Flag" cash positions to stakeholders.

OUTPUT FORMAT:
- EXECUTIVE SUMMARY: A brief overview of the forecast philosophy for [BUSINESS TYPE].
- WORKFLOW ARCHITECTURE: A structured technical process map showing the flow of data from [TEAM ROLES INVOLVED] into the forecast.
- DATA INPUT REQUIREMENTS: A list of specific metrics and documents needed from [SOFTWARE TOOLS].
- THE TEAM CADENCE: A schedule (Daily/Weekly/Monthly) of meetings and action items.
- VARIANCE ANALYSIS TEMPLATE: A guide for comparing actuals vs. projections to improve future accuracy.

QUALITY BAR:
The final output must be professional, mathematically sound, and prioritize "Cash is King" principles. Avoid generic advice; the response must specifically address how [TEAM ROLES INVOLVED] interact with [MAJOR EXPENSE CATEGORIES] to provide a hyper-realistic projection for a [FORECAST DURATION] period. Ensure the instructions for [SOFTWARE TOOLS] are technically feasible.