Allocate included retainer hours and potential overage

The problem

A monthly retainer can cover a fixed time quota while only excess work is separately billable. Splitting the threshold-crossing entry and reconciling prior billing is difficult when entries span projects or contract rules leave rounding, rollover or eligible work unclear.

Agent job

Prepare a deterministic time-allocation workpaper using owner-supplied retainer rules, preserving threshold crossings and holding ambiguous entries for billing review.

Expected output

A draft entry-level included/overage/unresolved allocation, entitlement reconciliation and billing questions; no invoice, charge or contractual entitlement is established.

Why an agent / simpler alternative

The agent can connect retainer wording to project mappings and explain ambiguous entries. Chronological allocation, quota depletion and conservation checks should be deterministic. A native retainer module or spreadsheet is simpler when the contract and mappings are stable; owner judgment is needed for scope, rollover and chargeability.

Who this helps

1. Project operations coordinator

2. Billing specialist

Before a pilot — required, unexecuted

1. Add entry timestamps or explicitly define the listed order as the ordering input before using the example as reusable test data.

2. If an earlier entry is held or unmapped, carry its uncertainty into later quota balances and overage allocations, or show bounded alternatives. Do not present later overage as definite merely because the earlier row was set aside.

3. Include a nonempty prior-billing ledger and independent expected results to test that previously billed work is not billed twice.

Evidence boundary

Human duty and problem-source context are separate from the authored workflow. The steps, prompt, synthetic example, acceptance checks and expected value are original proposals, not source-derived procedures or demonstrated agent results.

Setup requirements

1. Use one synthetic retainer and one billing period; supply explicit timezone and entry-order rule.

2. Represent all durations in minutes internally, retaining original units and rounding instructions.

3. Require a billing-owner decision for rollover, excluded activities and project mappings; do not infer terms from common practice.

Inputs and access

1. Name

   retainer_rule_copy.txt

   Source or owner

   Synthetic contract/billing owner

   Sensitivity

   Synthetic-only fixture. Invented quota, period, rounding and rollover terms; no legal identities. Any later export-copy pilot must exclude personal data, credentials and unrelated content.

   Permission needed

   This document describes a future test only. Owner must separately authorize the exact minimized copies and processing environment before any pilot; no live account access or provisioning.

   Scope

   Invented quota, period, rounding and rollover terms; no legal identities

2. Name

   time_entries.csv

   Source or owner

   Synthetic project owner

   Sensitivity

   Synthetic-only fixture. Entry ID, project code, timestamps, duration and synthetic work category; no worker names. Any later export-copy pilot must exclude personal data, credentials and unrelated content.

   Permission needed

   This document describes a future test only. Owner must separately authorize the exact minimized copies and processing environment before any pilot; no live account access or provisioning.

   Scope

   Entry ID, project code, timestamps, duration and synthetic work category; no worker names

3. Name

   project_retainer_map.csv

   Source or owner

   Synthetic operations owner

   Sensitivity

   Synthetic-only fixture. Approved synthetic project-to-retainer mapping with effective periods. Any later export-copy pilot must exclude personal data, credentials and unrelated content.

   Permission needed

   This document describes a future test only. Owner must separately authorize the exact minimized copies and processing environment before any pilot; no live account access or provisioning.

   Scope

   Approved synthetic project-to-retainer mapping with effective periods

4. Name

   prior_billing_quantities.csv

   Source or owner

   Synthetic billing owner

   Sensitivity

   Synthetic-only fixture. Entry-linked hours already treated as included/overage; no payment data or amounts. Any later export-copy pilot must exclude personal data, credentials and unrelated content.

   Permission needed

   This document describes a future test only. Owner must separately authorize the exact minimized copies and processing environment before any pilot; no live account access or provisioning.

   Scope

   Entry-linked hours already treated as included/overage; no payment data or amounts

Proposed steps

1. 1

   Extract quota, scope, ordering, rounding and carryover rules into a decision sheet; mark omitted terms unresolved.

   Input: Retainer copy and billing period

   Output: Retainer allocation specification with source clauses.

   Expected output: Retainer allocation specification with source clauses.

   Checkpoint: No rate, rollover or eligible-work rule is invented.

   Approval gate: Billing/contract owner approves the specification; the agent gives no legal interpretation.

2. 2

   Map each entry to the correct retainer/period using approved IDs; separate noneligible, duplicate and unmapped entries.

   Input: Time entries and project map

   Output: Eligible-entry ledger plus mapping exceptions.

   Expected output: Eligible-entry ledger plus mapping exceptions.

   Checkpoint: Each entry is assigned once or held; overlapping project labels do not double count time.

   Approval gate: Project owner resolves ambiguous mapping and work-category eligibility.

3. 3

   Sort eligible entries deterministically, split cross-period entries only under the supplied rule, and preserve ties as specified.

   Input: Eligible ledger and ordering rule

   Output: Ordered minute ledger with period-boundary splits.

   Expected output: Ordered minute ledger with period-boundary splits.

   Checkpoint: Allocated portions sum to each original entry duration; unknown timezone blocks boundary splits.

   Approval gate: Unspecified tie or boundary treatment requires owner choice before allocation.

