Founder & Finance School · Learning track

Government Proposal Coordination

Coordinate compliant proposal work without blurring authorship, legal review, or contracting authority.

Start Lesson 1

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 Learning plan

Know the work.
Produce evidence.

Public foundation 2026.10.08-learning-paths-1 · published 2026-10-08. Independent subject-matter review is pending; paid delivery and credential issuance remain closed. This track is organized around inspectable work, not attendance alone.

Workload

No validated completion time is published. Read the six modules, then complete the six case assignments and self-review across as many sessions as needed. This release has not yet been timed with learners; no facilitated capstone is included.

Prerequisites

  • Basic business writing and spreadsheet skills
  • Access to a public training solicitation or a fictional solicitation that contains no protected procurement information
  • Understanding that only authorized officials may certify, price, submit, negotiate, or bind an offeror

Outputs

  • Bid or no-bid qualification brief
  • Requirement-level compliance matrix
  • Proposal calendar and responsibility map
  • Evidence, past-performance, and resume request register
  • Controlled review and submission record

Demonstrated outcomes

  • Build a requirement-by-requirement compliance matrix
  • Coordinate owners and review gates
  • Maintain an evidence and version trail
  • Escalate legal, pricing, and certification questions

Working vocabulary

Solicitation
The government's request and governing package that states requirements, instructions, provisions, clauses, and evaluation approach.
Compliance matrix
A control table mapping each material solicitation requirement to an owner, response location, evidence source, and review status.
Amendment
An official change to a solicitation that may revise requirements, dates, instructions, terms, or answers and must be controlled.
Past performance
Relevant record of prior contract or project performance considered under the solicitation's stated rules and evaluation factors.
Contracting officer
A government official with delegated authority to enter into, administer, or terminate contracts and make related determinations.

02 Public foundation curriculum

Six foundation
learning modules.

Each module states what to understand, what to practice, what evidence to retain, and the criteria for moving forward. The case lab turns those standards into six realistic assignments.

01

Module 1

Opportunity qualification

Objective: Determine whether an opportunity is real, current, eligible, strategically relevant, and supportable before committing proposal resources.

Open Lesson 1: examples, worksheet & feedback →

Begin at the official notice and solicitation, not an aggregator or forwarded summary. Confirm agency, notice identifier, procurement type, set-aside, NAICS code, place of performance, due date and time zone, submission method, amendments, questions deadline, required registration, and point of contact. Verify the entity's SAM.gov status when registration is required; registration is free on SAM.gov. A coordinator may organize the check, but authorized leadership and qualified advisers must resolve representation, certification, size, affiliation, responsibility, or eligibility questions.

Build a bid or no-bid brief around customer fit, scope, mandatory requirements, evaluation factors, relevant experience, team availability, delivery capacity, pricing readiness, contract risk, conflicts, and probability based on evidence. Estimate the cost of pursuit and opportunity cost. Identify every unknown that could make the offer nonresponsive or unperformable. Do not assume an incumbent relationship, certification, clearance, socioeconomic status, or subcontractor commitment. Record the decision owner and conditions for approval. A no-bid is a successful outcome when it prevents a weak, ineligible, misleading, or operationally unsafe submission.

Practice

Qualify one public training opportunity using only official sources and present a documented bid, conditional bid, or no-bid recommendation.

Evidence to keep

Official notice links, solicitation version, amendment log, eligibility checklist, capability assessment, pursuit estimate, risk register, and signed decision.

Ready to move on when

  • The opportunity and all controlling documents are verified at official sources
  • Mandatory eligibility and capability gaps are visible and assigned for authorized resolution
  • The recommendation identifies decision owner, conditions, costs, risks, and evidence

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

02

Module 2

Solicitation reading and compliance matrix

Objective: Translate the complete solicitation and amendments into a requirement-level control system without adding or omitting obligations.

Open Lesson 2: examples, worksheet & feedback →

