Foundry Academy · Virtual Professional Operations · Lesson 2 of 6

Task intake, priorities, and time

Convert requests into traceable commitments and manage priorities, capacity, dependencies, and recurring work without hiding tradeoffs.

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

Task intake, priorities, and time

Objective: Convert requests into traceable commitments and manage priorities, capacity, dependencies, and recurring work without hiding tradeoffs.

A task is not ready because it appears in a message. Capture requester, desired result, definition of done, deadline and time zone, priority reason, inputs, dependencies, confidentiality, approval, and next update. Restate ambiguity before acting. Distinguish an externally fixed deadline from a preferred date and an urgent interruption from work that is merely visible. If two authorized requests conflict, present the impact and ask the designated decision owner to choose; do not silently sacrifice one or work unsafe hours to conceal overcapacity.

Plan with a single trusted task system. Break work into observable next actions, reserve focused time, and give recurring tasks owners, checklists, calendars, and exception rules. Limit work in progress so status remains meaningful. Update before a deadline is missed, stating what changed, what is complete, what is blocked, options, recommendation, and the decision needed. Time records should be accurate and proportionate to the agreement, not reconstructed to please a client. A closed task includes result, location, exceptions, approval status, and any follow-up—not just a checked box.

Before you begin

  • Confirm F01, F02, F03, and F12; do not infer any individual request, requester, date, confidentiality label, conflict identity, approver, effort, or task outcome from aggregate counts.
  • STOP “Triage competing work” when this prerequisite cannot be confirmed: Confirm F01, F02, F03, and F12; do not infer any individual request, requester, date, confidentiality label, conflict identity, approver, effort, or task outcome from aggregate counts. 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

Portfolio field
Task-level due date, approver, confidentiality, conflict, effort/capacity, dependency, and completion evidence.
Aggregate evidence
27 tasks; only 9 have due dates, 7 name an approver, 5 are confidentiality-labeled, and 4 conflict with another authorized leader's request (M02-I01–M02-I03).
Source input ID
M02-I01 (F01); M02-I02 (F02); M02-I03 (F03); M02-I04 (F12)
Required task-level fields
Task ID, requested outcome, owner/requester, due date/time zone, approver, sensitivity, authority conflict, dependency, effort/capacity, evidence, and status.
Triage rule
Learner proposal — stop tasks with authority/sensitivity conflicts; clarify missing due date/approver; rank only after impact, urgency, effort, dependency, and capacity are documented.
Capacity dependency
Not supplied — assistant availability, task effort, service limits, and contingency capacity; 27-task count alone cannot establish feasibility.
Conflict or authority gate
Four assignments conflict with another authorized leader (M02-I03, F03); route each conflict to the named authorized decision roles before scheduling or execution.
Decision owner
The authorized portfolio sponsor and the leaders who issued the four conflicting assignments must resolve priority and authority; the confidentiality owner reviews any sensitive task. Specific assignees and decisions are not supplied and remain pending.
Status
Draft — cited evidence recorded; authorized review pending

A well-handled evidence gap

Portfolio field
Task-level source rows are incomplete.
Aggregate evidence
Counts supplied; record-level identities and facts not supplied.
Source input ID
M02-I04 (F12); M02-I03 (F03); M02-I02 (F02); M02-I01 (F01)
Required task-level fields
18 due dates, 20 approvers, confidentiality review, conflict disposition, effort, capacity, and dependencies remain missing or unresolved.
Triage rule
Proposed only; approval and record-level application not supplied.
Capacity dependency
Not supplied — hours, skills, availability, and service constraints.
Conflict or authority gate
Open — four conflicting assignments lack authorized resolution.
Decision owner
Not supplied — identify the portfolio sponsor, each conflicting request owner, and the confidentiality decision owner before scheduling the affected tasks.
Status
Blocked — required evidence or authorized decision not supplied

Flawed approach — do not copy

Marking this portfolio-level triage summary “approved and complete” without the required evidence or reviewer is a flawed submission. Stop individual ranking or execution when requester authority, deadline/time zone, confidentiality, conflict, dependency, effort, approver, or required control is missing.

Repair: Rework the portfolio-level triage summary as an evidence-backed draft, not an approved result. Capture the aggregate portfolio exactly: 27 tasks, nine due dates, seven named approvers, five confidential-client labels, and four cross-authority conflicts. Use a triage rubric covering authority, deadline/commitment, impact, dependency, confidentiality/control, effort/capacity, reversibility, and evidence confidence. Create the aggregate-safe TASK starter row supplied in this bank; never convert aggregate counts into fictional individual task attributes. Check the revision against this requirement: All five aggregate counts are exact and no individual task details are invented. 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 portfolio-level triage summary.

Turn the aggregate 27-task intake facts into a portfolio-level triage starter and design decision requests for the four reported conflicts without inventing the omitted task records.

