Gemini 4 Neon: reconcile a client’s PDF and spreadsheet brief
Google announced Gemini 4 Neon on November 18. If your account has access, try reconciling a fictional PDF offer card and spreadsheet update against explicit client instructions. Require a source location and authority rule for every accepted fact. Preserve unchanged fields, date limits and unknowns. Have the client approve the resulting facts before they become social posts.[1]
Use the announcement for a specific agency task
Google says Neon can combine inputs including spreadsheets and PDFs into structured work. Its announcement lists a rollout to Pro and Ultra subscribers in the Gemini app. Check availability in your own account. This exercise examines a useful preparation task; it provides no measured result for Neon.[1]
A client sends an offer card, a newer spreadsheet and a coach’s draft. Before writing captions, reconcile which source controls each fact. A later file can update one price without replacing a booking address or duration. Deliver a short facts register with source locations and unresolved questions, so the client can review the exact inputs to the next campaign.
Supply all four inputs and the client’s authority rule
Tern Cycle Studio, workspace TC, is fictional. The exercise review clock is November 19, 2026 at 2 AM America/Los_Angeles. The intended post date is November 21, 2026. Input A, offer-card.pdf page 1, is approved November 10 and gives INTRO class price $45, duration 50 minutes and booking path /intro. It supplies no capacity. These are transcribed teaching inputs; no actual file was opened.
Input B, offer-register.csv row 2, is approved November 18. It gives service INTRO, price $39, start November 20, end November 27, duration blank and booking path /classes/intro. Capacity is blank. Input C, coach-notes.pdf page 2, is an unapproved draft saying capacity 10. Input D, other-client.csv row 2, belongs to Moss Yoga, workspace MY, and gives an INTRO class price $29, duration 60 minutes and booking path /yoga.
The supplied client instruction is precise: A remains authoritative except that B replaces INTRO’s price on November 20 through November 27 inclusive, in America/Los_Angeles. B has authority for that price and its date window only. Its other fields cannot replace A. Blank cells make no deletion instruction. C is unapproved; D belongs to another client. No source or instruction supplies an approved capacity.
Produce one traceable facts handoff
For the November 21 post, accept $39 from B within the approved window. Retain A’s 50 minutes and /intro path. B’s different path is visible in the register, but the explicit price-only instruction does not authorize adopting it. Keep capacity unknown despite C’s suggestion. Exclude D before any of its matching service labels can influence TC’s facts.
The six reference rows contain four accepted fact decisions, one unresolved capacity and one excluded client input. The offer window is an accepted fact, not permission to run the $39 copy indefinitely. If the intended post moves outside that window, reevaluate the price against the instruction and current client approval before drafting. These decisions are an authored answer key, not a model response.
Try the reconciliation without publishing anything
Reusable prompt: Attach the complete fictional A through D input descriptions and the full TC instruction, including the review clock and intended post date. Provide the first two worksheet columns. Return F1 through F6 with source location, governing rule, accepted fact or unresolved question. Apply B only to the price and date window. Preserve blanks and A’s other approved fields. Separate MY from TC. Do not infer approval from a newer filename or from a repeated service label. Prepare the facts register only; do not draft a public offer, access accounts, change settings, publish or contact anyone.
Run that prompt in a fresh chat if Neon is available. Keep the response, displayed model identity and source references, then compare every decision with the answer key. A capacity of 10, /classes/intro as the approved path, or an undated $39 offer fails this exercise. With real files later, verify that each cited page or row was read correctly and that extraction did not lose blanks, headings or client identity. This example supplies no actual run or score.
Make the approved brief a recurring client deliverable
Offer the reviewed register and capacity question as the handoff before content creation. After client confirmation, retain the approved version alongside the next content brief. AgencyPro’s documentation describes operating assigned client workspaces through one integration. Evaluate AgencyPro for that separate client delivery workflow. This guide’s document reconciliation happens in the assistant; it establishes no Sociamonials PDF parser or Neon connection.[2]
Illustrative TC source reconciliation for a November 21 post
| Decision | Supplied input | Governing authority | Reference handoff |
|---|---|---|---|
| F1 / INTRO price | A p1: $45. B r2: $39 for Nov 20–27. Intended post Nov 21. | B price override applies on the intended local date. | Accept $39 for this post with the Nov 20–27 window attached. |
| F2 / Duration | A p1: 50 minutes. B r2: blank. | B has price/date authority only; blank is no deletion. | Retain 50 minutes from A. |
| F3 / Booking path | A p1: /intro. B r2: /classes/intro. | A governs this field; B’s path is outside the authorized override. | Retain /intro. Record the unused conflicting B value for client review. |
| F4 / Capacity | A: absent. B r2: blank. C p2: 10, unapproved draft. | Neither approved source supplies capacity. C cannot establish it. | Unknown. Ask the client; omit a capacity claim until confirmed. |
| F5 / Price window | B r2: Nov 20 through Nov 27, 2026 inclusive; America/Los_Angeles. | Client explicitly approves these dates for the price override. | Attach the exact window. Recheck price if the intended post date changes. |
| F6 / Other client | D r2: MY INTRO, $29, 60 minutes, /yoga. | D is Moss Yoga; the destination brief is TC. | Exclude all D facts from the TC handoff. |
When this approach needs adjusting
- All clients, documents, values, authority instructions and reference decisions are fictional teaching materials prepared with Codex. No files, model outputs or accounts were inspected or tested.
- This prompt exercises source reconciliation, not proof of model accuracy on real uploads. Inspect actual extraction and obtain client confirmation before using real facts.
- Access to Gemini and AgencyPro is separate. This example establishes no integration, purchase outcome or improvement in client results.
Return to this next week
Reconcile the next client’s changed offer sources before creating its weekly posts. Keep each accepted fact’s page or row, approval scope and date window, and resolve missing facts with the client.
See how AgencyPro fits your agency