The Window: Build the Employment AI Record While You Can Use It

Begin with the systems already in use

The useful question for an employer is concrete: which decisions does AI influence today, and who can explain how those decisions are made? Answering it does not require agreement about when more capable AI will arrive. It requires an inventory of the actual workflow.

A forecast can inform planning without becoming a compliance calendar. A laboratory’s internal target is not a statutory deadline, and an announced capability is not evidence that the employer’s deployed product has that capability. This revision removes that conflation from the earlier essay.

Features can change the question

An organization may start with a drafting assistant and later use a ranking or recommendation feature in the same product. The familiar supplier name can obscure a different decision process. A useful record identifies the active feature, the people affected and how its output is used.

Ask who notices a material change, who assesses it and who decides whether the existing procedure remains appropriate. Record the answer while the people and evidence are available. That record can make the next review easier; it is not a promise that every uncertainty has been resolved.

A changing source record needs disciplined maintenance

Illinois HB 3773 is in force, while IDHR’s proposed procedural provisions were formally withdrawn in the June 26, 2026 Register. Colorado’s SB 26-189 replaced its earlier framework and includes duties beyond notices. These developments illustrate why a current obligation map should identify the source and its exact status. September primary-source notes.

Do not respond to a changed deadline by assuming the entire governance problem has disappeared. Equally, do not preserve a withdrawn proposal as a mandatory rule merely because a template was built around it. Keep the operational facts and the applicable requirements distinct, then update the connection.

The record should help someone do the work

A colleague should be able to open the file and identify the tool, the decision, the owner, the evidence and the unresolved question. If those facts are hard to find, adding another long narrative may not help.

Use a small set of connected working documents: an inventory, supplier questions, a response tracker, a communication map and an action record. Include a worked example so a new owner can see how the pieces fit together. Keep examples fictional unless the organization has permission and an appropriate basis to use a real case.

The point is not to create paperwork for an imagined courtroom. The point is to give the people making decisions an accurate account of what they are doing and what they still need to understand.

Choose a first decision

Select one consequential employment workflow. Ask the responsible team to describe the active feature and retrieve the available supplier evidence. Identify the most important open question and assign an owner for answering it. Record the decision that follows.

That is a useful place to begin even when the regulatory landscape remains unsettled. It advances a real task, produces a reusable record and makes the next question easier to assess.

The TalentSight library provides current employment documentation and implementation guidance. The BoardSight library supports the board reporting side of the work. Their current contents and formats are listed before purchase.