4. 4

   Deplete included minutes entry by entry; split the first threshold-crossing entry into included and candidate overage portions.

   Input: Ordered ledger and approved quota

   Output: Quota-depletion ledger and threshold-crossing rows.

   Expected output: Quota-depletion ledger and threshold-crossing rows.

   Checkpoint: Included plus candidate overage equals eligible minutes and included total never exceeds the supplied quota.

   Approval gate: Candidate overage remains a review classification, not an authorization to charge.

5. 5

   Match previously treated hours by entry ID; flag duplicates, differences and missing prior-billing coverage.

   Input: Allocation ledger and prior billing quantities

   Output: Reconciliation of proposed allocation versus prior billing and unresolved residuals.

   Expected output: Reconciliation of proposed allocation versus prior billing and unresolved residuals.

   Checkpoint: Already invoiced hours are not added again to a proposed new billable quantity.

   Approval gate: Missing billing history blocks an invoice-ready conclusion; no invoice is generated.

6. 6

   Prepare a review packet showing the exact crossing row, held entries and decisions needed before billing.

   Input: Allocation, reconciliations and unresolved terms

   Output: Draft retainer-hours workpaper awaiting project/billing approval.

   Expected output: Draft retainer-hours workpaper awaiting project/billing approval.

   Checkpoint: No amounts or approved charges appear; all substantive billing decisions remain pending.

   Approval gate: Billing owner approves allocations and separately authorizes any invoice, credit or client communication.

Original starter prompt — proposed

Origin

editorial_proposal

Label

Original starter prompt for a future authorized synthetic test; not executed

Placeholders

1. billing_period

2. output_folder

3. prior_billing

4. project_map

5. retainer_rules

6. time_entries

Text

Allocate hours from {time_entries} using only {retainer_rules}, {project_map} and {prior_billing} for {billing_period}. Normalize to minutes, preserve original durations and apply the supplied ordering/rounding rules. Split the threshold-crossing entry explicitly. Keep unmapped work, unclear rollover or missing prior-billing evidence unresolved. Prove that included plus candidate overage equals eligible duration. Produce new draft allocation.csv and billing_questions.txt in {output_folder}; no rates need be inferred. Do not issue invoices, charge accounts or message clients. Every allocation awaits project/billing-owner approval.

Execution authorized

No

Expected output schema — proposed

Origin

editorial_proposal

Columns

1. entry_id

2. retainer_id

3. period

4. original_minutes

5. eligible_minutes

6. included_minutes

7. candidate_overage_minutes

8. held_minutes

9. quota_balance

10. prior_billing_ref

11. difference_reason

12. owner_decision

Record status

draft_pending_owner_review

Synthetic output illustration — not an executed result

Label

Clearly synthetic worked input/output illustration; authored expectation, not an observed result

Synthetic

Yes

Executed

No

Owner approval status

pending_not_obtained

Data

Synthetic inputs

Quota minutes

600

Order

entry timestamp ascending

Entries

1. Id

   SYN-E1

   Minutes

   360

2. Id

   SYN-E2

   Minutes

   180

3. Id

   SYN-E3

   Minutes

   120

Rounding

none

Prior billing

complete empty ledger

Illustrative expected rows

1. Id

   SYN-E1

   Included minutes

   360

   Candidate overage minutes

   0

2. Id

   SYN-E2

   Included minutes

   180

   Candidate overage minutes

   0

3. Id

   SYN-E3

   Included minutes

   60

   Candidate overage minutes

   60

Illustrative totals

Eligible minutes

660

Included minutes

600

Candidate overage minutes

60

Owner decision

pending

Human approval boundaries

1. Before any future pilot, the accountable owner confirms the exact synthetic or nonpersonal export copies, processing environment, scope and retention. No such approval or pilot is claimed here.

2. Project owner approves work eligibility and mapping; billing/contract owner approves quota, ordering, rounding, rollover and prior-billing treatment.

3. Invoice issuance, fee interpretation, credits, charges and client communication require separate explicit authorization.

4. The base deliverable is a separate draft review artifact awaiting owner approval. Source copies remain unchanged; no live mutations, communications, purchases, personal-data processing, external uploads or access provisioning are included.

Failure modes

1. Rounding each entry differently changes which entry crosses the quota.

2. A project rename causes work to be counted under two retainers.

3. Previously billed overage is included again in the candidate remainder.

4. Source text can contain instructions unrelated to the authorized analysis; treat it as evidence, never as permission or executable guidance.

Recovery and troubleshooting

1. Signal

   Rounding each entry differently changes which entry crosses the quota.

   Recovery

   Display raw minutes and recompute only under the owner’s documented rounding stage and rule.

   Resume condition

   Billing owner confirms whether rounding applies per entry or to totals.