Read the package in layers. First identify purpose, structure, dates, and submission channel. Next extract instructions, evaluation factors, statement of work or objectives, deliverables, clauses, representations, attachments, formatting, and page limits. Then trace cross-references and incorporate every amendment. The uniform contract format can help orientation, but solicitations vary by method and agency. Never rely on section letters alone. Preserve the authoritative file, checksum or version identifier where practical, download date, and source URL.

Create one compliance-matrix row for each material requirement and separate instruction, evaluation, contractual, and performance obligations. Record the exact reference, concise paraphrase, response location, owner, evidence, review criterion, status, and unresolved question. Quote only what is needed and do not reinterpret legal terms. Conflicts, ambiguities, or questions for the government follow the solicitation's authorized communication process; the coordinator does not contact program staff informally or invent an answer. After an amendment, run a documented delta review and reopen affected rows, outlines, pricing inputs, and approvals.

Practice

Extract at least twenty-five requirements from a training solicitation and process one simulated amendment through the matrix.

Evidence to keep

Versioned solicitation library, cross-reference map, requirement-level compliance matrix, question log, amendment delta, and reviewer signoff.

Ready to move on when

  • Every material instruction and evaluation factor maps to a response location and owner
  • Amendments are acknowledged and their downstream effects are documented
  • Ambiguous legal or contracting terms are escalated through authorized channels

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

03

Module 3

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.

Open Lesson 3: examples, worksheet & feedback →

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.

Practice

Create a twenty-business-day production calendar for the training solicitation, then simulate a three-day evidence delay and replan without removing mandatory review.

Evidence to keep

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

Ready to move on when

  • The schedule includes all external and internal deadlines, reviews, authorization, production, and contingency
  • Each output has one accountable owner, backup, dependency, and escalation trigger
  • Price, representations, exceptions, and submission remain reserved for authorized personnel

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

04

Module 4

Evidence, past performance, and resumes

Objective: Collect accurate, permitted, solicitation-relevant proof while preventing unsupported, stale, or unauthorized claims.

Open Lesson 4: examples, worksheet & feedback →

Issue structured data calls tied to the compliance matrix. For each requested item, state the requirement, evaluation use, format, period, owner, reviewer, source, due date, and sensitivity. Past-performance material should match the solicitation's definition of recency and relevance and accurately identify scope, role, value, dates, outcomes, and customer contact rules. Do not rename subcontractor work as prime experience, inflate contract value, omit material performance problems, or reuse a customer reference without permission and current contact details.

Resumes and key-personnel summaries must reflect real qualifications, availability, employment or teaming status, and proposed role. Confirm consent before using personal information. Reconcile dates, titles, credentials, and project descriptions with source records; do not add keywords that imply experience the person does not have. Maintain an evidence library with version, approval, reuse restriction, and expiration date. Contracting, privacy, employment, export-control, clearance, and proprietary-information questions may require authorized legal, security, human-resources, or contracting review. The coordinator's job is traceability and timely escalation, not certification of facts outside their authority.

Practice

Prepare one compliant past-performance record and one key-person resume from a fictional evidence packet containing inconsistencies and restricted information.

Evidence to keep

Data-call log, source-to-claim matrix, permissions, corrected record, resume approval, sensitivity marking, and unresolved discrepancy list.

Ready to move on when

  • Every material claim maps to a current source and authorized owner
  • Role, scope, dates, value, outcomes, and relationship are represented without inflation
  • Personal, proprietary, and controlled information follows approved access and reuse rules

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

05

Module 5

Color-team review and document control

Objective: Run criteria-based reviews and controlled revisions that improve compliance, evidence, and evaluator usability without losing authorship or approval integrity.

Open Lesson 5: examples, worksheet & feedback →

A review needs a defined purpose. Early reviews may test solution logic and outline coverage; later reviews test persuasiveness, compliance, evidence, consistency, price alignment, and production readiness. Use the solicitation's evaluation factors and requirements as the primary rubric. Assign reviewers who are independent enough to challenge the draft and brief them on scope, prohibited information, comment format, and deadline. Comments should identify the requirement, observed issue, consequence, and recommended correction. Personal preference is not a review criterion.

