Act as a production coordinator at a media ad agency. Draft a data entry initiation email to the SEPO team. Project details: - Project ID: [Project ID] - Client/Account: [Client name, e.g. Google] - Estimate type: [Original / Revision / Actualization] - Job folder: [Paste Google Drive link] - Key callouts: [e.g. "vendor X is always preferred" / "cost-plus pricing applies" / "endorsed stamp = standard review"] Format: Short email with subject line. Professional but friendly. Bullet list for callouts only.

I'm writing up a savings entry for a production project and need to make sure it's documented well enough to pass BI validation. Here's what happened: - Type of saving: [e.g. Vendor rate negotiation / Scope reduction / Rebid] - Original cost: [$X] - Final cost: [$Y] - How I achieved it: [Brief description, e.g. "Renegotiated director day rate from $X to $Y by presenting competing bids"] - Backup documents available: [e.g. Version 1 estimate + Version 2 estimate / Competing bid documents] Write a clear savings note I can paste into the savings module. It should: (1) state the saving amount, (2) explain what type of saving it is, (3) reference which documents validate the numbers. Under 80 words.

A client asked me this question: "[Paste the question]" My intuitive answer is: [What you'd normally say] Help me think through: (1) what data or evidence would make this answer more credible, (2) what questions I should ask myself before responding, (3) how to frame my answer if I have partial data but not a complete picture. I want to be honest with the client about what I know vs. what I'm estimating.

Using the framing above, draft a 3-4 sentence response I can send to the client. Be direct. Acknowledge where I'm drawing on experience vs. hard data. Don't oversell the certainty. Tone: confident but honest.

Act as a quality control advisor at a production management agency. I'm about to close a project. Client: [Client name] Project type: [e.g. Film / Stills / Events / Digital] Modules completed by SEPO: [e.g. estimates, bids, deliverables, shoots] Modules I'm responsible for: [e.g. savings, GAFFY fee validation] Create a structured pre-close checklist grouped by module. Flag which fields are most likely to cause downstream BI validation errors if left blank or wrong.

I reviewed the project and found these issues: [e.g. "Savings module blank" / "Vendor marked non-preferred but client profile says always preferred" / "Bid totals don't match estimates module"] Which of these is most likely to break the BI report downstream? List them in priority order with a one-line reason for each.

I'm uploading a client profile for [Client name]. Extract the content into these sections: 1. Vendor rules (always preferred / never use / conditional) 2. Stamp/estimate type rules (what each means for data entry) 3. Module-specific rules (which modules apply and how to complete them) 4. Fee rules (e.g. GAFFY, cost-plus, agency fee specifics) 5. Any unclear or contradictory instructions (flag for advisor review) Format: numbered list under each section. Plain language. Flag anything that seems outdated or contradictory.

I'm a data entry specialist completing a project and need to flag pending items to the advisor. Project ID: [Project ID] What I completed: [Brief summary of what you entered] Fields I left pending (and why): - [Field name]: [Reason, e.g. "Savings module — no savings data in job folder" / "Vendor preference — stamp says endorsed but client profile doesn't have a rule for this stamp type"] Write a professional note under 150 words that: (1) confirms what I completed, (2) lists pending items with a clear reason for each, (3) tells the advisor exactly what I need from them. No blame language. Specific enough that they can reply without asking a follow-up question.

I'm about to validate Google Agency Fee (GAFFY) entries for the following projects. Help me prepare a structured validation approach. Number of projects to validate: [number] What I'm checking: [e.g. fee percentages, project IDs, estimates match, correct fee category applied] Common errors I've seen before: [e.g. wrong fee tier selected / fee applied to wrong estimate version / missing documentation] Create a short field-by-field validation checklist I can use for each project. Format as a table: Field | What to check | Common error to watch for. Keep it to the most important fields only — I need to move quickly.

Act as a BI analyst at a media production company. I completed a data validation pass and found discrepancies I need to communicate to the advisor. Client: [Client name] Report period: [e.g. Q1 2026] Issues found: - [Issue 1: e.g. "Project 2045 — savings module has no backup documents"] - [Issue 2: e.g. "Project 2089 — bid totals don't match estimate figures"] - [Issue 3: e.g. "Project 2103 — savings entry references a document not in the job folder"] Write a concise validation findings note. Include: (1) what I reviewed, (2) specific issues with project IDs, (3) exactly what I need from the advisor to resolve each issue, (4) a suggested deadline. Tone: factual, collaborative, zero blame language. This is a "data quality check" note, not a rejection.

Act as a business insights analyst presenting quarterly performance to a marketing client. Client: [Client name] Period: [e.g. Q1 2026] Key metrics: - Total production spend: [$X] - Cost savings vs estimate: [$Y] - Bids reviewed: [number] - Any notable trends: [e.g. "Shoot costs up 12% vs prior quarter" / "Savings rate improved"] Write a 2-paragraph executive summary to open the quarterly presentation. Lead with the most important finding. Tone: data-driven, confident, client-friendly. No jargon.

Based on those findings, draft 3 forward-looking recommendations for next quarter. Each must: (1) reference a specific finding, (2) suggest one concrete action, (3) state the expected outcome. Format as a slide — brief headline + 2-sentence explanation per recommendation.

I'm a BI analyst and received this data request: "[Paste the request exactly as received]" Help me: (1) identify the 3-4 clarifying questions I need answered before starting (deadline, data scope, format needed, purpose/audience for the output), (2) draft a short reply asking those questions. Tone: friendly, collaborative, not unhelpful. Under 100 words for the reply.

Write a clear, 2-3 sentence explanation for an account team explaining why a specific data point from our insights dashboard cannot be used in their client report. Reason: [e.g. "Only 2 clients contribute to this segment — below our minimum of 3" / "Google represents more than 33% of the data in this benchmark, which violates our data-sharing constraints"] The explanation should: (1) state the data is unavailable for reporting, (2) give the reason simply, (3) suggest an alternative (e.g. "you can use this internally but not in a published report" / "try filtering for a broader region where you have more data points"). Tone: direct, no jargon, no apology language.

Acting as a senior project manager, generate a structured report from the attached meeting transcript. Include these sections: 1. Meeting summary (3 sentences max) 2. Decisions made (what was agreed) 3. Action items — format as: [Owner] → [Task] → [Deadline if mentioned] 4. Open questions still needing answers 5. Information or data that was requested Format: bold section headers. Action items as a numbered list.

Using the action items above, draft a follow-up email to send to the full team. Recipients: [e.g. Client team + internal team] Tone: professional, direct. Include: subject line, brief recap (2 sentences), numbered action item list, note on open questions still pending, next meeting date if it came up.

I'm going to describe a work process in rough, conversational terms. Reorganize it into a clear, numbered step-by-step workflow document. Process name: [e.g. "SEPO Data Entry Initiation" / "Advisor Project Close-Out"] Who does it: [Role] Trigger: [What starts this process] Here's the process as I know it: [Describe it however it comes out — Gemini will clean it up] After I finish, organize this into: (1) numbered steps, (2) who owns each step, (3) what system or tool is used, (4) common mistakes to avoid, (5) decisions that vary by account or advisor.

Review this process document. What steps are unclear? What would confuse someone doing this for the first time? What decisions have no clear rule? List every gap — I'll go fill them in before sharing with the team.

I need to create a quick-start onboarding guide for a new advisor joining the [Client name] account team. What I know about this account: - Key SEPO rules: [e.g. stamp types and what they mean, vendor rules] - Data entry specifics: [e.g. modules they care about, typical project types] - Common mistakes new advisors make: [e.g. missing savings documentation, wrong fee category] - Who to contact for questions: [Names/roles] - Tools and folders they need access to: [Google Drive structure, tracker locations] Create a one-page quick-start guide with: (1) "First week" checklist, (2) key rules at a glance, (3) who to ask for what, (4) the 5 most common mistakes and how to avoid them. Keep it scannable — no paragraphs over 3 sentences.

I'm running a team project status meeting. Here's a snapshot of our tracker: Total projects: [number] Completed: [number] Pending advisor response: [number] In progress with SEPO: [number] On hold / flagged: [number + brief reason if known] Items needing a decision today: [List any specific projects] Write a 3-sentence verbal status update to open the meeting. Follow it with a bulleted list of the top 2-3 items the group needs to decide or act on today. Format: spoken summary paragraph → action bullets.

Act as my business advisor. I work at a media production management company and want to solve this workflow problem: Problem: [Describe it plainly — e.g. "Projects submitted to SEPO sit pending for months with no visibility. Advisors don't follow up because there's no in-system status tracking. SEPO has a spreadsheet tracker but it's not connected to the main platform."] Constraints: [What can't change — e.g. "Must work within Google Workspace. No major platform rebuild. Low developer hours available."] Give me 3 approaches to fix this. For each: (1) describe the solution, (2) effort level (low/medium/high), (3) main risk or limitation.

I want to test option [#]. What 3-5 steps can I take this week to pilot it? Assign one owner per step. Format as a simple numbered task list.

Write a structured admin request message for this system update: Request type: [e.g. Add new vendor / Add new user / Update campaign / Add agency contact / Add venue] What's needed: [Plain language description] Details: [Name, ID, contact, account, category, or whatever applies] Why it's needed: [Brief context] Urgency: [Deadline or "no rush"] Format: Subject line, Request type, Details as bullet list, Urgency note. Under 120 words.

I'm preparing a presentation on [topic, e.g. Q1 production performance review]. My goal: [e.g. show Google their cost savings and flag two projects that need scope decisions]. Audience: [e.g. Google client team — 5 senior marketing managers] Time available: [e.g. 30 minutes] Give me 3 different ways to structure this. For each structure: what it leads with, what it risks leaving out.

I'm going with structure [#]. Now act as a skeptical client at this meeting. What are the 3 hardest questions they're likely to ask? For each question, suggest how I should respond.

I need to document data quality rules for a specific module so they can be shared with advisors and SEPO. Module: [e.g. Savings / Estimates / Bids / Deliverables / Shoots / GAFFY] Account: [e.g. Google / All accounts] Rules I know: [List them however you know them — Gemini will organize] Common errors I see repeatedly: [List them] What "good" looks like: [Describe a correctly completed entry] Organize this into a data quality rule sheet with: (1) required fields and what goes in each, (2) conditional rules (if X then Y), (3) common errors and how to catch them, (4) what to do if you're not sure. Format as a table where possible.

Act as a business development consultant for a production management company. I'm building a pitch narrative to show a prospective client the value of working with us. Prospect type: [e.g. Global brand with large production budgets / Regional marketing team scaling production] Data I have to back this up: [e.g. "Average 12% cost savings vs estimate across clients" / "Rebid success rate" / "Average time from estimate to production close"] What makes us different: [Your differentiators — data, SEPO program, benchmarks, etc.] Draft a 3-paragraph pitch narrative that leads with a client pain point, introduces our solution with specific data, and ends with a clear value statement. Tone: confident, data-backed, not salesy.

Turn that narrative into a 3-slide structure for a new business deck. For each slide: (1) slide title, (2) 2-3 key points, (3) what visual or data point would go here. Format as a simple outline.

Act as a production cost advisor. I've received multiple bids for a project and need to compare them before the bid treatment meeting. Project type: [e.g. TVC / Stills / Digital / Events] Client: [Client name] Bids received: [Number of bids] Bid summaries: - Bid 1 ([Company name]): Total [$X]. Key line items: [Director rate, shoot days, post, etc.] - Bid 2 ([Company name]): Total [$Y]. Key line items: [Director rate, shoot days, post, etc.] - Bid 3 ([Company name]): Total [$Z]. Key line items: [Director rate, shoot days, post, etc.] Create a comparison table: Bid | Total | Key variance items | What stands out (high/low vs expected). Then write a 2-sentence summary of where the biggest cost differences are.

Based on this comparison, help me prepare for the negotiation. The preferred bid is [Bid #] but the client's budget ceiling is [$X]. What are the 3 strongest arguments I can use to negotiate down the cost? What should I ask them to reduce first without affecting the creative? Keep each argument to 2 sentences.

I need to write a director recommendation for a client who is choosing between two options. Client: [Client name] Project type: [e.g. brand film / TVC / stills campaign] Director being recommended: [Name] Why I'm recommending them (my notes): [What I know — past projects, experience, style, any firsthand insight] Alternative director being considered: [Name and any relevant context] Client's concerns or priorities: [e.g. "They want someone who's worked with their category before" / "Budget is tight so they want predictability"] Write a 3-4 sentence director recommendation I can include in an email or present verbally. Lead with the strongest reason. Sound confident, not salesy. End with what specifically makes this the right choice for this brief.

Act as a production compliance advisor. I need to build an audit-ready folder checklist for a completed project. Client: [Client name] Project type: [e.g. TVC / Stills / Events / Digital] Audit requirements I know about: [e.g. "L'Oreal requires 15%+ savings documented" / "Single bid waivers must be in the root folder" / "All estimate versions must be retained"] Scope of work: [Brief description] Create a folder checklist grouped by document type: (1) Estimates and bid documents, (2) Savings evidence, (3) Vendor contracts and approvals, (4) Compliance documents (waivers, approvals), (5) Correspondence. For each item, note: required or recommended, and where it should live in the folder structure. Flag anything that's commonly missing.

I'm reviewing a data point from our production management system and something looks off. Help me think through whether this number is reliable before I share it with a client. The data point: [e.g. "Director day rate of $X for a TVC in Los Angeles"] Why it looks suspicious: [e.g. "It's 3x higher than what I'd expect for this director category"] What I know about the project: [Any context — project type, client, year, scope] Give me: (1) a list of likely reasons this number could be inflated or wrong (e.g. line items rolled up incorrectly, wrong category selected), (2) what I should check in the source documents to verify it, (3) how to explain to the client that I'm validating the data before sharing it — in one sentence, no alarm language.

Act as a production management advisor specializing in integrated and non-traditional production. I need to structure a response to an RFP. Client: [Client name] RFP type: [e.g. Influencer program / Events and activations / Supplier RFP / Print and below-the-line / 360 integrated] What they're asking for: [Paste or summarize the brief] Our relevant experience: [What we've done in this space] Key differentiator we want to lead with: [e.g. data-backed savings / SEPO program / benchmark access] Outline the structure for our RFP response: section headings, what to cover in each section, and what to include as evidence or appendices. Keep it to 5-6 sections maximum.

Write the executive summary section of this RFP response. 2-3 paragraphs. Lead with the client's problem, then our solution, then why us. Tone: confident, specific, not generic. Avoid buzzwords like "seamless" or "end-to-end."

I need to reconcile the deliverables for a completed project. What was entered at award has changed significantly by post-production. Project: [Project name / ID] Client: [Client name] Deliverables entered at award: [Paste list or describe — e.g. "3x 30sec TVCs, 2x 15sec cut-downs, 5x social assets"] What actually delivered (from completion report / agency): [Paste or describe actual output] Do the following: (1) create a reconciliation table showing Original vs. Final vs. Status (added / removed / changed / unchanged), (2) flag anything that was planned but not delivered, (3) flag anything delivered that wasn't in the original scope, (4) write a 2-sentence note I can add to the project record explaining the changes. Format the table cleanly — I may paste it into a report.

Write an email to an agency contact requesting a production completion report for a finished project. Project: [Project name] Client: [Client name] Agency contact: [Name / role] What I need confirmed: [e.g. final list of all assets delivered / trafficking destinations (paid vs organic) / any scope changes from original brief] Deadline: [Date or "end of week"] Format: short email with subject line. Include a clear list of exactly what information I need — formatted so they can respond point by point. Friendly but specific. Under 150 words.

I need to create a client tier framework that maps each account to its workflow and data entry requirements. Clients to map: [List clients with any notes you have, e.g.:] - L'Oreal: audit trail critical, 15%+ savings target required, full documentation - PepsiCo: advisor presence on set is priority, savings less critical, lighter documentation - Google: specific data fields required, GAFFY fee validation, strict module completion - [Add others] Organize these into 3 tiers: Tier 1 (full workflow, strict documentation), Tier 2 (standard workflow, moderate documentation), Tier 3 (lightweight workflow, advisor-led). For each tier, define: (1) required modules to complete, (2) documentation required before close, (3) savings documentation level, (4) SEPO involvement level. Format as a table.

Help me design a standard job folder structure for production projects that any advisor or contractor can follow consistently. Project types we run: [e.g. TVC / Stills / Events / Digital / Integrated] Documents that must always be easy to find: [e.g. single bid waiver, stamped estimate, savings evidence, vendor contracts, client approval emails] Our current approach (what exists, even if messy): [Describe or skip if starting fresh] Platform: [Google Drive / OneDrive / Both] Design a folder structure with: (1) top-level folders (max 6 — keep it simple), (2) what goes in each, (3) naming convention for files, (4) which folders must be created at project setup vs. added later. Then write a one-paragraph instruction I can share with contractors explaining the structure and why it matters.

I need to build a cost-per-deliverable summary for a completed project to show the client their procurement savings. Client: [Client name] Period: [e.g. Q1 2026 / Full year 2025] Projects included: [Number or list] For each project (or in aggregate): - Total deliverables produced: [number and types] - Original estimated cost: [$X] - Final actual cost: [$Y] - Savings achieved: [$Z and/or %] - Key savings drivers: [e.g. bid negotiation, scope reduction, vendor rebid] Create: (1) a cost-per-deliverable table (deliverable type | estimated cost | actual cost | savings), (2) a 2-sentence executive summary of the savings story, (3) a one-line client-facing statement they can use internally to report on APR's value. Format the table so it can be copied into a PowerPoint slide.

Write a brief project hold notice to send to the SEPO team and any relevant parties. Project ID: [ID] Client: [Client name] Reason for hold: [e.g. "Client has paused the production pending budget approval" / "Estimate revision in progress" / "Awaiting creative brief from agency"] Expected resume date: [Date or "TBD — will update by 2026"] Any actions needed while on hold: [e.g. "No action needed" / "SEPO please do not proceed with data entry until further notice"] Format: Short email or note, subject line included. Under 80 words. Clear, friendly, no unnecessary detail.

I'm attaching project notes, takeaways, and description fields from a production project. A specific data point looks unusual and I want to understand why. The unusual data point: [e.g. "Director day rate is $X — much higher than expected for this project type"] What I expect it to be: [Your benchmark or instinct] Read through the attached notes and: (1) identify any context that would explain this number, (2) flag any mentions of scope changes, unusual arrangements, or added costs, (3) tell me if the notes justify this figure or if the data looks like an entry error. Give me a plain-language explanation in 3-4 sentences that I could share with a client if needed.

Based on that analysis, write a 2-sentence explanation I can include in a report or email to the client explaining why this figure is what it is. Factual, no hedging, no alarm language.

Act as a production workflow trainer. I work at a production consultancy and I need a plain-language reference guide that explains each project milestone date field and when to enter it. Project stages we use: Pre-bid → Bidding → Award → Pre-production → Production → Post-production → Job Wrap For each stage, tell me: 1. What the date represents (what actually happened on that date) 2. When I should enter it (immediately? end of day? only once confirmed?) 3. What NOT to do (common mistakes — e.g. backdating, using today's date as a placeholder) Format as a simple table with three columns. Plain language, no jargon.

Act as an account operations manager. I manage multiple brands on one client account and need to run a weekly status check to make sure all awarded jobs are captured in our production tracking system. My current situation: - Number of active brands/projects: [e.g. 12 brands, ~30 active projects] - Team mix: [e.g. mix of staff and independent contractors] - Biggest gap: Jobs that are awarded but not yet entered in the system, missing budget data, or projects that closed without a final entry Create a weekly status check template I can fill in before my status call. Include: (1) jobs to confirm as awarded, (2) jobs missing Acero entry or budget, (3) projects approaching close that need data cleanup, (4) any ICs with outstanding actions. Keep it simple — this should take me 10 minutes to fill, not 30.

Based on the template above, draft a short Slack or email message I can send before the status call to the advisors on my team. The message should: list the specific projects that need to be in the system by end of day, be direct but not accusatory, and make it easy to reply with a quick update. Keep it under 100 words.

Act as a managing advisor at a production consultancy. I need to write a short, professional brief for an independent contractor joining my account team. The brief should clearly explain their data entry and validation responsibilities so there are no disputes later. Context about this IC engagement: - Account: [Client name] - IC's role: [e.g. Production advisor reviewing bids and shoots] - Data they'll be responsible for: [e.g. savings entries, bid review, deliverable confirmation] - Third-party data entry involved: [Yes/No — e.g. offshore team entering granular line items] Write a 200-word brief that covers: what data they own, what they're responsible for reviewing even if entered by others, what to do when something looks wrong, and the timeline for corrections when BI sends a validation note. Firm but professional tone — this is onboarding documentation, not a complaint.

I've received a SEPO data entry initiation email. I need to create a log entry for our Google Sheet tracker before I begin. Here is the initiation email: [Paste the full email] From this email, extract and format the following fields as a single spreadsheet row: - Date received - Project ID - Client / Account - Estimate type (original / revision / actualization) - Advisor name - Job folder link - Key callouts or special instructions - Assigned to (leave blank for me to fill) - Status (set to: In Progress) If any field is missing from the email, write "Missing — follow up with advisor" in that cell.

Act as a data operations coordinator. I need to write a clear, factual audit note documenting a data change in a production tracking system. Here is what the recent activity log shows: [Describe or paste what the log shows — who changed what, when, what the original value was, what it changed to] The error was flagged by: [e.g. BI validation / advisor / client team] SEPO's original entry date: [Date] When the change occurred: [Date — after SEPO marked complete] Write a 3-4 sentence audit note that: (1) states the facts of the change without accusation, (2) confirms SEPO's original entry was correct, (3) recommends a next step (e.g. advisor to review and correct, or flag for process review). Neutral, professional tone.

Act as a BI analyst at a production consultancy. I want to build a report on project turnaround speed and delivery agility, but our milestone date fields are inconsistently filled. Here is a sample of what date fields I have populated and how complete they are: [Describe what's available — e.g. "bid received date is ~80% populated, award date is ~60%, project open date is ~95%, production start is ~30%"] Client or scope: [Client name or project type] Time period: [e.g. Q1–Q3 2024] Based on this, tell me: (1) which date-to-date gaps are calculable with enough data to be meaningful, (2) which ones have too many nulls to report on reliably, (3) what caveats I need to include in any agility metric I publish. Be direct — I'd rather know what I can't say than publish something that gets challenged.

Based on the available data and the caveats we identified, write a 3-sentence agility narrative I can include in a client report. It should present what we can prove, acknowledge where data is limited, and frame the improvement opportunity honestly. No inflated claims.

Act as a BI analyst onboarding a new client to a production data reporting program. I need to define what data we'll track and report on before building the first report. Client context: - Client name / type: [e.g. large CPG brand, retainer client] - Production types they run: [e.g. broadcast, experiential, digital] - Report cadence they've requested: [Monthly / Quarterly / Annual] - What they care most about: [e.g. savings, spend by category, cost per deliverable, agility] - Any custom fields specific to this client: [If known] Give me a structured onboarding checklist that covers: (1) which data modules to validate for this client, (2) which fields are critical for their reporting goals, (3) what I need to confirm with the advisor before building, (4) what a "clean enough to run" threshold looks like for first report. Format as a checklist.

Based on the checklist, draft a short email to the managing advisor explaining which data fields are critical for this client's reporting, what needs to be filled in consistently from day one, and what happens to the report if those fields are missing. Keep it under 150 words — practical, not lecturing.

Act as a BI lead at a production consultancy. I want to write a short internal communication to our advisor team that builds enthusiasm for data quality — not compliance, enthusiasm. The specific data gap I want to address: [e.g. "milestone dates not being filled in" / "savings entries missing backup docs" / "deliverables not updated at close"] The benefit to advisors if this improves: [e.g. "you'll be able to answer client questions in 30 seconds instead of digging through dashboards" / "your savings numbers will be credible in the next review"] Tone: Practical, collegial. Not a policy announcement. Not a guilt trip. Write a 150-word message I can send to the advisor team. It should: explain what we're seeing, show what good data makes possible for them personally, and make one clear ask. No bullet points — this should read like a human wrote it.

Act as a production advisor. I've received the initial brief and materials for a new project at the pre-bid stage. I need to create a structured pre-bid summary I can file in the job folder before bidding begins. Here are the materials I have: [Attach the brief, email, or paste the relevant content] Extract and organize the following into a clean summary: 1. Job overview (client, project name, type of production) 2. Creative direction (attach or summarize) 3. High-level budget range (if stated) 4. Draft schedule / key dates 5. Draft deliverables (list what's been requested) 6. Usage rights / distribution (if mentioned) 7. Open questions (anything missing that we'll need before bids go out) Format as a one-page summary. Flag anything that's missing with "TBC — needed before bid."

Act as a production delivery consultant. I need to determine the correct service tier and engagement point for a new project, and communicate it to the client and internal team. Project details: - Client: [Client name] - Project type: [e.g. broadcast TVC / experiential / digital / print] - When APR was engaged: [e.g. before kickoff / at pre-bid meeting / post-award] - Scope of work agreed: [Brief description or attach SOW] - Any special arrangements (e.g. reduced cost, project-only basis): [Note here] Based on this, tell me: (1) which service tier this project falls into, (2) which milestones APR is responsible for from this engagement point, (3) what needs to be set up in the project record to reflect this correctly, (4) any flag if we're being asked to deliver scope outside what the tier covers. Plain language, no jargon.

Act as a production advisor documenting on-set activity for a project record. I attended the shoot today and need to capture what happened — especially any negotiations, savings, or scope changes — in a format I can enter into our system. Here's what I remember from today: [Type your bullet notes — e.g. "negotiated craft services down $3k, director wanted extra setup hour pushed back, agency tried to add unscripted VFX shot I flagged as scope change"] Project: [Project name / ID] Client: [Client name] Shoot date: [Today's date] Format my notes into: 1. On-set savings entry (what I negotiated, original vs. agreed cost, brief rationale) 2. Scope changes or deviations flagged (what was requested, what I said, outcome) 3. Shoot attendance note (that APR was present and actively managing) 4. Any follow-up actions for post-production Plain language, factual, ready to paste into project notes.

Act as a production advisor reconciling a project at job wrap. I need to document overages and produce a clear summary comparing what was approved vs. what was actually spent. Project: [Project name / ID] Client: [Client name] Approved total (from stamped estimate): [Amount] Here are the overages I'm tracking: [List each — e.g. "Extra shoot day: +$18,000 / Agency VFX additions: +$7,500 / Talent buyout amendment: +$4,200"] Create a job wrap overage table with: (1) line item, (2) approved amount, (3) actual amount, (4) variance, (5) reason / justification. Then write a 2-sentence summary I can include in a close-out note to the client.

Based on the overage table, write a cost-plus reconciliation note I can attach to the final invoice upload. It should confirm the approved base, itemize the adjustments, and state the final reconciled total. 150 words maximum. Professional, no ambiguity.

Act as a senior production advisor. I'm closing out a project and need to write a structured postmortem before it's marked complete. This will be filed in the job folder and used to brief the next advisor who works with this client. Project overview: - Client / Account: [Client name] - Project type: [e.g. broadcast TVC / experiential / digital] - Budget (approximate): [Approved / Final reconciled] - Key challenges during this project: [Bullet notes — what went wrong or was harder than expected] - What worked well: [What you'd repeat] - Client-specific notes: [Any preferences, sensitivities, or rules that future advisors should know] - Savings delivered: [Key negotiation wins] Write a 250-word postmortem structured as: (1) Project summary, (2) What worked, (3) What to watch for next time, (4) Client-specific guidance for the next advisor. Factual, useful, no fluff.