Foundry Academy · Government Proposal Coordination · Lesson 3 of 6

Proposal calendar and responsibility map

Build a backward plan that protects review, authorization, and submission time while assigning one accountable owner to every output.

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

Proposal calendar and responsibility map

Objective: Build a backward plan that protects review, authorization, and submission time while assigning one accountable owner to every output.

Plan backward from the official receipt deadline and time zone, not from the team's preferred finish date. Include questions, teaming decisions, data calls, outline approval, first draft, pricing inputs, compliance checks, color or structured reviews, corrections, executive authorization, final production, upload, receipt confirmation, and contingency time. Check weekends, holidays, system maintenance, file limits, and registration status. Internal deadlines should leave enough time to recover from a missing attachment, invalid signature, portal error, or late amendment.

Assign one accountable owner to each requirement, section, attachment, evidence request, and approval. Define contributors, reviewer, backup, dependency, and escalation trigger. Only authorized personnel approve price, contractual exceptions, representations, certifications, and final submission. Protect source-selection-sensitive, proprietary, personal, export-controlled, classified, or controlled unclassified information according to applicable requirements; a general collaboration folder may be inappropriate. Review the critical path daily near submission. When a deadline slips, record the effect and decision rather than silently compressing legal, pricing, or compliance review.

Before you begin

  • Confirm the official Eastern deadline and internal Mountain-time discrepancy.
  • Do not calculate a local deadline without the year and date-specific conversion evidence.
  • Identify price and representation approvals that must precede packaging.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This is a fictional, sanitized training case. Solicitation identifiers, agencies, companies, people, pricing, and performance records are invented and are not legal, contracting, pricing, or government representations advice.

Canyon Response Logistics proposal sprint

Canyon Response Logistics, a fictional small business, is considering a federal request for quotations for emergency warehouse staging. The official package was downloaded on September 3 and requires electronic submission by 2:00 p.m. Eastern on September 18. It contains 47 stated requirements, a price schedule with 12 line items, two mandatory representations, three past-performance examples, and a 12-page technical limit. An amendment issued September 10 changes the delivery window from 30 days to 14 days, replaces one line-item quantity, and requires explicit amendment acknowledgment. The capture lead's calendar still uses the original deadline in Mountain Time and the draft compliance matrix has not incorporated the amendment. Operations believes 14-day delivery is possible only if a subcontracted warehouse is available; the subcontractor supplied an unsigned availability email but no binding commitment. Finance's workbook totals $486,200, while the price form totals $468,200 because a freight row is omitted. A resume says the proposed project manager led a $3 million federal program, but the approved employment record shows the person served as deputy for nine months. One past-performance reference has not granted current contact permission. The draft technical narrative is 13.5 pages before final graphics. The company president may sign offers up to $500,000, but the proposal coordinator has no signature or certification authority. The government portal requires multi-factor authentication and has a 25-megabyte package limit; the current folder is 31 megabytes and contains working notes that should not be submitted. Learners must qualify the opportunity, rebuild compliance control, coordinate evidence and review, and demonstrate a submission process. They must not invent commitments, alter official instructions, or represent that training guarantees award or eligibility.

Supported example — reference only

Milestone or date
September 18, 2:00 p.m. Eastern; year and local conversion not supplied
Deliverable
Authorized final submission
Evidence
M03-I01 (F01, confirmed)
Owner
Authorized submission owner; name not supplied
Dependency
Price, representations, page limit, package, signature, and amendment acknowledgment must be approved.
Review gate
Proceed only after authorized package-readiness disposition and confirmed portal plan.
Exception
Internal calendar uses original Mountain-time deadline. M03-I03 (F04, confirmed).
Status
Official deadline recorded — conversion gap open

A well-handled evidence gap

Milestone or date
Date-specific internal cutoff
Deliverable
Verified local deadline and team handoff schedule
Evidence
Official Eastern deadline supplied; year and correct local conversion not supplied.
Owner
Authorized proposal lead
Dependency
Official year, date-specific time-zone conversion, and approved internal buffer.
Review gate
Do not publish the local cutoff until verified against the controlling source.
Exception
Current internal Mountain-time entry conflicts with official deadline.
Status
Gap open — schedule not final

Flawed approach — do not copy

Marking this proposal calendar “approved and complete” without the required evidence or reviewer is a flawed submission. Stop packaging or submission when deadline conversion, price, representations, version, page limit, or authority remains unresolved.

