How to write a primary-source decision memo without hiding the unknowns

Frame the decision before gathering material

Write the decision as a sentence with an accountable owner, deadline, alternatives, and intended operational consequence. Define the criteria the owner will apply, how each criterion will be observed, and which questions are outside scope. A platform selection might cover functional fit, implementation effort, access controls, portability, support, and total committed cost while excluding unrelated organizational policy or legal determinations.

Set an evidence threshold for each material claim. A vendor feature may require current official documentation and a working demonstration; a contractual term requires the actual proposed agreement; an internal constraint requires a named owner or approved record. Mark assertions that cannot meet the threshold as unknown rather than converting repetition, confidence, or a secondary summary into proof.

Build the sourcebook before the narrative

Create one row per atomic claim. Record the source, publisher, title, date, retrieval date, exact passage, nearby context, applicable alternative and criterion, evidence status, and any contradictory source. Prefer current official documentation, standards, public agency material, product terms, and buyer-authorized primary records. Secondary material can identify leads, but the final claim should point to the underlying source whenever it is available.

Search deliberately for disconfirming material: deprecation notices, exception clauses, unsupported configurations, migration limits, additional charges, contradictory versioned documentation, and user roles that behave differently from the demonstration. Preserve the contradiction even when one source appears more authoritative. The memo should explain why a source controls, which context limits it, and what observation would change the conclusion.

Separate evidence, interpretation, and owner judgment

Structure the memo so the reader can distinguish verified facts, reasoned interpretations, unresolved unknowns, and the accountable owner's criteria. Compare alternatives on the same definitions and dates. State where a conclusion depends on an assumption, and show the sensitivity: if the implementation estimate doubles or a required control is unavailable, which direction changes and which does not? Link every material sentence back to the ledger row.

Decision Sourcebook, operated by Reality Contact, LLC, prepares the record and explains its limits. The accountable product, technology, operations, or procurement buyer decides whether the evidence is sufficient, requests corrections, and accepts, modifies, or rejects the direction. The service does not substitute for legal, security, compliance, contracting, or budget authority and does not claim that every relevant source was obtainable.

Where the service stops

Reality Contact, LLC performs bounded research and documents evidence but does not make the product, technology, operations, procurement, legal, compliance, employment, or budget decision; negotiate or select a vendor; certify a product; or guarantee that public and supplied sources are complete. The accountable buyer reviews the criteria, evidence, contradictions, unknowns, and source limitations; requests repairs where needed; and accepts, modifies, or rejects the product, technology, operations, or procurement direction. Do not send private material through the public form. Secure intake and written deletion terms are established before contracts, internal analyses, files, links, credentials, or sensitive records are transferred. This is research and documentation; it does not replace the buyer's legal, security, compliance, procurement, contracting, or budget review. Findings are limited by the confirmed question, deadline, available public and supplied sources, source dates, authorized contacts, and stated exclusions; later evidence may change the accountable buyer's judgment.