Control the document through a named system of record, approved file naming, version ownership, check-in rules, and a master change log. Decide who may accept, reject, or defer comments and require reasons for material decisions. Lock approved sections at defined points while preserving an authorized path for late amendments or cross-volume corrections. Run automated and human checks for requirement coverage, page limits, fonts, cross-references, acronyms, names, numbers, attachments, accessibility, and metadata. Before final production, remove comments, tracked changes, hidden text, prior versions, and unintended personal or proprietary metadata.

Practice

Conduct a structured review of a flawed five-page response, adjudicate ten comments, and produce a clean controlled revision with a change log.

Evidence to keep

Review plan, rubric, annotated draft, comment-adjudication log, controlled master, production checklist, and approval record.

Ready to move on when

  • Review findings are tied to requirements, evaluation factors, evidence, or production controls
  • Every material change has an owner, disposition, reason, and resulting version
  • The final file contains no comments, tracked changes, hidden material, or unintended metadata

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

06

Module 6

Submission, confirmation, and lessons learned

Objective: Execute an authorized, verifiable submission and preserve a complete record for follow-up, debrief, and process improvement.

Open Lesson 6: examples, worksheet & feedback →

Treat submission as a controlled operational event. Confirm the final package against the matrix, amendment acknowledgments, filenames, formats, size limits, signatures, attachments, representations, and authorized approval. Verify the portal account and registration early. Use the method named in the solicitation; do not substitute ordinary email or a different portal because it seems easier. The authorized submitter should upload with contingency time, capture the receipt or confirmation identifier, and preserve the exact submitted files. A draft saved locally is not evidence that the government received the offer.

After submission, restrict changes and record any agency communication through the designated channel. Preserve the solicitation version, matrix, approvals, submitted package, confirmation, questions, clarifications, and outcome according to organizational and applicable contract-record policies. If a debrief is available, follow the stated request procedure and deadline. Conduct an internal lessons-learned review that separates outcome from process quality: a loss does not prove the process failed, and a win does not excuse control failures. Do not speculate about competitors or source-selection information. Convert verified findings into named process changes with owners and review dates.

Practice

Run a timed mock submission, verify the receipt, reconstruct the exact package from the archive, and facilitate a thirty-minute lessons-learned review.

Evidence to keep

Final compliance check, authorization, exact submitted files, timestamped receipt, communication log, archive index, and improvement register.

Ready to move on when

  • The authorized submitter can prove what was submitted, when, how, and under which solicitation version
  • The archive supports prompt reconstruction without relying on personal drives or memory
  • Lessons learned produce specific controlled improvements rather than blame or unsupported inference

Module provenance

External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.

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.

Free operational lesson

Turn a solicitation into a control sheet

Read once for purpose, again for instructions, and a third time for evaluation criteria. Convert every material requirement into a row with an owner, source, due date, and review status.

01

Verify the authority

Use the official solicitation, amendments, SAM.gov record, and authorized contacts; treat summaries and aggregators as discovery aids only.

02

Control every requirement

Map material instructions, evaluation factors, clauses, deliverables, attachments, and acknowledgments to owners and evidence.

03

Reserve binding decisions

Pricing, representations, certifications, exceptions, signatures, and submission belong to personnel with documented authority.

04

Review against the solicitation

Use stated requirements and evaluation factors rather than taste, generic templates, or unsupported win themes.

05

Preserve the exact record

Retain controlling documents, approvals, final files, receipt, communications, and lessons in the approved system of record.

Unscored self-reflection

Select each module standard that is already consistently true. This is a private reflection—not a test, grade, credential assessment, or claim of competence.

Your choices stay in this browser and are not submitted. Device-only saving is optional in the learning-work panel.

Worked example

Turning an RFP paragraph into a controlled response

