Foundry Academy · Virtual Professional Operations · Lesson 3 of 6

Calendar, meeting, and document operations

Coordinate calendars, meetings, and documents through controlled permissions, accurate records, and explicit owner approval.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Calendar, meeting, and document operations

Objective: Coordinate calendars, meetings, and documents through controlled permissions, accurate records, and explicit owner approval.

Calendar access is delegated authority, not ownership of another person's time. Confirm scheduling rules, working hours, time zones, travel buffers, meeting priority, privacy labels, attendee approval, and who may move or cancel events. Before sending an invitation, verify purpose, attendees, duration, location or link, preparation, and decision needed. Protect private appointment details and never infer why a person is unavailable. For changes, preserve notice and update every participant through the approved calendar rather than relying on a separate message.

A useful meeting produces a record proportionate to its purpose. Prepare an agenda, pre-read, roles, and desired decisions. Capture decisions, actions, owners, due dates, unresolved questions, and approved distribution; do not record sensitive discussions without authority. Documents need a named owner, controlled location, meaningful filename, version or status, access rule, and review route. Avoid duplicate 'final' files by using the agreed system. Before external sharing, confirm recipient, attachment or link, permissions, confidential content, accessibility, and approval. Delete or retain records only under the applicable policy.

Before you begin

  • Confirm F04 and F05; recognize that the authoritative date-specific meeting time, current approved revenue figure, owner, version, distribution list, and approval status are not supplied.
  • STOP “Control calendar and documents” when this prerequisite cannot be confirmed: Confirm F04 and F05; recognize that the authoritative date-specific meeting time, current approved revenue figure, owner, version, distribution list, and approval status are not supplied. Record the exact missing or conflicting evidence, keep the artifact blocked, and route it to the authorized client process owner, with security, privacy, payment, contract, or subject review when applicable. Do not execute the workflow, make the specialist judgment, record approval, or claim an operational result.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This fictional, sanitized virtual-operations case uses invented people, organizations, calendars, records, and requests. It contains no real personal or confidential data and grants no employment, legal, financial, or security authority.

Pioneer Advisory operating week

Pioneer Advisory is a fictional three-partner consulting firm onboarding a remote virtual professional for a simulated operating week. The shared intake contains 27 tasks. Nine have a due date, seven name an approver, five include confidential-client labels, and four conflict with another leader's request. One partner marks every task urgent. The calendar shows a client review at 10:00 a.m. Mountain on Thursday, while the invitation body says 10:00 a.m. Central and two attendees accepted from different time zones. A meeting brief contains one outdated revenue figure copied from an earlier deck. The assistant receives a request to book travel using a photographed credit card sent in chat and another request to log in through the partner's personal password. A research task asks for current licensing requirements but provides no jurisdiction or authoritative source standard. A draft client email says the firm guarantees funding approval within 30 days, although the agreement contains no such commitment and the assistant has no authority to discuss outcomes. A prospect asks to remove their information from the mailing list. The CRM sequence is still active and has already created tomorrow's follow-up task. On Friday, a partner asks the assistant to send an unsigned contract and describe it as approved to keep the deal moving. Service reporting currently counts completed tasks but not rework, missed dependencies, unsafe requests, or client-confirmed outcomes. Learners must establish professional boundaries, triage priorities, coordinate calendar and document operations, produce traceable research, communicate and escalate responsibly, and review confidentiality and service quality. Completing the exercise does not authorize access to real client systems or qualify the learner to make licensed or binding decisions.

Supported example — reference only

