How to Build a Mineral Rights Offer Correspondence Index

Direct answer

Create one neutral row for each written offer communication. Preserve the source, assign a stable ID, record only observable message fields, link attachments to document-package IDs, and connect duplicates or revisions without overwriting earlier records. Use indexed, linked to package, duplicate noted, or not available as outcomes. The index does not prove delivery, legal receipt, title, legal effect, value, fairness, deadlines, or what the owner should do.

Key takeaways

• Preserve each source message and record observable metadata instead of rewriting the communication from memory.
• Link attachments to the separate document-package index so message identity and file completeness remain distinct.
• Connect duplicates, forwards, and revisions with stable IDs while keeping every source record available.
• Keep decisions, deadlines, legal conclusions, valuation, and reply strategy outside the correspondence index.

Educational records-control boundary. This article provides a neutral organizational template for written mineral-rights offer communications. It does not establish delivery, legal receipt, authenticity, title, ownership, acreage, authority, deadlines, compliance, legal effect, enforceability, contract meaning, value, offer fairness, buyer quality, tax treatment, or whether to respond, sign, sell, or hold. Use qualified legal, title, tax, accounting, appraisal, land, and financial professionals for owner-specific conclusions. MRX may have an economic interest in a later transaction; when that applies, the buyer relationship is disclosed in writing before an agreement is signed.

A mineral rights offer correspondence index is a directory of written messages, not a negotiation log and not an offer analysis. It records which message was sent or received, when the source shows it, who appears in the message fields, which attachments traveled with it, and how it relates to another retained communication.

Its permitted outcomes are deliberately small: indexed, linked to package, duplicate noted, or not available. Those outcomes describe record-control work. They do not say that a message was legally delivered, that a deadline applies, that a buyer is trustworthy, that a document controls, or that an owner should reply.

Keep four artifacts separate

Owners often receive an email, a portal link, a cover letter, an offer, a deed, an exhibit, and later revisions in one fast-moving exchange. One spreadsheet should not be asked to perform every job.

Use four separate artifacts:

1. The correspondence index identifies written messages and links.
2. The document-package index inventories files, pages, exhibits, schedules, signatures, and replacements.
3. The property-scope crosswalk transcribes the property and interest descriptions stated in organized documents.
4. The mineral-rights sale decision log records open questions, referrals, decisions, and next actions.

This separation prevents a subject line from becoming a legal conclusion or an attachment filename from becoming evidence that a package is complete. The correspondence index begins after intake. It points to the other artifacts without absorbing their jobs.

Preserve the source before creating a row

Retain the original communication in the form you actually received or sent when practical. For email, that may include the native message and its headers. For a portal, preserve the available source record and an observed identifier. For postal mail, preserve the envelope and contents in the package workflow. For a text message, preserve the available written conversation record and its visible participants and timestamps.

Do not rewrite the message from memory. Do not paste private correspondence into a shared worksheet unless the people with access are authorized to see it. The index should point to a controlled source location rather than copying the entire message body.

The U.S. National Archives’ email and electronic messages page is guidance for federal agencies, not a private-owner rule. Its linked transfer-format tables are still a useful records-management analogy because they identify observable message parts such as date, from, to, subject, body, attachment, sent time, and filename, and they treat attachments as components of the email record. This article borrows that neutral field discipline; it does not impose NARA transfer or retention requirements on mineral owners.

Assign a stable correspondence ID

Give every retained written communication a stable ID before adding interpretation elsewhere. A simple format might be COR-2026-08-22-001. The exact pattern matters less than uniqueness and consistency.

Create one row per source communication. Record each field conservatively:

• Correspondence ID: Record a unique internal ID, but do not present it as a legal exhibit number.
• Direction: Record sent or received as observed, but do not infer who legally initiated contact.
• Sender: Record the name or address shown in the source, but do not infer identity, authority, or buyer quality.
• Recipient: Record the name or address shown in the source, but do not infer legal receipt or notice.
• Observed date and time: Record the displayed timestamp and time zone when shown, but do not calculate a contractual or statutory deadline.
• Channel: Record email, portal, mail, or text as observed, but do not characterize the legal method of delivery.
• Subject or neutral label: Record the source subject or a factual label, but do not infer urgency, fairness, finality, or validity.
• Source location: Record a controlled message path or record ID, but do not claim that every copy is preserved.
• Attachment list: Record filenames or package links as observed, but do not infer package completeness.
• Related correspondence ID: Record a reply, forward, duplicate, or revision link, but do not decide which version legally controls.
• Administrative outcome: Use indexed, linked to package, duplicate noted, or not available, but do not label the offer accepted, rejected, final, or binding.

Use not shown rather than guessing. If a message displays only a nickname, record the nickname as written and route any identity question outside the index.

Link attachments without re-inventorying them

An email with four attachments is one correspondence row plus four observed attachment references. It is not automatically a complete four-file package.

For each attachment:

• preserve the filename as received;
• record the message’s correspondence ID;
• assign or locate the attachment’s component ID in the separate package index;
• mark linked to package only when that relationship is recorded; and
• use not available when the source mentions an attachment that is not present in the retained message.

The package index owns file size, page count, exhibits, signatures, and replacement reconciliation. The correspondence index owns the fact that an observed message carried, linked to, or referred to the file.

That boundary matters when a sender says “see attached revised offer” but the retained message contains no attachment. The correspondence row can preserve the exact message identity and mark the attachment unavailable. It cannot decide what document the sender meant or reconstruct the missing file.

Connect replies, forwards, duplicates, and revisions

Do not collapse a thread into one summary row. Keep each source communication and connect the records.

A reply can point to the prior correspondence ID. A forward can point to the original message when the source makes that relationship visible. A revised message can link to the earlier row while both remain available. A duplicate can receive its own ID and the outcome duplicate noted.

Use neutral relationship labels:

• replies to;
• forwards;
• sender-stated revision of;
• encloses file also linked from;
• possible duplicate of; or
• relationship not available.

Avoid labels such as supersedes, controls, accepted, rescinded, legally received, or final version unless you are merely preserving exact source wording and clearly marking it as source wording. Whether one communication changes legal rights belongs with qualified counsel reviewing the actual documents and facts.

If two files appear byte-identical, a cryptographic hash can support a technical duplicate check. The index may record that match. It still should not delete either source message or claim the messages had identical legal significance.

Keep decisions and response timing outside the index

A message may contain a requested response date, an expiration statement, or a claim that an offer is final. Transcribe the visible wording only when needed for source identification, then route the substantive question to the decision log and an appropriate professional.

The correspondence index must not:

• calculate a response deadline;
• decide whether a stated date is enforceable;
• recommend replying, negotiating, signing, or ignoring;
• compare offer prices or terms;
• rank buyers or judge their credibility;
• determine whether a message satisfies notice requirements; or
• record an outcome such as accepted or rejected.

The broader selling-mineral-rights hub explains the larger decision process. This index is only a controlled input to that process.

Treat mailed offer packets as linked records

Texas Property Code Chapter 5, Subchapter F addresses defined mineral- or royalty-interest conveyance situations. Section 5.151 describes a specific mailed offer that includes a conveyance instrument and a payment instrument, along with a property-description disclosure.

That limited statutory example shows why message, envelope, offer, conveyance, and payment materials should remain linked as received. It does not mean every mineral-rights communication falls within that section. A correspondence index cannot determine coverage, compliance, sufficiency, delivery, enforceability, remedies, or whether an instrument is void. Those are legal questions for a qualified Texas attorney reviewing the actual facts.

Record only observable links: COR-001 mailed cover letter → PKG-004, with the envelope and enclosed components inventoried separately. Do not label the row “statutory notice satisfied.”

Work through a fictional example

Assume an owner receives an email with the subject “Updated documents.” It contains two attachments. The next morning, the same sender sends a short message saying one attachment was included by mistake and provides another file. A portal later displays a copy of the second message.

The index could contain:

• COR-001: received email; subject as shown; attachments linked to PKG-01/F01 and PKG-01/F02; outcome linked to package;
• COR-002: received email; sender-stated revision of COR-001; new attachment linked to PKG-02/F01; outcome linked to package; and
• COR-003: portal message; possible duplicate of COR-002; outcome duplicate noted.

