Digital Records

Digital records work becomes urgent when an organization cannot tell whether a file is current, who may open it, or when it should be retained. The service organizes a defined collection and makes those decisions visible without acting as the organization's legal retention authority. A good result reduces search and access risk while preserving evidence and ownership.

This guide applies the general Starter Library method to digital records. Use G01 for opportunity selection, G03 for AI verification, G04 for demand evidence, G05 for setup, G06 and G07 for customer contact and selling, G08 for pricing, G09 for service recovery, G10 for cash discipline, G12 for workflows, and G13 for contracts and privacy. Those guides carry the shared method; the sections below cover the operating decisions that change when this specific service is delivered.

Opportunity and Customer

The buyer group is Small organizations with a defined collection of files, an approved retention policy, named owners, and a need to find and protect records more reliably.

The recurring problem is File names are inconsistent, duplicates and obsolete versions are mixed with current records, permissions are unclear, and retention dates are absent.

The paid result is An organized records collection with a naming scheme, ownership index, access review, backup check, retention labels, and safe deletion recommendations. Progress must remain inspectable, and consequential changes require the buyer's named approver.

The operating boundary is You organize and document records within approved policy. You do not decide legal retention requirements or destroy records without explicit authorization.

Demand evidence

Ask the owner to find one current contract, one superseded version, and one document with an unknown owner in the live system. Strong evidence includes slow retrieval, duplicate folders after staff turnover, uncertain access, or a backup that has never been tested. Confirm that an approved retention policy or named policy owner exists before proposing change. A statement that the drive is messy is only a symptom; the paid inventory should have a folder boundary, file-count estimate, authority, and a non-destructive exception route. Ask who can approve access changes and deletions, and record whether a legal hold or regulated record category is present.

Fit and Skills

The fit assessment is Fits someone methodical who can distinguish content categories, preserve evidence, document each move, and stop before deleting uncertain records.

The minimum skill set is Practice naming conventions, metadata, duplicate detection, version history, permissions, retention labels, backup verification, and audit logs.

Use G04 to test buyer demand for digital records after building this guide's artifact; capability alone is not proof.

Capability artifact

Create a fictional three-folder contract collection with current agreements, superseded versions, duplicate scans, unknown owners, and one retention label. Build an inventory, naming rule, duplicate report, access matrix, restore-test note, and deletion decision list. Leave all deletion statuses unapproved until a named owner signs them.

Startup Budget

These digital records USD ranges are planning inputs; confirm each cost with current local quotes and keep first-test loss affordable.

• Secure cloud storage under the client's account: client-dependent.
• Spreadsheet or indexing tool: 0 USD.
• File comparison or hashing tools: 0 to 30 USD monthly.
• Training on records privacy and retention: 50 to 200 USD.
• Professional records or legal review: 100 to 500 USD.
• Contingency for duplicate review and restore testing: 50 to 250 USD.

Skill Acquisition

Operating sequence

Confirm the folder set, owners, approved retention policy, legal holds, authoritative versions, access roles, backup status, and deletion authority. Inventory the files, normalize names and folder structure in a mapping table, identify exact and near duplicates, record versions and owners, review permissions, and test a restore. Return proposed deletions as decisions rather than performing them automatically.

Acceptance test

Sample the renamed inventory and confirm that metadata, owner, version, and current-status labels match the content. Check that an obsolete file has not displaced the authoritative one and that every deletion or move has a destination and approval. Preserve audit evidence and stop on an unclear legal hold, sensitive record, unknown owner, or failed restore.

Setup

Confirm legal hold, retention policy, owners, access roles, backup status, authoritative versions, deletion approval, and the location of personal or sensitive data.

Launch controls

Work from a permissioned account and preserve a recoverable copy before a batch move. Confirm legal hold, retention, access owners, and deletion approver. Do not copy sensitive files into unapproved AI tools or use public sharing links. Make date, version, and owner changes in a controlled batch with a rollback record.

Use G05 and G13 for jurisdiction-specific setup, privacy, and legal questions.

Concrete Offer

A records cleanup for one approved folder set up to an agreed file count. Includes naming map, inventory, duplicate report, permission review, retention labels, restore test, and an owner-approved action list.

First acceptance evidence

The first handoff includes an inventory, naming map, duplicate report, access review, restore evidence, retention labels, and approved action list. Counts should distinguish moved, labeled, pending decision, and unresolved records. The organization can inspect every consequential change and know what still requires legal or owner review. The report also records the source collection date, the tested restore version, and the person who owns access removal.

Use G07, G08, and G13 to write the scope, payment, approval, and stop condition.

Outreach

Ask how a recent document was located and who confirms the current version. Do not request sensitive files before a written scope.

Target small firms facing staff turnover, inconsistent shared drives, audit preparation, or repeated difficulty finding approved records.

Acquisition test

