Can an executive assistant maintain a decision log without becoming the decision-maker?

The hidden risk in “capture the decision”

Executive meetings produce approvals, preferences, tentative directions, assignments, and unanswered questions. If all of them enter one log as “decisions,” the record can give informal remarks false authority. If nothing is recorded, teams reconstruct intent from memory and contradictory messages. This study asks how a Philippines-based executive assistant can maintain a useful decision log while executives retain authority over the decision, audience, confidentiality, and retention. The unit of analysis is one asserted decision connected to a meeting, written approval, or designated system event. The assistant may prepare a candidate entry from an authorized source, identify the decision owner, link supporting material, route it for confirmation, publish the approved version to the permitted audience, and track actions. The assistant should not convert discussion into commitment, resolve conflicting executives, expose privileged or sensitive content, decide who is bound, or determine the official record category. A reliable log separates proposed, confirmed, superseded, withdrawn, and closed states. It also distinguishes the decision statement from follow-up tasks. “Adopt vendor A” is different from “Jordan will request the contract by Friday.” Recording both as one task loses authority and rationale; recording every conversational detail increases privacy and discovery risk without improving execution.

Evidence principles from authoritative frameworks

GAO’s Standards for Internal Control describes principles involving documentation, quality information, responsibility, and corrective action. NARA guidance on electronic records and Capstone addresses systematic management of electronic communications in the federal context. NIST’s Privacy Framework helps organizations identify and manage privacy risk, and CISA’s Zero Trust Maturity Model emphasizes identity, access, visibility, and governance concepts. These sources do not dictate a private company’s meeting log or make an executive assistant a records officer. Their value is structural: information should have known provenance, access should reflect purpose, responsibilities should be assigned, and records should be managed deliberately. A business still needs advice suited to its laws, contracts, litigation posture, sector, and systems. A decision log is not automatically a board minute book, legal approval, contract amendment, accounting authorization, or retention schedule. The assistant should state what the source shows and use the company’s approved labels. If counsel marks a matter privileged or an executive limits distribution, that instruction controls the lane. If two sources disagree, the log should show a conflict awaiting owner resolution rather than selecting the more recent or more senior-sounding message by guesswork.

A decision entry that can survive handoff

A complete candidate entry begins with a unique identifier, source event, source link, source timestamp and timezone, proposed decision statement, accountable decision owner, effective date if stated, affected scope, constraints, confirmation status, audience, and related actions. Record the assistant who prepared it and the owner who confirmed it. The decision statement should be short enough to quote accurately and specific enough to distinguish it from discussion. Rationale belongs only where approved; the log may link to a restricted memo rather than duplicate sensitive detail. Follow-up tasks need separate owners, due dates, dependencies, and status. If an action completes, the decision remains unless its owner withdraws or supersedes it. If a later decision changes direction, link the predecessor and successor; do not edit history until the old choice appears never to have existed. Attachments and chat excerpts should remain in their controlled source systems where possible. Copying a whole conversation into the log increases exposure and removes context. The record should indicate missing elements openly: “effective date not stated” is better than the meeting date inserted as a guess. The confirmation workflow should ask the owner to approve the meaning and scope, not merely click a generic completion box.

Stress-test ambiguity, authority, and access

Create synthetic scenarios based on the company’s meeting patterns. Include a clear written approval, a verbal preference followed by “let’s investigate,” two executives giving incompatible instructions, a decision contingent on legal review, a time-limited exception, a confidential personnel matter, an action assigned without a policy decision, a decision made outside the meeting, and a later message that appears to reverse an earlier direction. Add an executive who does not respond to confirmation and a participant who asks to see a restricted entry. Freeze the owner matrix, meeting types, source hierarchy, state definitions, access groups, and escalation route. The assistant prepares candidate entries; authorized executives or governance owners independently classify them. Compare statement accuracy, source linkage, owner identity, state, effective date, audience, action separation, and supersession. Severe events include publishing an unconfirmed commitment, disclosing a restricted matter, attributing a decision to the wrong owner, or erasing a prior approved state. The test reveals whether the operating definitions work under ambiguity. It does not prove corporate authority, privilege, records compliance, or that a decision was wise.

Exceptions should remain visible

The routine lane should stop when authority is unclear, sources conflict, confidentiality markings differ, the matter concerns litigation or investigation, a personnel or health issue appears, a contract or payment authorization is implied, or someone asks for retroactive wording that changes the historical record. The assistant should preserve the source, restrict access, label the uncertainty, and route it to the named executive, legal, HR, finance, privacy, security, or records owner. They should not poll attendees to create a majority interpretation, downgrade a confidentiality label, or rewrite an old entry in place. An unavailable executive creates a pending decision, not implied approval. Emergency decisions can use a documented expedited path with a later confirmation requirement; they should not become a reason to remove provenance. Corrections need a reason, actor, and timestamp. When access changes after a reorganization or departure, review both the log and its linked sources. A person’s ability to see the meeting calendar does not necessarily grant access to every decision record. Conversely, hiding ordinary operating decisions in a private executive notebook prevents accountable owners from acting. The audience field should be a deliberate part of confirmation.

Measure usefulness without turning the log into surveillance

Useful operational measures include candidate entries awaiting confirmation, confirmed decisions with complete owner and scope, actions linked to a current decision, unresolved conflicts, superseded entries linked correctly, access exceptions, corrections by reason, and time between source event and owner confirmation. Sample whether readers can trace an entry to its authorized source and identify the current version. Ask action owners whether the record answers what changed, who decided, when it applies, and what they own. Avoid ranking executives by decision count or treating short confirmation time as good governance. A low conflict count may mean clarity or suppressed disagreement. A high correction rate may reflect poor capture or a healthy new review practice. Do not collect detailed attendee behavior to improve a simple decision register. The management gate is whether the log reduces contradictory execution while preserving authority and appropriate access. If confirmed entries remain traceable and exceptions are resolved by the correct owners, preparation can be delegated. Decision rights, sensitive classification, legal interpretation, retention policy, and final communication remain with accountable leadership.

Launch sequence and study limits

Start with one recurring operating meeting that does not routinely handle privileged, board, medical, or personnel matters. Define what counts as a decision, which source controls, who can confirm, allowed states, audience groups, and how supersession works. Configure the log so assistant preparation and owner confirmation are different actions. Use synthetic examples, then shadow several meetings without publishing candidate entries as final. Review every entry until owners agree that the language and state definitions are stable. Add only one new meeting type at a time because authority and confidentiality may differ. Establish how the register interacts with project tasks, minutes, contracts, policies, and records systems; it should link rather than pretend to replace them. Review access on a schedule and when roles change. This is a qualitative workflow study based on broad public governance, records, privacy, and access frameworks. It does not establish a retention period, legal record, board procedure, or security architecture, and it reports no company performance. Its conclusion is conditional: an executive assistant can improve continuity by preparing and maintaining a confirmation-based log, provided every consequential entry preserves source, owner, status, audience, and history. Without those fields, the log risks becoming confident-looking hearsay.

Does this study report service performance?

No. It proposes a bounded workflow and reports no observed company, assistant, or customer outcomes.

Who keeps consequential decisions?

The business and its authorized legal, finance, HR, safety, privacy, security, tax, or executive owners retain decisions within their fields.

When should the support lane expand?

Only after representative cases remain reconstructable and exceptions reach the named owner.