increment-rounding register · bound register page

Expose the Minutes Added by Per-Entry Billing Increments

A short task rounded separately several times can add more billed minutes than the same work grouped once. Enter recorded durations, occurrence counts and the increment from your terms to see raw minutes, rounded minutes and the difference.

1 · entry type | recorded minutes per occurrence | occurrences

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The increment-rounding register processes entry type | recorded minutes per occurrence | occurrences locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: rounded invoice minutes obscured recorded time. After: every occurrence’s raw, rounded and added minutes are shown without deciding what the contract authorizes.

2 · Read the increment-rounding register

Billing-duration arithmetic only, not legal, accounting, tax or wage-entitlement advice. It models per-occurrence upward rounding and no separate minimum charge; it does not verify a contract or declare an overcharge. Check the signed terms and factual time records with the provider or a qualified accountant before disputing or issuing an invoice.

Paid layer: increment-rounding register filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked increment-rounding register run in the app
three labeled samples and unlimited article-demo calculations
complete result text and a user-triggered input-state link

What $4 one-time adds

unlimited subsequent increment-rounding register app calculations after a local convenience signal
print the increment-rounding register with visible assumptions and its safety boundary
CSV of the displayed additional billed minutes and row workings; conditional estimate uses your manual-retyping minutes
five local reading summaries (headline/count/time), not saved full inputs or cross-device backups

HYPOTHESIS / PROTOTYPE: $4 is a proposed one-time price for filing the increment-rounding register, not a current sales offer. No measured time saving or buyer demand is claimed. The optional manual-retyping baseline above estimates one export’s retyping budget only; it does not change the calculation or guarantee savings.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the increment-rounding register

Read the time-entry clause before choosing the increment. “Nearest quarter-hour,” “each commenced quarter-hour” and “round once at the daily total” are different rules. This register models only the second shape: round every entered occurrence upward to a whole increment, then multiply by its count. If your terms use another convention, the result is not a substitute for that convention. Use generic descriptions such as proof check rather than client names or confidential case references. Keeping the raw time next to the uplift helps a provider explain a bill and helps a customer ask a precise question. Neither party needs to accuse the other of an error merely because rounding changed a total; the first question is whether the agreed method matches the calculation.

Boundary and sources

Method: Rounded minutes per occurrence equal ceiling of recorded minutes divided by the increment, multiplied by the increment. Uplift is rounded minus recorded, multiplied by occurrences. Row notes retain both totals so grouping effects can be checked.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-09-30, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this increment-rounding register for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a increment-rounding register. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are entry type | recorded minutes per occurrence | occurrences; the setting is Billing increment in whole minutes. Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.