Approach twelve small firms facing staff turnover, audit preparation, or repeated difficulty locating an approved document. Ask how a recent document was found and who confirms the current version. Offer a paid inventory of one folder set. Do not request sensitive files before the scope, authority, access, and retention controls are agreed.

Use G06 for the lawful contact method and record each reply and next action.

Pricing and Unit Economics

An illustrative cleanup is 500 to 2,000 USD depending on volume and risk. A quarterly index and access review may be 200 to 700 USD. Legal records advice remains separate.

Count inventory, duplicate analysis, naming, permissions, backup testing, deletion review, and handoff. File count is only one input; sensitive and unstructured records take more time.

Illustrative floor calculation

For a 1,000-file folder set, plan 4 units for policy and ownership mapping, 12 for inventory and deduplication, 5 for access review, 3 for restore testing, 3 for labels and handoff, and 3 for uncertainty review. At 40 USD per direct unit, planned labor is 1,200 USD before storage tools and sales. A 900 USD cleanup needs a smaller file set, clean metadata, and an existing retention policy.

Use G08 and G10 to set a local floor; contribution is not owner pay.

Delivery Example

The example below is an illustrative composite, not a real customer record or income promise.

A small association has three supplier-contract folders and no clear owners. You inventory current and obsolete versions, create a naming guide, flag duplicates for approval, review access, test restore, and leave deletion as a signed decision. The illustrative fee is 900 USD.

Delivery trace

In the association example, current and superseded supplier contracts are separated, two duplicates are flagged, one unknown owner remains open, and a restore test proves that the approved record can be recovered. Deletion is not performed. The owner signs each proposed action and receives a mapping log for future staff.

Growth

Offer recurring index, access, and backup checks. Add new-record intake rules. Never treat storage as a retention policy or perform bulk deletions without authorization.

Scale boundary

Add a folder set only after naming, ownership, access, and restore checks work for the first. A recurring review can include index freshness, permission drift, and backup evidence, but legal retention decisions remain with the authorized owner. Never turn storage cleanup into bulk deletion without explicit approval.

Use G14 before expanding digital records capacity, a customer segment, or a service line; protect delivery quality first.

Risks

• Deleting the only copy or a record under a hold.
• Changing permissions and blocking operational access.
• Exposing names or personal information in an index.
• Assuming backup exists without restoring a test file.

The controls above are the early-warning route. Jurisdiction-specific professional review still applies.

Privacy and AI Verification

Inventory metadata rather than unnecessary content, restrict access, and verify retention instructions with the client's qualified adviser. AI can suggest categories from approved filenames, but a human must inspect exceptions and protect sensitive records.

Apply the authorization, minimization, verification, and deletion process in G03, G12, and G13.

30-Day Action Plan

• Days 1-4: choose one file collection and define inventory fields and prohibited data.
• Days 5-9: build a fictional folder tree with duplicates, obsolete versions, and access roles.
• Days 10-13: create naming, inventory, duplicate, restore, and deletion-approval templates.
• Days 14-20: contact twelve organizations with a specific records-finding problem.
• Days 21-26: deliver one approved cleanup or audit and verify one restore.
• Days 27-30: review retrieval, access, uncertainty, and contribution. Avoid high-risk deletion work.

At day 30, continue, revise one variable, or stop.

Day-30 decision record

At day 30, record paid digital records tests, costs, delivery time, rework, exceptions, one objection, and one approval delay.

Templates

Template 1

Inventory row: Current name, category, owner, version status, created date, retention label, sensitivity, duplicate reference, and action.

Template 2

Access review: Person, role, folder scope, permission level, approval, last review, removal date, and multi-factor status.

Template 3

Deletion decision: Record set, authority, retention rule, legal hold check, client approval, backup tested, delete date, evidence retained, and operator.

Adapt contract language through G13 and local professional review.

Related General Guides

• G01, Finding a Business Opportunity That Fits
• G03, AI Assistant Basics
• G05, Business Setup
• G09, Customer Service
• G12, One-Person AI Workflows
• G13, Contracts and Privacy
• G14, Sustainable Growth

Read the linked general guides for shared definitions, customer acquisition, pricing method, service recovery, cash discipline, workflow design, and legal and privacy controls. This specialized guide intentionally stays focused on digital records operations.

Key Takeaways

• The first handoff includes an inventory, naming map, duplicate report, access review, restore evidence, retention labels, and approved action list.
• Sample the renamed inventory and confirm that metadata, owner, version, and current-status labels match the content.
• For a 1,000-file folder set, plan 4 units for policy and ownership mapping, 12 for inventory and deduplication, 5 for access review, 3 for restore testing, 3 for labels and handoff, and 3 for uncertainty review.
• Approach twelve small firms facing staff turnover, audit preparation, or repeated difficulty locating an approved document.
• Add a folder set only after naming, ownership, access, and restore checks work for the first.
• Keep the service boundary, named approver, and stop condition in every offer.
• At day 30, decide from paid delivery evidence and actual contribution.