What does the retention schedule builder produce?
Assemble a retention schedule from selected requirements, business purposes and approved periods.
Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.
What do you need before you start?
- Define your exact task, source population and method.
- Keep the unchanged original files and the selected source versions.
- Review missing, invalid and unresolved facts before preparation.
What information do you enter?
Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.
- Reference. Stable internal reference for this exact privacy workpaper.
- Working pack version. Customer document version.
- Organization. Actual organization owning the selected cases.
- Your jurisdiction. Jurisdiction and entity scope approved for this pack. Each case retains its own operative jurisdiction.
- Responsible reviewer. Customer-authorized reviewer for the selected decision method.
- Review timestamp. Exact timestamp with seconds and confirmed UTC offset.
- Approved privacy scope. Entities, activities, data, rules, populations, exclusions and uncertainty.
- Scope approval reference. Customer approval for the included cases.
- Approved preparation method. Your exact method version.
- Method source reference. Actual local file containing the approved method.
- Approved method source locator. Exact source location supporting the selected method.
- Method approver. Customer-authorized approver.
- Method approval timestamp. Exact approved instant no later than review.
- Privacy population. Selected cases or a declared complete supplied population.
- Declared case count. Required for your declared complete case population.
- Source-backed retention schedule draft case inputs. Readable typed rows with exact case IDs, operative rules, original sources and approvals.
- Record Classes. Readable typed rows with exact case IDs, operative rules, original sources and approvals.
- Retention Rules. Readable typed rows with exact case IDs, operative rules, original sources and approvals.
- Holds. Readable typed rows with exact case IDs, operative rules, original sources and approvals.
- Decisions. Readable typed rows with exact case IDs, operative rules, original sources and approvals.
- Evidence. Readable typed rows with exact case IDs, operative rules, original sources and approvals.
- Actions. Readable typed rows with exact case IDs, operative rules, original sources and approvals.
| Field | What to enter |
|---|---|
| ReferenceRequired | Stable internal reference for this exact privacy workpaper. |
| Working pack versionRequired | Customer document version. |
| OrganizationRequired | Actual organization owning the selected cases. |
| Your jurisdictionRequired | Jurisdiction and entity scope approved for this pack. Each case retains its own operative jurisdiction. |
| Responsible reviewerRequired | Customer-authorized reviewer for the selected decision method. |
| Review timestampRequired | Exact timestamp with seconds and confirmed UTC offset. |
| Approved privacy scopeRequired | Entities, activities, data, rules, populations, exclusions and uncertainty. |
| Scope approval referenceRequired | Customer approval for the included cases. |
| Approved preparation methodRequired | Your exact method version. |
| Method source referenceRequired | Actual local file containing the approved method. |
| Approved method source locatorRequired | Exact source location supporting the selected method. |
| Method approverRequired | Customer-authorized approver. |
| Method approval timestampRequired | Exact approved instant no later than review. |
| Privacy populationRequired | Selected cases or a declared complete supplied population.Choose from Selected records only, Declared complete population. |
| Declared case countOptional | Required for your declared complete case population. |
| Source-backed retention schedule draft case inputsRequired | Readable typed rows with exact case IDs, operative rules, original sources and approvals. |
| Record ClassesRequired | Readable typed rows with exact case IDs, operative rules, original sources and approvals. |
| Retention RulesRequired | Readable typed rows with exact case IDs, operative rules, original sources and approvals. |
| HoldsRequired | Readable typed rows with exact case IDs, operative rules, original sources and approvals. |
| DecisionsRequired | Readable typed rows with exact case IDs, operative rules, original sources and approvals. |
| EvidenceRequired | Readable typed rows with exact case IDs, operative rules, original sources and approvals. |
| ActionsRequired | Readable typed rows with exact case IDs, operative rules, original sources and approvals. |
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.
How does the retention schedule builder work?
- 1Define the approved scope
Reference. Stable internal reference for this exact privacy workpaper.
- 2Enter task-specific evidence
Group exact record classes, systems and data categories with source-selected triggers, minimum/maximum/fixed periods and approved business justifications. Compare incompatible periods and hold scope. Mixed calendar units require actual trigger dates before compatibility is confirmed. Retain each operative provision and approval without inventing mandatory retention periods.
- 3Inspect complete findings
Review all named calculations, original source bindings and unresolved findings.
- 4Keep recoverable work
Exact source bytes and draft strings save locally. Strict restore checks tool identity, typed structure, file hashes and history before replacing current work. Prior checkpoints and generic drafts remain downloadable.
- 5Prepare the finalized pack
Prepare 7 plus selected attachments complete files, then download them free. Review the fictional sample below.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
Common questions
What information does the retention schedule builder need?
Enter reference. Stable internal reference for this exact privacy workpaper; working pack version. Customer document version; organization. Actual organization owning the selected cases; your jurisdiction. Jurisdiction and entity scope approved for this pack. Each case retains its own operative jurisdiction; responsible reviewer. Customer-authorized reviewer for the selected decision method. Define your exact task, source population and method.
What does the retention schedule builder produce?
Source-backed retention schedule draft. Complete task-specific source and rule comparisons. Seven core files plus selected exact attachments. Formal PDF/DOCX, complete Excel, findings CSV, source/result JSON, hashes and instructions. Complete named decisions, text offsets, exact retention dates, contract scope, source-backed draft sections and unresolved findings. Exact original bytes, unfinished drafts, retained history, strict browser recovery and preserved earlier work. Review unresolved findings and limitations before use.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the retention schedule builder for this task?
Assemble selected requirements and business justifications for approval. This customer-prepared control pack retains exact source facts, operative rules, instrument text, responsible decisions and actual execution evidence. It does not determine legal applicability, approve a transfer, authenticate consent, execute deletion, sanitize media or make a filing. Imported non-US instruments require explicit customer approval. Exact originals stay browser-local. Original files are not saved to the cloud.
What still needs review?
This customer-prepared control pack retains exact source facts, operative rules, instrument text, responsible decisions and actual execution evidence. It does not determine legal applicability, approve a transfer, authenticate consent, execute deletion, sanitize media or make a filing. Imported non-US instruments require explicit customer approval. Exact originals stay browser-local. Original files are not saved to the cloud.
At most 500 rows and 200000 characters per table, 20 files, 10 MB each and 25 MB total. Input metadata is bounded to 900 KB. Complete result metadata is bounded to 8 MB. Exact JSON source comparisons support originals up to 1 MB.
Formal tables use bounded previews. Complete approved draft text and protected imported wording appear in the reports and remain exact in Excel/JSON. Text passages and protected instruments support UTF-8 .txt originals up to 128 KB.