A solicitation requires three recent examples, names key personnel, limits the technical volume to fifteen pages, and evaluates technical approach, past performance, and price.

Weak approach

Assign the technical lead to write a persuasive response and ask everyone to send their best project examples by Friday.

Stronger approach

Create separate matrix rows for the three-example requirement, recency definition, required fields, key-person commitments, page limit, each evaluation factor, and price. Assign owners and reviewers, issue a structured data call, verify permissions and relevance, reserve pricing and representations for authorized approval, schedule a page-budget review, and preserve the official solicitation and amendments. Close only after every row points to a response location and approved evidence.

Why it matters: The improved approach converts an informal writing request into traceable controls aligned with how the government says it will evaluate the offer.

03 Control the work

Spot failure.
Measure the system.

Common failure modes

Working from an aggregator summary

Third-party listings may be stale or incomplete. The official notice, solicitation, and amendments control the response.

Treating the matrix as an outline only

A useful matrix also controls evidence, owner, review, status, amendment effects, and the exact response location.

Inflating experience

Misstating role, value, outcome, credential, or availability creates integrity and contracting risk. Use approved source records.

Submitting at the deadline

Portal, registration, file, or network problems can make an otherwise complete offer late. Preserve contingency and verify receipt.

Operating measures

Compliance closure rate

Percentage of material matrix rows with approved response location, evidence, owner, and review status.

Use it to decide: Unclosed mandatory rows block final authorization unless the authorized decision-maker records a lawful resolution.

Evidence acceptance rate

Percentage of data-call items accepted without correction for relevance, accuracy, permission, or completeness.

Use it to decide: Low acceptance triggers narrower requests, better source ownership, or earlier data calls.

Review defect escape rate

Material issues found after the review stage intended to detect them, classified by compliance, evidence, price, and production.

Use it to decide: Escapes drive targeted rubric, reviewer, timing, or document-control improvements.

Submission contingency

Time between verified receipt and the official deadline.

Use it to decide: Repeatedly narrow contingency requires earlier authorization, production, or portal-readiness controls.

04 · Applied case lab · 2026.08.31-practice-3

Practice on a
messy record.

The packet contains contradiction and incomplete evidence on purpose. Each assignment now identifies the exact fictional inputs available to the learner. Complete a bounded starter, mark missing records instead of inventing them, and compare your reasoning with the debrief—not with a pretend single perfect answer.

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.

CB01 · citable versioned case brief

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.

F01 · confirmedThe official submission deadline is September 18 at 2:00 p.m. Eastern.
F02 · confirmedThe base package contains 47 requirements, 12 price line items, and two mandatory representations.
F03 · confirmedAmendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
F04 · confirmedThe internal calendar still displays the original deadline in Mountain Time.
F05 · confirmedThe compliance matrix and current drafts do not reflect the amendment.
F06 · provisionalA proposed subcontract warehouse supplied only an unsigned availability email.
F07 · conflictingFinance totals $486,200 and the required price form totals $468,200.
F08 · conflictingThe resume claims program leadership while approved records show a deputy role for nine months.
F09 · confirmedOne proposed past-performance contact has not provided current reference permission.
F10 · confirmedThe draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
F11 · confirmedThe coordinator lacks authority to sign the offer or certify representations.
F12 · confirmedThe current upload folder is 31 megabytes and includes internal working notes.

The subcontractor expresses availability but has not made an authorized commitment for the revised delivery period.

Judgment required: Decide whether to secure evidence, qualify the claim, redesign the approach, or recommend no-bid before the internal gate.

Do not assume: Do not present informal availability as committed capacity or guaranteed 14-day performance.

The pricing discrepancy may be an omitted freight row, an outdated quantity, or both.

Judgment required: Reconcile the approved pricing source to every required line and identify who may approve the final offer.

Do not assume: Do not choose the lower or higher total without tracing scope, formula, amendment, and authority.

Six module assignments and debriefs

Module 1 · Qualify before bidding

Bounded case starter