Repair: Rework the proposal calendar as an evidence-backed draft, not an approved result. Anchor the calendar on September 18 at 2:00 p.m. Eastern and cite F01. Mark the year and date-specific local conversion not supplied instead of using the internal Mountain-time entry. Sequence compliance, amendment, price, representation, page, package, and submission reviews backward from the official deadline. Check the revision against this requirement: The official Eastern deadline is preserved and missing year/local conversion remain explicit. 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 proposal calendar.

Build a backward schedule with review windows, dependencies, and a documented time-zone conversion.

Deliverable: A provisional proposal calendar, responsibility map, deadline-verification request, and daily exception-report template.

Complete a bounded starter and gap analysis using only CB01, F01, F03, F04, F07, F10, F11, 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
  • M03-I01 · F01 — The official submission deadline is September 18 at 2:00 p.m. Eastern.
  • M03-I02 · F03 — Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
  • M03-I03 · F04 — The internal calendar still displays the original deadline in Mountain Time.
  • M03-I04 · F07 — Finance totals $486,200 and the required price form totals $468,200.
  • M03-I05 · F10 — The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
  • M03-I06 · F11 — The coordinator lacks authority to sign the offer or certify representations.
  • M03-I07 · F12 — The current upload folder is 31 megabytes and includes internal working notes.
  • 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 · F01, F03, F04, F07, F10, F11, F12 — Build a starter version of “A provisional proposal calendar, responsibility map, deadline-verification request, and daily exception-report template.” 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. Anchor the calendar on September 18 at 2:00 p.m. Eastern and cite F01.
  2. Mark the year and date-specific local conversion not supplied instead of using the internal Mountain-time entry.
  3. Sequence compliance, amendment, price, representation, page, package, and submission reviews backward from the official deadline.
  4. Place price reconciliation and representation authorization before final packaging or upload preparation.
  5. Assign accountable owner and backup roles to each critical handoff without inventing staff names.
  6. Add exception triggers for deadline conflict, page overage, price mismatch, signature boundary, and package contamination.
  7. Quality-check time zone, dependencies, review gates, and absence of invented dates or completed milestones.
Field-by-field guidance
Milestone or date
Use the official deadline or a proposed relative milestone; mark calendar dates not supplied.
Deliverable
Name the specific compliance, price, representation, page, package, or submission output.
Evidence
Cite the supplied deadline or constraint and preserve its status.
Owner
Use accountable proposal, pricing, representation, packaging, or submission roles only.
Dependency
State prerequisite evidence or approval that must close first.
Review gate
Define the evidence and authorized disposition required to advance.
Exception
Name deadline, version, price, page, authority, or package problem.
Status
Use Proposed, Conflict open, Blocked, Review pending, or Ready for authorized review.
Proposal calendar · learning draft
Milestone or dateDeliverableEvidenceOwnerDependencyReview gateExceptionStatus

Start with 2 rows; the complete workbook specifies 2 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

Proposal calendar and responsibility map

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 · knowledgeWho should approve the final offered price and binding representations before submission?
Question 2 of 2 · MODULE 3 · scenarioHow should Canyon Response build its proposal calendar from the supplied deadline records?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • The official Eastern deadline is preserved and missing year/local conversion remain explicit.
  • Critical approvals precede packaging and submission.
  • Each handoff has accountable and backup roles without invented staff names.

Stop: Stop packaging or submission when deadline conversion, price, representations, version, page limit, or authority remains unresolved.

Go: Go to the next calendar gate when its dependencies, owner, backup, and evidence are visible.

Escalate: Escalate official deadline interpretation and submission authority to the authorized proposal or contracting reviewer.

04 · Evidence to keep

Leave with usable work.

Backward calendar, responsibility matrix, dependency map, access list, escalation record, and approved recovery plan.

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.

Proposal team reviewing printed requirements and compliance paperwork in an office.
Learn the standard. Practice the work.
Professionals presenting and reviewing a coordinated business proposal.
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.

far-15-204 · Current codified text

FAR 15.204: Contract format

Primary Federal Acquisition Regulation source describing the uniform contract format and its limits.

Open reviewed external source ↗

far-4-802 · Current codified text

FAR 4.802: Contract files

Illustrative government-side contract-file rule for contracting, contract administration, and paying offices. It is not an offeror record-retention requirement; an offeror must identify its own applicable solicitation, contract, law, policy, and counsel-approved retention obligations.

Open reviewed external source ↗

ws-government-proposal-operating-standard · Academy internal operating standard

Wealth Synergy government-proposal coordination internal operating standard

Academy-selected requirement, version, review, evidence, handoff, and submission-simulation 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.