The package index would compare the files. The property-scope crosswalk would transcribe stated tract and interest descriptions if needed. The decision log would hold any question about what changed and who should review it.

The correspondence index would not say which attachment controls, whether the revision was effective, whether the portal copy proves receipt, whether a deadline moved, or whether the new terms are better.

Run a four-outcome quality check

Before sharing the index for review, confirm that every row ends in one allowed administrative outcome:

1. Indexed: Source message identity and observable fields are recorded.
2. Linked to package: Observed attachments or enclosed files point to package/component IDs.
3. Duplicate noted: The retained source is linked to a possible or technically confirmed duplicate without deletion.
4. Not available: A source, attachment, timestamp, participant field, or relationship cannot be established from the retained record.

Then check that no row contains a legal, valuation, tax, negotiation, buyer, deadline, or sell-or-hold conclusion. Open questions should link to the decision log, not be answered in the index.

Protect access and preserve provenance

Correspondence may contain private contact information, signatures, account details, legal descriptions, tax identifiers, or access links. Keep the index itself minimal and place sensitive source records in an access-controlled location.

Do not put passwords, one-time links, bank details, taxpayer identifiers, or unredacted private data in an ordinary shared index. Record a controlled location or restricted-record ID instead. Ask qualified counsel or records professionals about preservation duties, litigation holds, privacy rules, and retention periods for the actual matter.

Add a short provenance block to the index:

• index owner;
• date created;
• last reviewed date;
• source locations included;
• source locations excluded;
• naming convention;
• time-zone convention; and
• known gaps.

That block helps another reviewer understand what the index covers without turning it into a completeness or legal-sufficiency certification.

Use the index as a handoff, not a verdict

A useful mineral rights offer correspondence index lets an owner or professional move from a message ID to the retained source, then to any attached package, related correspondence, scope crosswalk, and open question.

It should make the record trail easier to inspect while remaining modest about what it proves. If the question is “Which message carried this file?” the index can help. If the question is “Was it legally delivered, does it control, is it fair, or should I sign?” stop and route the actual records to qualified professionals.

Frequently asked questions

What is a mineral rights offer correspondence index?

It is a neutral directory of already-sent or already-received written communications related to a mineral-rights offer. Each row preserves observable message metadata and links attachments to separate package records without interpreting the offer or prescribing a response.

How should I label a message without interpreting it?

Use the subject exactly as shown when one exists. If there is no useful subject, use a neutral label such as portal message, mailed cover letter, or text message and keep the source communication ID beside it. Do not label a message urgent, final, fair, binding, or accepted unless that exact word is preserved only as source text.

How do I connect an attachment to the document package?

Give the message a correspondence ID and record the attachment filename as observed. Then link that filename to the stable package or component ID in the separate document-package index. The correspondence index shows the delivery relationship; the package index owns page and attachment completeness.

What should I do with duplicate, forwarded, or revised messages?

Keep each source message, assign its own correspondence ID, and link it to the related earlier row. Mark the administrative outcome duplicate noted when the source appears byte-identical or visibly repeated, but do not delete it or decide which version has legal effect.

What can the correspondence index prove?

It can prove only what the indexer observed and linked in the retained source records. It cannot establish delivery, legal receipt, authenticity, title, ownership, authority, deadlines, contract meaning, value, fairness, buyer quality, tax treatment, or whether the owner should respond, sign, sell, or hold.

Sources

• U.S. National Archives, Email and Electronic Messages Management (accessed 2026-08-22)
• U.S. National Archives, Appendix A: Tables of File Formats (accessed 2026-08-22)
• Texas Legislature, Property Code Chapter 5, Conveyances (accessed 2026-08-22)
• Mineral Rights Xchange, How to Build a Mineral Rights Sale Document Package Index (accessed 2026-08-22)
• Mineral Rights Xchange, How to Build a Mineral Rights Sale Decision Log (accessed 2026-08-22)
• Mineral Rights Xchange, How to Build a Property-Scope Crosswalk Before Comparing Mineral Rights Offers (accessed 2026-08-22)