Evaluate strategic fit, delivery feasibility, authority, evidence, schedule, and bid cost before committing the team.

Deliverable: A bid/no-bid brief with assumptions, disqualifiers, owners, and a decision gate.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F03, F06, 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.

Workbook plan: 3 authored artifacts with 4 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M01-I01 · case-fact · F01
    The official submission deadline is September 18 at 2:00 p.m. Eastern.
  • M01-I02 · case-fact · F03
    Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
  • M01-I03 · case-fact · F06
    A proposed subcontract warehouse supplied only an unsigned availability email.
  • M01-I04 · case-fact · F07
    Finance totals $486,200 and the required price form totals $468,200.
  • M01-I05 · case-fact · F10
    The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
  • M01-I06 · case-fact · F11
    The coordinator lacks authority to sign the offer or certify representations.
  • M01-I07 · case-fact · F12
    The current upload folder is 31 megabytes and includes internal working notes.
  • M01-B01 · case-brief · 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.
  • M01-S01 · assignment-scope · F01, F03, F06, F07, F10, F11, F12
    Build a starter version of “A bid/no-bid brief with assumptions, disqualifiers, owners, and a decision gate.” 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.

Evidence criteria

  • M01-EC01: Uses the current official solicitation and amendment as controlling sources
  • M01-EC02: Treats warehouse availability and 14-day delivery as unresolved dependencies
  • M01-EC03: Names who may authorize bid, price, representations, and final submission
  • M01-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: A potentially attractive opportunity can still be a no-bid if mandatory capacity or authority cannot be secured. The brief should distinguish a solvable gap from a disqualifying one.

  • Current source package
  • Owned dependency and decision log
Module 2 · Rebuild compliance

Bounded case starter

Create a delta-aware requirement matrix covering instructions, evaluation factors, deliverables, and acknowledgments.

Deliverable: A versioned starter compliance matrix for the requirement categories explicitly described in F02 through F05, plus a gap register for the unsupplied 47-row solicitation record and amendment text.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F02, F03, F04, F05, F07, F10, 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.

Workbook plan: 3 authored artifacts with 56 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M02-I01 · case-fact · F02
    The base package contains 47 requirements, 12 price line items, and two mandatory representations.
  • M02-I02 · case-fact · F03
    Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
  • M02-I03 · case-fact · F04
    The internal calendar still displays the original deadline in Mountain Time.
  • M02-I04 · case-fact · F05
    The compliance matrix and current drafts do not reflect the amendment.
  • M02-I05 · case-fact · F07
    Finance totals $486,200 and the required price form totals $468,200.
  • M02-I06 · case-fact · F10
    The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
  • M02-I07 · case-fact · F12
    The current upload folder is 31 megabytes and includes internal working notes.
  • M02-B01 · case-brief · 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 · assignment-scope · F02, F03, F04, F05, F07, F10, F12
    Build a starter version of “A versioned starter compliance matrix for the requirement categories explicitly described in F02 through F05, plus a gap register for the unsupplied 47-row solicitation record and amendment text.” 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.

Evidence criteria

  • M02-EC01: Cites supplied fact IDs and creates columns for section, page, exact requirement, owner, artifact, and status without inventing missing solicitation text
  • M02-EC02: Flags the known page, file-size, pricing, delivery, and acknowledgment constraints
  • M02-EC03: Explains how superseded requirements would be preserved once the official base document and amendment are available

Debrief lens: A complete matrix does more than count rows. It connects each instruction and evaluation requirement to content, proof, owner, review, and amendment status.

  • Requirement citations
  • Amendment delta trace
Module 3 · Recover the calendar

Bounded case starter

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.

Completion boundary: 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.

