Choose one collection you can explain
Begin with a repeated task or a defined body of work. “Completed maintenance histories in our current service system” is a clearer scope than “everything on the shared drive.” You can add another collection later. Keeping the first scope narrow makes gaps, responsibilities, and permissions easier to identify.
Ask the person who uses the system how a record becomes complete. Does closing a ticket mean the work ended, the customer accepted it, or an administrator cleared the queue? Write that definition in the inventory. A reviewer needs the meaning of the count as well as the count itself.
Use these fields in your own worksheet
| Field | What to write | Example description |
|---|---|---|
| Collection and process | The work represented, including where the history begins and ends. | Equipment-service jobs from initial report through recorded closeout. |
| System and format | Where the records live and what an authorized export could preserve. | Service platform with linked notes; older attachments in a separate archive. |
| Usable period | Dates with connected, understandable coverage; list gaps separately. | Recent years have diagnosis and follow-up; earlier years have invoice summaries. |
| Scale and counting rule | Approximate number plus the unit and known duplication. | Completed job histories, excluding duplicate exports and cancelled bookings. |
| Context and links | Identifiers, attachments, revisions, and definitions that explain the work. | Job reference links each visit and its parts record. |
| Rights and approvals | Creator, governing agreements, open questions, and responsible reviewer. | Company-created notes; customer contracts and supplier manuals need review. |
| Exclusions | Categories that must stay outside the proposed scope. | Payment information, access credentials, and individual personnel files. |
An illustrative inventory entry
A hypothetical service company might write: “The current system contains completed commercial-equipment jobs with technician notes and linked return visits. The earlier system retains invoice summaries but lacks detailed diagnosis. Staff wrote the service notes; customer-site photographs and manufacturer documents need separate review. Operations can explain the exports, and an authorized director must approve any proposed introduction.”
This description supplies a process, a boundary, a gap, and named responsibilities. It does not claim that the records are ready to license. It also avoids copying an actual customer record into a document that may later circulate beyond the service team. Illustrative histories on this website serve the same purpose; they are not completed North Fox Digital transactions.
Check the inventory with two people
The operational owner can explain how the work is recorded and where context is missing. The person responsible for approval can identify agreements and other reviewers. Those may be different people. An IT administrator’s ability to export records does not replace organizational authority or permission from another rights holder.
Keep uncertainty visible. Write “count not checked,” “attachment coverage unknown,” or “contract review required” where that is the current position. Guessing can make an estimate look more specific while making the eventual review less reliable. The estimator includes explicit unknown answers for employee count and usable history.
- Confirm the counting unit and remove known duplicate exports from your estimate of scope.
- Note software changes, missing periods, and unlinked attachments.
- Identify sensitive or restricted categories for exclusion before any sample discussion.
- Record who will review rights, approvals, and the proposed buyer’s terms.
- Prepare a short nonsensitive summary for Neil; retain the detailed worksheet internally.
Turn the inventory into a first conversation
You can use the scope to answer the estimator and describe the result in context. It remains a source-based planning figure with stated reference rules, not an appraisal of the worksheet. An incomplete or specialist archive receives the reference treatment explained in the methodology.
When you are ready, request a conversation. The website accepts organizational descriptions only. Any later request for a sample, preparation work, or delivery should follow an agreed scope and protections. A contact request alone does not authorize an introduction or grant access to the archive.