Deliverable: A portfolio-level triage table, capacity view, blank 27-row task worksheet, and four conflict decision-request templates marked pending record-level evidence.

Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F12, 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
  • M02-I01 · F01 — The intake includes twenty-seven tasks but only nine have due dates.
  • M02-I02 · F02 — Seven tasks name an approver and five carry confidential-client labels.
  • M02-I03 · F03 — Four assignments conflict with another authorized leader's request.
  • M02-I04 · F12 — Current reporting counts completed tasks but omits quality, control, and outcome measures.
  • M02-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.
  • M02-S01 · F01, F02, F03, F12 — Build a starter version of “A portfolio-level triage table, capacity view, blank 27-row task worksheet, and four conflict decision-request templates marked pending record-level evidence.” 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. Capture the aggregate portfolio exactly: 27 tasks, nine due dates, seven named approvers, five confidential-client labels, and four cross-authority conflicts.
  2. Use a triage rubric covering authority, deadline/commitment, impact, dependency, confidentiality/control, effort/capacity, reversibility, and evidence confidence.
  3. Create the aggregate-safe TASK starter row supplied in this bank; never convert aggregate counts into fictional individual task attributes.
  4. Create one pending CONFLICT decision-request starter and replicate its structure only after individual conflict records are supplied.
  5. Apply the capacity rule: admit a task only after authority, required controls, due date, dependency, and effort are supplied; otherwise hold and request data.
  6. Route cross-leader conflicts or demand exceeding evidence-backed available capacity to the designated client decision owner; do not self-prioritize.
  7. Final-QC that task-level details, approvals, quality, control, outcomes, and completed work remain absent or pending.
Field-by-field guidance
Portfolio field
Name the specific task-level attribute being summarized—due date, approver, confidentiality, authority conflict, effort, capacity, dependency, completion evidence, or status—and cite M02-I01 (F01), M02-I02 (F02), M02-I03 (F03), or M02-I04 (F12). Mark record-level values not supplied when only aggregate counts exist. Do not invent individual tasks from counts. Review: the portfolio sponsor and affected control owner.
Aggregate evidence
For Aggregate evidence, transcribe the smallest decision-relevant fact supported by the cited module input and preserve its supplied confidence or uncertainty. Cite M02-I01 (F01), M02-I02 (F02), M02-I03 (F03); 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: M02-I01 (F01), M02-I02 (F02), M02-I03 (F03); 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.
Required task-level fields
List the specific minimum row fields needed before ranking: task ID, requested outcome, requester, due date and time zone, approver, sensitivity, authority conflict, dependency, effort, available capacity, evidence, and status. M02-I01 (F01), M02-I02 (F02), M02-I03 (F03), and M02-I04 (F12) supply only aggregate gaps; mark individual values not supplied. Do not reconstruct task identities. Review: the portfolio sponsor.
Triage rule
Write a specific learner-proposed sequence: stop authority or sensitivity conflicts, clarify missing due dates and approvers, then compare impact, urgency, effort, dependencies, and documented capacity. Use M02-I03 (F03) and M02-I04 (F12) as the conflict and quality-boundary evidence; mark approved priority policy not supplied. Never rank or execute a task from aggregate counts alone. Keep pending for the portfolio sponsor and conflicting request owners.
Capacity dependency
State the exact absent record, decision, method, value, or authority; explain why it matters and the bounded next request for Capacity dependency. Evidence: no direct “Triage competing work” source fact; mark “Not supplied” when absent. Do not hide the gap in narrative, fill it with a placeholder value, or imply the request was answered. Escalate to the client process owner and any required specialist.
Conflict or authority gate
Conflict or authority gate: Write a stop/go/escalate rule with its prerequisite, authorized decision role, evidence gate, and pending outcome. Cite M02-I03 (F03), M02-I04 (F12); if insufficient, mark “Not supplied” and name the missing decision gate. Do not execute the control, commit funds, release work, or claim a decision occurred in this exercise. Review: the client process owner and any required specialist.
Decision owner
For Decision owner, name the authorized role that must review or decide, then show the decision as pending unless an authorized record is supplied. No “Triage competing work” source fact supplies it; mark “Not supplied” and request the missing decision authority. Never invent a person's name, infer authority from job title, or record approval from silence. Keep pending for the client process owner and any required specialist.
Status
Select a truthful state—draft, open, blocked, pending review, or not supplied—and tie it to the evidence still required for Status. Evidence: M02-I03 (F03); mark “Not supplied” when absent. Do not mark complete, accepted, verified, distributed, or closed without the corresponding record. Escalate to the client process owner and any required specialist.
Portfolio-level triage summary · learning draft
Portfolio fieldAggregate evidenceSource input IDRequired task-level fieldsTriage ruleCapacity dependencyConflict or authority gateDecision ownerStatus

Start with 6 rows; the complete workbook specifies 8 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 2 · 2-item formative check

Task intake, priorities, and time

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 2 · knowledgeTwo authorized leaders assign conflicting tasks due at the same deadline. What should the assistant do?
Question 2 of 2 · MODULE 2 · scenarioHow should the assistant triage Pioneer’s task intake before promising a revised operating week?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • All five aggregate counts are exact and no individual task details are invented.
  • The TASK starter, CONFLICT request, triage rubric, and capacity rule are operationally explicit.
  • Task decisions, approvals, execution, and results remain pending.

Stop: Stop individual ranking or execution when requester authority, deadline/time zone, confidentiality, conflict, dependency, effort, approver, or required control is missing.

Go: Proceed to owner review only with a completed task row, evidence-backed available capacity, and no unresolved authority/control conflict.

Escalate: Escalate every cross-authority conflict and any demand above verified capacity to the designated client decision owner with options and tradeoffs.

04 · Evidence to keep

Leave with usable work.

A task board, capacity plan, decision log, recurring checklist, and three examples of complete status communication.

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.