Workbook plan: 4 authored artifacts with 7 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M03-I01 · case-fact · F01
    The official submission deadline is September 18 at 2:00 p.m. Eastern.
  • M03-I02 · case-fact · F03
    Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
  • M03-I03 · case-fact · F04
    The internal calendar still displays the original deadline in Mountain Time.
  • M03-I04 · case-fact · F07
    Finance totals $486,200 and the required price form totals $468,200.
  • M03-I05 · case-fact · F10
    The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
  • M03-I06 · case-fact · F11
    The coordinator lacks authority to sign the offer or certify representations.
  • M03-I07 · case-fact · F12
    The current upload folder is 31 megabytes and includes internal working notes.
  • M03-B01 · case-brief · 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 · assignment-scope · 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.

Evidence criteria

  • M03-EC01: Retains the official 2:00 p.m. Eastern deadline and marks the year and date-specific local conversion as required missing evidence
  • M03-EC02: Places price and representation approval before packaging
  • M03-EC03: Assigns an accountable owner and backup to the critical handoffs evidenced by the packet without inventing staff names

Debrief lens: Backward scheduling should protect review and authorization time, not merely fill every hour with drafting. Time-zone and portal constraints belong in the critical path.

  • Verified deadline conversion
  • Dependency-aware calendar
Module 4 · Repair evidence claims

Bounded case starter

Validate resume, past performance, subcontractor, delivery, and price-support statements.

Deliverable: An evidence-ledger starter and claim-correction plan for the resume, warehouse, pricing, delivery, and past-performance issues; source excerpts and permissions not supplied remain explicit gaps.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F03, F06, F07, F08, F09, 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.

Workbook plan: 3 authored artifacts with 6 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M04-I01 · case-fact · F03
    Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
  • M04-I02 · case-fact · F06
    A proposed subcontract warehouse supplied only an unsigned availability email.
  • M04-I03 · case-fact · F07
    Finance totals $486,200 and the required price form totals $468,200.
  • M04-I04 · case-fact · F08
    The resume claims program leadership while approved records show a deputy role for nine months.
  • M04-I05 · case-fact · F09
    One proposed past-performance contact has not provided current reference permission.
  • M04-B01 · case-brief · 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.
  • M04-S01 · assignment-scope · F03, F06, F07, F08, F09
    Build a starter version of “An evidence-ledger starter and claim-correction plan for the resume, warehouse, pricing, delivery, and past-performance issues; source excerpts and permissions not supplied remain explicit gaps.” 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.

Evidence criteria

  • M04-EC01: Uses F03, F06, F07, F08, and F09 to separate known claim defects from missing source records
  • M04-EC02: Provides fields for role, dates, value, scope, delivery, price, and permission without inventing the unavailable underlying documents
  • M04-EC03: Routes each corrected excerpt and commitment claim to the authorized source owner before use

Debrief lens: Past-performance and resume claims should describe the documented role accurately. A narrower true claim is stronger than an inflated one that creates representation risk.

  • Approved source records
  • Permission and claim ledger
Module 5 · Run controlled reviews

Bounded case starter

Plan compliance, content, price, and final-production reviews with finding closure.

Deliverable: A review plan and finding log showing retest and authorized disposition.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F03, F05, 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.

Workbook plan: 3 authored artifacts with 5 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M05-I01 · case-fact · F03
    Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
  • M05-I02 · case-fact · F05
    The compliance matrix and current drafts do not reflect the amendment.
  • M05-I03 · case-fact · F07
    Finance totals $486,200 and the required price form totals $468,200.
  • M05-I04 · case-fact · F10
    The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
  • M05-I05 · case-fact · F11
    The coordinator lacks authority to sign the offer or certify representations.
  • M05-I06 · case-fact · F12
    The current upload folder is 31 megabytes and includes internal working notes.
  • M05-B01 · case-brief · 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.
  • M05-S01 · assignment-scope · F03, F05, F07, F10, F11, F12
    Build a starter version of “A review plan and finding log showing retest and authorized disposition.” 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.