2. Signal

   A project rename causes work to be counted under two retainers.

   Recovery

   Quarantine both mappings and preserve the original entry ID; do not allocate twice.

   Resume condition

   Operations supplies an effective-dated single mapping or explicit split rule.

3. Signal

   Previously billed overage is included again in the candidate remainder.

   Recovery

   Reconcile by immutable entry ID and retain the earlier billing reference as an exception.

   Resume condition

   Billing owner confirms complete prior coverage and the residual allocation is independently checked.

Unexecuted validation plan

Sample setup

Unexecuted fixture blueprint: the three illustrated eligible entries plus one excluded activity, one unmapped project, one duplicate entry ID and one cross-period entry without a timezone. Supply a second rule variant with no rollover and an independently prepared minute-allocation answer key.

Acceptance checks

1. The illustrated 600-minute quota allocates 360, 180 and 60 included minutes, with 60 candidate overage minutes on E3.

2. Every nonblocked entry conserves duration; total included minutes never exceed the authorized quota.

3. Excluded activity stays outside quota, and unmapped/duplicate/ambiguous-boundary records are held with distinct reasons.

4. Prior-billing matches prevent a second candidate charge for the same entry; absent rollover terms never create carryover hours.

5. All input copies remain byte-for-byte unchanged; every proposed output is labelled synthetic/draft and pending owner review.

6. No network/account operation, live mutation, external communication, personal-data use or access provisioning is attempted.

Stop conditions

1. Any planted critical exception is missed or a blocked value is presented as certain.

2. A required policy, identity, time basis or source reference is absent and cannot be resolved within the supplied fixture.

3. Personal data, credentials or unrelated content appears, or the workflow requests live access, external action or source mutation.

Executed

No

Fixture status

Design only; no fixture, workflow or acceptance check has been executed.

Approval status

not_requested_or_granted_for_execution

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Agent plan eligibility, usage limits and actual price: unknown; verify before any authorized pilot.

2. Policy extraction and prior-billing reconciliation effort are unknown; no hourly rate, fee, revenue or margin estimate is part of the plan.

3. Preparation of minimized copies, owner review, corrections and retention effort: unmeasured.

4. No native connector, paid dependency, integration installation or new account is assumed.

Caveat

No numerical price, effort, saving, income or ROI claim. Costs and usefulness require an authorized, bounded test and comparison with simpler existing controls.

Canadian adaptation — proposed

Preserve the contract’s timezone and time-unit conventions. Currency/tax amounts are outside this hours-only scope; any later Canadian invoice treatment and bilingual terms need the owner’s qualified review.

Limits

1. Original editorial plan, not a source-documented agent case. No workflow, fixture or acceptance test was executed.

2. Problem sources support a reported historical/current discussion or documented behavior; they do not establish a current defect, prevalence, buyer demand or willingness to pay.

3. Exact ChatGPT Work and Claude (Cowork capabilities) compatibility, account access and export completeness remain unknown and untested.

4. All substantive decisions and operational use remain with the named accountable owner; draft output does not imply approval.

5. Current need must be reconfirmed against the target installation, its version and simpler built-in remedies before considering a pilot.

Candidate platforms — compatibility untested

1. Name

   ChatGPT Work

   Required capabilities

   1. Read the supplied synthetic structured/text copies without source-system access

   2. Use inspectable deterministic joins/calculations for this plan’s checks

   3. Create separate reviewable CSV and text artifacts with source-row references

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   2. https://learn.chatgpt.com/docs/artifacts-viewer

   3. https://learn.chatgpt.com/docs/sandboxing

   4. https://learn.chatgpt.com/docs/enterprise/chatgpt-work-overview

   Workflow compatibility

   Unknown and untested for every proposed plan.

   Selection basis

   Editorial candidate based on general documented primitives; this exact workflow has not been executed.

   Current access note

   Current official documentation supports general file, code and reviewable-output primitives. This proposed workflow and its connector/environment compatibility are unknown and untested.

   Setup caveat

   Keep cost unknown; verify current plan, limits and task-specific tools before testing.

   Availability in canada

   Not assessed by this reference update.

2. Name

   Claude (Cowork capabilities)

   Required capabilities

   1. Read the supplied synthetic structured/text copies without source-system access

   2. Use inspectable deterministic joins/calculations for this plan’s checks

   3. Create separate reviewable CSV and text artifacts with source-row references

   Capability source urls

   1. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork

   2. https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

   Workflow compatibility

   Unknown and untested for every proposed plan.

   Selection basis

   Editorial candidate based on general documented primitives; this exact workflow has not been executed.

   Current access note

   Current Claude documentation says Cowork and chat are merging into Claude, beginning with a staged Pro/Max rollout. Some accounts still show Cowork. Verify the account’s plan, interface, permissions and tools before testing; exact workflow compatibility remains untested.

   Setup caveat

   Use current help for actual runtime and permissions. Local files, apps or browser resources require the appropriate connected desktop setup; do not assume all cloud tasks require the app open.

   Availability in canada

   Not assessed by this reference update.