Companies lose rights in their technical data far more often through sloppy marking than through anything they negotiated. The rule is unforgiving in both directions: data you deliver without the required legend is generally treated as delivered with broader rights than you intended, and data you mark with a legend you invented can be challenged and the marking removed. Getting this right costs an afternoon of attention per deliverable.

Unmarked data is usually lost data

If a deliverable arrives at the agency with no restrictive legend, the default assumption runs against you. There is no implied protection, no benefit of the doubt, and no practical way to argue afterward that everyone understood the drawings were proprietary. Marking is the mechanism by which a restriction exists at all. That means the marking step cannot be the last thing an intern does to a PDF at midnight before the deadline — it has to be planned when the deliverable is planned, alongside the rest of your reporting and deliverable schedule.

Use the legend the clause gives you

The applicable data rights clause prescribes the exact legend text, including the fields you fill in — contract number, contractor name and address, and where relevant the expiration of the restriction. Copy it verbatim. "Company Confidential," "Proprietary — Do Not Distribute," and a marking you drafted yourself are nonconforming markings; the government can require you to correct them and, if you do not, strip them. The opposite failure is just as real. Marking everything restricted, including data the government paid to develop or data that has to be delivered with unlimited rights, is an overbroad assertion, and there is a formal challenge process for exactly that. An overreaching legend invites a validation challenge that can end with less protection than a careful, narrow assertion would have given you.

Mark narrowly, and mark consistently

Two habits do most of the work. Mark at the lowest segregable level — the specific pages, drawing sheets, software modules or paragraphs the restriction actually covers — rather than stamping a whole report and hoping. And keep the marking identical across every form the same information takes, because a single unmarked copy undermines the marked ones. In practice that means checking:

  • Written reports, appendices and the figures inside them
  • Drawings, CAD files and exported models, sheet by sheet
  • Software source files, headers, build artifacts and media labels
  • Hardware deliverables and the labels or nameplates on them
  • Slides used at program reviews, which are frequently forgotten

Behind the markings you need a record of who funded the development of each element, because the funding source is what determines which category the data falls into and what you can defend if challenged. Keeping that record from day one is much easier than reconstructing it, and it belongs in your IP protection strategy next to your patent and trade secret practice. It also connects directly to who owns what on a federal award.

This is general information, not legal advice. Marking requirements come from the specific clause in your award, and getting them right is a question for counsel experienced in federal contracting.

Projects House prepares engineering deliverables for companies working under federal awards. Reach us through the contact form.