Evidence criteria

  • M05-EC01: Defines reviewer purpose, entry criteria, severity, owner, and due time
  • M05-EC02: Treats unresolved compliance and price gaps as release blockers
  • M05-EC03: Uses version control so reviewers assess the correct package
  • M05-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: Review findings need severity, ownership, disposition, and retest. A review meeting without closure evidence is activity, not control.

  • Requirement-linked findings
  • Verified correction status
Module 6 · Prove submission readiness

Bounded case starter

Design a clean-package and portal-submission simulation without uploading, signing, hashing, timestamping, or claiming receipt.

Deliverable: A submission-readiness checklist, package-manifest starter, mock-receipt template, and lessons-learned template with execution evidence pending.

Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, 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.

Workbook plan: 4 authored artifacts with 7 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.

Review the module lesson →

Provided inputs

  • M06-I01 · case-fact · F01
    The official submission deadline is September 18 at 2:00 p.m. Eastern.
  • M06-I02 · case-fact · F02
    The base package contains 47 requirements, 12 price line items, and two mandatory representations.
  • M06-I03 · case-fact · F03
    Amendment one changes delivery to 14 days, changes a quantity, and requires acknowledgment.
  • M06-I04 · case-fact · F10
    The draft technical volume exceeds its stated page limit by 1.5 pages before final graphics.
  • M06-I05 · case-fact · F11
    The coordinator lacks authority to sign the offer or certify representations.
  • M06-I06 · case-fact · F12
    The current upload folder is 31 megabytes and includes internal working notes.
  • M06-B01 · case-brief · 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.
  • M06-S01 · assignment-scope · F01, F02, F03, F10, F11, F12
    Build a starter version of “A submission-readiness checklist, package-manifest starter, mock-receipt template, and lessons-learned template with execution evidence pending.” 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.

Evidence criteria

  • M06-EC01: Lists the required-file and portal-size controls supported by F10 and F12 while leaving exact final files pending
  • M06-EC02: Requires authorized signature, representations, and amendment acknowledgment without recording completion
  • M06-EC03: Provides fields for a future package hash, portal timestamp, receipt, and retained version but does not fabricate those results
  • M06-EC04: Cites the supplied input IDs for material statements and marks omitted operational records or results “not supplied” rather than fabricating them

Debrief lens: The final proof is the exact authorized package and system confirmation. Local files and calendar completion do not establish timely receipt by the designated system.

  • Final package manifest
  • Timestamped mock acceptance record

Self-review standard

Inspect evidence, reasoning, completeness, boundaries, and traceability.

There is no single universal bid decision. A defensible recommendation shows how official requirements, evidence gaps, schedule, authority, and delivery risk affect the choice. The downloadable rubric is formative guidance only—not a grade, verified completion, credential assessment, or professional approval.

Questions about solicitation meaning, representations, eligibility, protests, organizational conflicts, or contract terms

Route to: Authorized contracts leader and qualified government-contracts counsel as appropriate

Learner boundary: The coordinator tracks requirements but does not issue legal interpretations or certify eligibility.

Final pricing, cost treatment, offer signature, certifications, or binding subcontract commitments

Route to: Authorized company officer, pricing or accounting reviewer, and authorized subcontract representatives

Learner boundary: Preparation does not create authority to bind any party or certify facts.

05 Editable working tool

Use the template.
Inspect the example.

Create one row per material requirement. Use the official reference, point to the exact response location, assign one accountable owner, link approved evidence, and keep review status current after every amendment. Add as many rows as needed, export a CSV, or print only this tool. Entries are not transmitted. They last only in this tab unless you opt into device-only saving in the learning-work panel. No account or cross-device sync is provided.

Editable Government Proposal Coordination public-foundation worksheet
RequirementResponse locationOwnerEvidence sourceReview status

Completed example

Requirement
Provide three recent and relevant past-performance examples with customer contact information.
Response location
Technical Volume, Section 4.2, pages 10 to 12; forms in Attachment C.
Owner
Past-performance lead; proposal manager accountable for closure.
Evidence source
Approved contract summaries, performance records, and current customer-reference permissions.
Review status
Two accepted; third example awaiting recency and contact-permission confirmation.