Correction item
Thursday meeting date/time-zone meaning and revenue figure.
Supported issue
Meeting lists different Mountain and Central time-zone meanings (M03-I01, F04); brief contains an outdated revenue figure (M03-I02, F05).
Source input ID
M03-I01 (F04); M03-I02 (F05)
Source preserved
Preserve the original meeting record and brief as received; create a separate correction request rather than silently editing either source.
Missing authoritative evidence
Exact date, IANA zones/UTC offsets, authoritative meeting time, current approved revenue source, version/date, and release owner are not supplied.
Decision requested
Meeting owner to confirm exact date/time and zones; financial/source owner to provide the current approved revenue record; distribution owner to approve correction notice.
Version or owner
Correction draft version 0.1 (learner label); authoritative version and owners not supplied.
Distribution status
Not distributed — recipient list, owner approval, and evidence of corrected distribution are not supplied.
Reviewer
Meeting owner confirms the exact date, time, and zones; financial/source owner validates the current revenue record; distribution owner authorizes the correction notice. Named assignees and approvals remain pending unless documented.
Status
Draft — cited evidence recorded; authorized review pending

A well-handled evidence gap

Correction item
Two corrections identified; authoritative replacements not supplied.
Supported issue
Conflicts preserved at M03-I01 and M03-I02; no resolution inferred.
Source input ID
M03-I02 (F05); M03-I01 (F04)
Source preserved
Preservation location/version evidence not supplied.
Missing authoritative evidence
Date-specific time-zone source and approved revenue source absent.
Decision requested
Pending meeting, financial/source, and distribution owners.
Version or owner
Not supplied — controlled correction version and accountable owner.
Distribution status
Blocked — correction not approved or distributed.
Reviewer
Not supplied — identify the meeting owner, financial/source owner, and correction-distribution owner before release.
Status
Blocked — required evidence or authorized decision not supplied

Flawed approach — do not copy

Marking this meeting-correction request “approved and complete” without the required evidence or reviewer is a flawed submission. Stop calendar/brief distribution when authoritative date/time or approved current revenue evidence is absent or conflicting.

Repair: Rework the meeting-correction request as an evidence-backed draft, not an approved result. Preserve the two conflicting Mountain/Central interpretations without choosing one. Request one date-specific authoritative meeting time, including named time zone and UTC offset where approved. Record the outdated revenue figure as a correction need without inventing a replacement value. Check the revision against this requirement: Both conflicts/gaps are cited and preserved. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the meeting-correction request.

Resolve the meeting time and repair the brief without overwriting source evidence.

Deliverable: A meeting-correction request, agenda, decision-ready brief, and version log; the invitation remains pending a verified date, time, and zone.

Complete a bounded starter and gap analysis using only CB01, F04, F05, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M03-I01 · F04 — The Thursday meeting lists different Mountain and Central time-zone meanings.
  • M03-I02 · F05 — The meeting brief includes an outdated revenue figure.
  • M03-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M03-S01 · F04, F05 — Build a starter version of “A meeting-correction request, agenda, decision-ready brief, and version log; the invitation remains pending a verified date, time, and zone.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Preserve the two conflicting Mountain/Central interpretations without choosing one.
  2. Request one date-specific authoritative meeting time, including named time zone and UTC offset where approved.
  3. Record the outdated revenue figure as a correction need without inventing a replacement value.
  4. Define source-owner, version, approval, and distribution fields for both the calendar correction and updated brief.
  5. Route the time decision and revenue-source approval to the authorized client/operating owner.
  6. Final-QC that the original record is preserved and no time, revenue, approval, update, or distribution is claimed.
