Self-initiated demonstration 03

Recurring work, with every rule accounted for.

A coded browser sample that turns six fictional source records into a dated task register and report preview. The recurrence rules, held rows, checks, approval boundary, and planned handoff are all open for inspection.

The demonstration brief

Make the next run obvious without rewriting the past.

Daily, weekly, and month-end work needs one source table, explicit recurrence rules, a dated output, and an exception path. A report is trustworthy only when its counts reconcile to those records.

  • One preserved input snapshot
  • Three recurrence patterns
  • One checked task register
  • One exception and approval path

Coded browser sample / fixed fictional records

Trace one rule run from source to review.

Reporting window: 24 to 31 August 2026

Source6 records
Scheduled12 occurrences
Emitted11 checked rows
Held1 owner gap

Showing checked schedule.

Checked output

Recurring work becomes dated, traceable rows.

Every output row keeps its source ID, owner, recurrence rule, due time, and recorded status.

Checked schedule output generated by the browser demonstration
InstanceTaskOwnerDueStatus
OC-014/2026-08-24Review payment exceptionsEvery weekdayAlex M.Completed
OC-014/2026-08-25Review payment exceptionsEvery weekdayAlex M.Completed
OC-014/2026-08-26Review payment exceptionsEvery weekdayAlex M.Completed
OC-014/2026-08-27Review payment exceptionsEvery weekdayAlex M.Completed
OC-014/2026-08-28Review payment exceptionsEvery weekdayAlex M.Blocked
OC-014/2026-08-31Review payment exceptionsEvery weekdayAlex M.Open
OC-021/2026-08-25Send active project reviewEvery TuesdayMara P.Completed
OC-026/2026-08-28Approve contractor hoursEvery FridayElias R.Completed
OC-031/2026-08-31Close supplier statementLast business dayRina K.Open
OC-034/2026-08-25Refresh sales importTuesday and ThursdayUma S.Completed
OC-034/2026-08-27Refresh sales importTuesday and ThursdayUma S.Completed

Exception log

Bad inputs do not disappear.

One source record is held before scheduling. A blocked task remains visible for operator review.

Exceptions generated by the sample rule run
DateSourceLevelIssueHandling
Aug 26OC-039HoldOwner is missing, so the scheduled row was not emitted.Assign an owner, approve the source edit, then run the rule again.
Aug 28OC-014ReviewThe task remains in the schedule but its status is blocked.Keep the row visible and name the blocker before the next run.

Check record

The totals close before handoff.

  • Source trace

    Every emitted row retains its source ID.

  • Owner gate

    Unowned records stay out of the checked schedule.

  • Row balance

    Emitted rows and held occurrences reconcile to the rule run.

  • Status total

    Report status counts reconcile to the checked rows.

The calculations above run in this page against six fixed fictional source records. No upload, external system, Excel formula, macro, scheduled job, or PDF file is involved.

Rule book

The transformation is written down before the full file changes.

01

Preserve the source

The original row and source ID stay intact. Any correction belongs in a recorded working copy, not a silent overwrite.

02

Expand recurrence

Weekday, named-day, and last-business-day rules create dated task instances inside the approved report window.

03

Hold incomplete rows

A scheduled record without an owner does not enter the checked task table. It moves to the exception log for a decision.

04

Keep problems visible

Blocked work stays in the report with its source ID. The operator sees the obstruction instead of receiving a false completion.

05

Reconcile the output

Scheduled occurrences must equal emitted rows plus held rows. Status totals must equal the checked task register.

Approval and handoff

The buyer approves the rules before the workbook carries them.

A paid build would start with a small sample. Production formulas, recurrence logic, report sections, source corrections, and any export action wait for approval in the buyer's working copy.

Buyer supplies

The source workbook, required task fields, recurrence definitions, owner list, report sections, output format, and approver.

Approval point

The buyer signs off on a small source sample, rule table, exception handling, and report layout before the full workbook changes.

Katsa may change

Only the approved working copy, formulas, rules, validations, and report layout. Source values and completion overrides need a written decision.

Paid handoff would return

The preserved source, working workbook, rule and exception tabs, tested report layout, check record, and short operating guide.

Not present here

A client file, Excel workbook, macro, scheduled automation, one-click PDF export, live business data, time saving claim, or measured result.

Claim boundary

This page runs a browser sample. It is not an Excel workbook, macro, live automation, or downloadable PDF.

Scope an operations workbook