Data boundary: Work only in an approved system. Do not place passwords, payment-card data, government identifiers, health information, export-controlled material, client secrets, or unpublished invention details in this public worksheet.

Practice one module.
Get useful feedback now.

Each two-question check works independently. Review any answered question immediately; you do not need to finish all twelve. Feedback is formative, not a verified grade or credential.

Module 1 · 2-item formative check

Opportunity qualification

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 1 · knowledgeWhich source controls the requirements for a current federal proposal response?
Question 2 of 2 · MODULE 1 · scenarioWhich bid/no-bid update lets Canyon Response's authorized owner decide without overstating proposal readiness?

Answer either question to review its reasoning.

Module 2 · 2-item formative check

Solicitation reading and compliance matrix

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 · knowledgeWhat should the proposal team do when an amendment changes a requirement?
Question 2 of 2 · MODULE 2 · scenarioWhich Module 2 control best addresses the risk that Canyon Response submits against superseded requirements?

Answer either question to review its reasoning.

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.

Module 4 · 2-item formative check

Evidence, past performance, and resumes

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 4 · knowledgeWhich past-performance description follows an evidence-controlled and permission-aware proposal workflow?
Question 2 of 2 · MODULE 4 · scenarioWhich sequence responsibly repairs Canyon Response's resume, warehouse, price, delivery, and reference claims?

Answer either question to review its reasoning.

Module 5 · 2-item formative check

Color-team review and document control

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 5 · knowledgeWhat should a reviewer record after finding a material proposal compliance gap?
Question 2 of 2 · MODULE 5 · scenarioOne review-plan criterion is met, but unresolved compliance and price gaps are not release blockers. What should the reviewer decide?

Answer either question to review its reasoning.

Module 6 · 2-item formative check

Submission, confirmation, and lessons learned

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 6 · knowledgeWhich evidence most directly proves that the exact proposal package was submitted on time?
Question 2 of 2 · MODULE 6 · scenarioWhich finding creates a verifiable correction path for Canyon Response's incomplete submission-readiness package?

Answer either question to review its reasoning.

07 Sources and handoffs

Verify the standard.
Know when to escalate.

Module provenance distinguishes external authorities, legal-status evidence, and Wealth Synergy internal operating standards. Requirements change; verify current source text and obtain qualified advice when a decision carries legal, financial, technical, employment, safety, or regulatory consequences.

sam-entity-registration · Official guidance

SAM.gov: Entity Registration

Official source for federal entity registration, Unique Entity ID information, and the registration checklist.

Open reviewed external source ↗

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-15-304 · Current codified text

FAR 15.304: Evaluation factors and significant subfactors

Primary rule explaining that evaluation factors and their importance are stated in the solicitation.

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 ↗

sba-get-started-contracting · Official guidance

SBA: Get started with contracting

Current official small-business guidance on federal-contracting readiness, registrations, market research, compliance, and participation requirements.

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

Future facilitated pathway · not open

Practice with feedback.
Finish with evidence.

The public case lab is available now. A future facilitated cohort may add assignments, feedback, and human capstone review only after a named qualified facilitator and reviewer, schedule, rubric, privacy controls, support, price, refund terms, and delivery terms are published in writing. No enrollment or payment is accepted here.

Clear boundaries.

Course material supports professional development. It does not replace legal, tax, accounting, cybersecurity, engineering, regulatory, employment, translation, or other qualified professional advice where that expertise is required.

The public knowledge check and portal review markers are learning aids only. They do not award a credential. Pilot curriculum and credential assessment are in quality review; Foundry Academy is not currently representing these pages as accredited instruction or an automatic path to a certificate.

Participation does not guarantee employment, client work, funding, licensure, certification by a public authority, or any business outcome.

Use the public foundation

Read. Practice.
Inspect your evidence.

All public materials and case files are available without enrollment. A fit conversation is non-binding and does not reserve a place in a future pilot.

Ask about this track