Audit framework and data quality Work context: independent creator responsible for drafting and handing over three illustrated portfolio pages. Four-week goals: Complete the draft. Request one peer review. Revise after feedback, if available. Facts: Available capacity: 240 net minutes each Monday–Friday; 1,200 minutes per week. Meetings and breaks are already excluded. Messages must continue. Work remains a private draft, using existing resources. No purchases, public release, or external approval. No time log is available. Estimates: Source review: 3 × 30 = 90 minutes/week. Drafting: 5 × 60 = 300 minutes/week. Messages: 5 × 30 = 150 minutes/week. Folder organization: 1 × 30 = 30 minutes/week. File searching: 5 × 20 = 100 minutes/week. Repeated status updates: 5 × 15 = 75 minutes/week. Both suspected losses are already included in task durations. Unknowns: Actual task durations, interruption patterns, and results. Which tasks contain file searching and repeated updates. Necessary versus avoidable portions of these activities. Time required for illustration work, handover, and subsequent review. Initial hypothesis: some file searching and repeated status updates may be reducible. Neither their causes nor recoverable minutes are established. Measure five unchanged workdays first. The separate seven-calendar-day intervention period begins on the following Monday. Uniform time ledger Baseline period: five consecutive Monday–Friday workdays, with existing working methods unchanged. Use this ledger locally; duplicate rows for each continuous activity. Date | Start | End | Duration, min | Activity | Category | Planned result | Actual result | Interruption | Cause | Evidence Monday: ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ Tuesday: ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ Wednesday: ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ Thursday: ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ Friday: ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ | ___ Assign exactly one category per interval: Source review: inspecting source material. Drafting/illustration: creating or revising page content. Messages: necessary communication, including required status updates. Organization: maintaining folders or file references. Search/reorientation: locating files or recovering task context. Waiting/interruption: blocked or interrupted work; record whether necessary or potentially avoidable. Audit effort: logging, setup, controls, and final review. Other/unclassified: describe the activity before judging it. Excluded time: breaks and fixed meetings, outside the 1,200-minute net capacity. Rules: Record start and end to the nearest minute; calculate duration from them. Split an interval when an interruption becomes a separate activity. Tag repeated updates within Messages; do not add their duration again. Record parallel work once, under the activity receiving attention. Mark retrospective entries “Estimate,” with uncertainty and supporting evidence. Use local filenames or brief result descriptions as evidence; omit confidential message contents. Necessary recovery, accessibility measures, and safety checks remain protected. Budget up to five minutes per baseline workday for logging, inside capacity. Record actual logging time. Task impact inventory Task | Goal contribution | Expected result | Frequency/week | Estimated minutes/week | Urgency | Dependencies Source review | Supports draft accuracy and content selection | Usable source material | 3 | 90 | No deadline supplied | Existing sources and outline Drafting | Direct contribution to completing pages | Draft content | 5 | 300 | Four-week goal; exact deadline unspecified | Sources and outline Messages | Supports communication and possible peer review | Necessary exchanges | 5 | 150 | Individual deadlines unknown | Other participants’ responses Folder organization | Supports access to working material | Findable files | 1 | 30 | No deadline supplied | Existing file structure The draft is the primary deliverable. Messages remain necessary despite their less direct contribution. Folder organization may support faster access, but its benefit needs measurement. Illustration, handover, and revision requirements are not separately quantified. Establish whether they are included in drafting before expanding this inventory. Evidence-based time-waster ranking Rank | Candidate | Estimated weekly time | Pattern and probable cause | Impact | Data quality | Influenceable share | Change risk 1 | Hypothesis: avoidable file searching | 100 minutes | Reported searching; cause unknown. Baseline should distinguish unclear location, version ambiguity, and necessary exploration | May reduce creation time | Unmeasured estimate | Unknown; not all searching is avoidable | Wrong-file selection or index maintenance overhead 2 | Hypothesis: avoidable repeated status updates | 75 minutes | Reported repetition; cause unknown. Baseline should identify unchanged information and required recipients | May consume communication capacity | Unmeasured estimate | Unknown; required updates must remain | Missing current information or delayed communication These estimates describe candidate activity time, not verified losses. Their apparent order should change if baseline evidence shows different recoverable amounts. Stop/Reduce/Automate/Delegate decision Candidate | Primary measure | Benefit | Prerequisites | Responsible person | Privacy/quality risk | Fallback criterion File searching | Reduce | Shorter retrieval time | Baseline confirms repeated retrieval of known project files | Creator | Stale references or incorrect versions | Revert if retrieval errors occur or overhead exceeds saved time Repeated status updates | Reduce | Less repeated composition | Baseline confirms reuse of unchanged information | Creator | Outdated or confidential wording reused incorrectly | Revert if accuracy or required communication suffers No automation or delegation is proposed: neither a defined automation process nor a suitable delegate has been supplied. Up to three controlled elimination experiments Run only experiments supported by the unchanged baseline. Two are proposed conditionally. Experiment 1: local file-reference index Initial hypothesis: repeated retrieval of known files can be shortened. Essential change: use one text file containing references to baseline-confirmed, frequently retrieved project files. Measurement: compare retrieval minutes per comparable retrieval with baseline; count retrievals and errors. Setup budget: up to 15 minutes. Daily control budget: up to two minutes, plus actual index maintenance. Hypothetical gross recovery: 0 to the measured baseline minutes spent on comparable, avoidable retrievals. No narrower range is supported. Protection: retain original files and folders; verify the intended version. Termination: stop after an index-related wrong-file incident, or when maintenance outweighs observed savings. Experiment 2: reusable status draft Initial hypothesis: composing unchanged status information repeatedly can be shortened. Essential change: maintain one current local status draft and reuse relevant wording after checking it. Measurement: compare composition minutes per comparable update with baseline; count updates and corrections. Setup budget: up to ten minutes. Daily control budget: up to two minutes, plus actual draft maintenance. Hypothetical gross recovery: 0 to the measured baseline minutes spent recomposing unchanged information. Protection: preserve required messages, recipients, timing, and accuracy. Termination: stop if reuse causes a material error, missed requirement, or greater maintenance effort than savings. Order: establish the file index first, then the status draft. File searching has the larger reported estimate; both changes are reversible. Maintain separate activity tags so their savings cannot overlap. Capacity calculation All figures are minutes per week. Available net capacity: 240 × 5 = 1,200. Estimated recurring task time: 90 + 300 + 150 + 30 = 570. Unclassified capacity before audit effort: 1,200 − 570 = 630. The 630 minutes are not automatically waste. They may cover omitted project work and interruption buffers. Candidate activity time: 100 + 75 = 175, already within the 570. Do not calculate 570 + 175. Messages account for 150 estimated minutes within task time. Their necessary portion remains protected. Meetings and breaks require no further subtraction. Baseline logging budget: 5 × 5 = 25. Remaining unclassified baseline capacity: 1,200 − 570 − 25 = 605. Intervention overhead budget, if both experiments proceed: Setup: 15 + 10 = 25. Logging: 5 × 5 = 25. Controls: 5 × 4 = 20. Final review: 15, on the next Monday outside the intervention window. Total: 85, plus actual maintenance beyond these budgets. Let S be verified eligible search minutes and U verified eligible repeated-composition minutes from comparable baseline work. Hypothetical gross recovery is 0 to S + U. Using the current estimates only as provisional ceilings: 0 to 175 gross; after the 85-minute overhead budget, −85 to +90 net, before additional maintenance. Including the separate 25-minute baseline logging cost gives a full-audit provisional range of −110 to +65 minutes. These are hypotheses, not forecasts. Replace estimates and budgets with actual measurements. Seven-day measurement log This intervention period starts only after five unchanged baseline workdays. Day | Measurement | Concrete experiment action | Protection control | Brief result note 1, Monday | Log eligible activity and all setup time | Create and use baseline-supported index/status draft | Verify files and message accuracy | Record setup, counts, deviations 2, Tuesday | Record comparable retrieval/update durations | Use the supported changes | Check versions and required messages | Record errors and maintenance 3, Wednesday | Continue the same measurements | Continue unchanged experiments | Apply termination criteria | Note workload differences 4, Thursday | Continue the same measurements | Continue unchanged experiments | Check accuracy and overhead | Note special events or overtime 5, Friday | Complete workday measurements | Continue or revert if criteria trigger | Preserve required duties | Record outcomes without final review 6, Saturday | None | No work or experiment action | Nonworking day | No entry required 7, Sunday | None | No work or experiment action | Nonworking day | No entry required Keep other working methods as constant as practical. Record deviations during working-day logging; record overtime separately from ordinary capacity. Final review: next Monday, outside the intervention window. Reserve up to 15 minutes within that day’s 240-minute capacity. Final decision No outcome can be determined before measurement. At the next-Monday review, assess each experiment separately: Maintain: comparable work shows positive net savings without quality or duty failures. Adjust: benefit exists, but maintenance or errors indicate a specific correction. Revert: net time gain is nonpositive or protection rules fail. Measure longer: too few comparable events or substantial workload differences prevent a conclusion. Calculate gross gain using baseline time per comparable event and intervention event counts. Deduct actual setup, logging, control, maintenance, and allocated final-review time. Allocate shared overhead once across experiments. Report full-audit gain separately after also deducting baseline logging. Exactly the next cause to check: version ambiguity during file retrieval. Treat it as a hypothesis and test it using recorded search reasons; do not assume it caused the reported searching.