Field-by-field guidance
Correction item
Name one specific discrepancy and the authoritative replacement required: the conflicting Mountain/Central meeting meaning at M03-I01 (F04) or the outdated revenue figure at M03-I02 (F05). If the exact date, zone, current value, version, or owner is not supplied, state that gap. Do not silently edit the source or invent a corrected value. Review: the meeting owner or financial/source owner, plus the distribution owner.
Supported issue
For Supported issue, transcribe the smallest decision-relevant fact supported by the cited module input and preserve its supplied confidence or uncertainty. Cite M03-I01 (F04), M03-I02 (F05); if insufficient, mark “Not supplied” and name the missing bounded evidence. Never convert a report, allegation, estimate, or provisional statement into a verified fact. Keep pending for the client process owner and any required specialist.
Source input ID
List the exact module input ID beside every material statement, adding its fact ID when present for Source input ID. Evidence: M03-I01 (F04), M03-I02 (F05); mark “Not supplied” when absent. Do not cite the case brief as approval or cite an input that does not support the statement. Escalate to the client process owner and any required specialist.
Source preserved
Source preserved: Identify the controlled record, location, version, date, and module citation that governs this entry. No “Control calendar and documents” source fact supplies it; mark “Not supplied” and request the missing controlled provenance. Do not treat an undated draft, copied text, or secondary summary as the controlling record. Review: the client process owner and any required specialist.
Missing authoritative evidence
For Missing authoritative evidence, state the exact absent record, decision, method, value, or authority; explain why it matters and the bounded next request. Cite M03-I01 (F04); if insufficient, mark “Not supplied” and name the missing gap discipline. Never hide the gap in narrative, fill it with a placeholder value, or imply the request was answered. Keep pending for the client process owner and any required specialist.
Decision requested
Write a stop/go/escalate rule with its prerequisite, authorized decision role, evidence gate, and pending outcome for Decision requested. Evidence: M03-I02 (F05); mark “Not supplied” when absent. Do not execute the control, commit funds, release work, or claim a decision occurred in this exercise. Escalate to the client process owner and any required specialist.
Version or owner
Version or owner: Name the authorized role that must review or decide, then show the decision as pending unless an authorized record is supplied. Cite M03-I01 (F04), M03-I02 (F05); if insufficient, mark “Not supplied” and name the missing decision authority. Do not invent a person's name, infer authority from job title, or record approval from silence. Review: the client process owner and any required specialist.
Distribution status
For Distribution status, select a truthful state—draft, open, blocked, pending review, or not supplied—and tie it to the evidence still required. Cite M03-I02 (F05); if insufficient, mark “Not supplied” and name the missing state control. Never mark complete, accepted, verified, distributed, or closed without the corresponding record. Keep pending for the client process owner and any required specialist.
Reviewer
Name the authorized role that must review or decide, then show the decision as pending unless an authorized record is supplied for Reviewer. Evidence: no direct “Control calendar and documents” source fact; mark “Not supplied” when absent. Do not invent a person's name, infer authority from job title, or record approval from silence. Escalate to the client process owner and any required specialist.
Status
Status: Select a truthful state—draft, open, blocked, pending review, or not supplied—and tie it to the evidence still required. Cite M03-I02 (F05); if insufficient, mark “Not supplied” and name the missing state control. Do not mark complete, accepted, verified, distributed, or closed without the corresponding record. Review: the client process owner and any required specialist.
Meeting-correction request · learning draft
Correction itemSupported issueSource input IDSource preservedMissing authoritative evidenceDecision requestedVersion or ownerDistribution statusReviewerStatus

Start with 4 rows; the complete workbook specifies 4 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 3 · 2-item formative check

Calendar, meeting, and document operations

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 3 · knowledgeWhich information belongs in a complete closure record for an administrative task?
Question 2 of 2 · MODULE 3 · scenarioWhat should happen before Pioneer distributes the Thursday meeting brief and calendar invitation?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • Both conflicts/gaps are cited and preserved.
  • Date/time and revenue-source decisions have explicit reviewer fields.
  • No time conversion, revenue number, approval, update, or distribution is invented.

Stop: Stop calendar/brief distribution when authoritative date/time or approved current revenue evidence is absent or conflicting.

Go: Proceed to document review when source, owner, version, decision, and distribution fields are complete.

Escalate: Escalate the time conflict and financial-content correction to their authorized owners; do not resolve either by assumption.

04 · Evidence to keep

Leave with usable work.

Calendar invitation, scheduling checklist, agenda, decision and action record, document register, permission review, and distribution log.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Virtual professional completing structured work from a home office.
Learn the standard. Practice the work.
Remote business professional managing focused client work from home.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

ws-virtual-professional-operating-standard · Academy internal operating standard

Wealth Synergy virtual-professional internal operating standard

Academy-selected charter, intake, priority, record, research, communication, access, and service-review controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.