合規矩陣

Tender requirements are not held in one place. They are scattered across the instructions to bidders, the evaluation criteria, the specification or statement of work, the draft contract terms, the forms and declarations, and the annexes — often in different documents written by different people, sometimes contradicting each other. A compliance matrix is the single register that pulls them together and proves that each one has been addressed.

招標要求不會集中於單一處。它們散落在投標人須知、評估準則、規格或工作說明書、草案合約條款、表格與聲明以及附件中——常常位於由不同人撰寫的不同文件，有時彼此互相矛盾。合規矩陣是一個單一的登記冊，將這些要求彙集起來，並證明每一項皆已被處理。

What the register contains

One row per requirement, with at minimum: a requirement number you assign; the source document and the clause, section or page it came from; the requirement text, quoted rather than paraphrased; whether it is mandatory or desirable and its weighting if scored; the exact location in your response where it is answered, down to the section; the person who owns that answer; the evidence or attachment it depends on; and a status.

一列代表一項要求，至少應包含：你指定的要求編號；來源文件及其條款、章節或頁碼；要求原文（應引用原文而非意譯）；該要求為強制性或可取項目，以及若計分則之權重；在你回應中確切回覆該要求的位置，精確到章節；負責該回覆的人；所依據之證據或附件；以及一個狀態欄位。

Two structural points matter. Quote the requirement verbatim, because paraphrase is where compliance quietly drifts. And record the response location precisely enough that a reviewer, or an evaluator if the matrix is submitted, can open the page and find the answer.

有兩點結構性要點很重要。必須逐字引用要求，因為意譯是合規性悄然偏移的所在。並且應精確記錄回應位置，足以讓審查者（或若矩陣一併提交則評估者）能直接開到該頁找到答案。

Why solicitation structure makes this necessary

The formal architecture of a solicitation splits instructions from evaluation. In US federal procurement, FAR 15.204-5(b) provides that Section L of the uniform contract format carries the "solicitation provisions and other information and instructions not required elsewhere to guide offerors or respondents in preparing proposals", while FAR 15.204-5(c) provides that Section M is to "identify all significant factors and any significant subfactors that will be considered in awarding the contract and their relative importance".

招標的正式架構將指示與評估分開。在美國聯邦採購中，FAR 15.204-5(b) 規定統一合約格式的 Section L 載有「招標條款及其他資訊與指示（供投標人或應答人在準備提案時之參考）」（"solicitation provisions and other information and instructions not required elsewhere to guide offerors or respondents in preparing proposals"）；而 FAR 15.204-5(c) 規定 Section M 則用以「識別在授予合約時將被考量的所有重要因素及任何重要子因素及其相對重要性」（"identify all significant factors and any significant subfactors that will be considered in awarding the contract and their relative importance"）。

Those two sections do different jobs and both bind you. Section L, or its equivalent in any other regime, dictates the structure, format, page limits and content of your submission. Section M dictates where the marks are. A response that follows the instructions but ignores the weightings is compliant and unpersuasive; a response that chases the weightings but breaks the instructions may not be read at all. The matrix has to carry both, which is why mature matrices have a column for the instruction and a column for the criterion.

這兩個部分分屬不同職能，且兩者均具約束力。Section L 或其他制度中的等值規定，指示你提交文件的結構、格式、頁數限制與內容；Section M 則指示評分重點。遵守指示但忽視權重的回應，雖合規卻不具說服力；追逐權重但違反指示的回應，可能根本不會被閱覽。矩陣必須同時承載兩者，因此成熟的矩陣會有一欄記錄指示（instruction）及一欄記錄評分準則（criterion）。

Why non-compliance loses bids that were otherwise winning

The mechanisms are unglamorous and mostly final.

造成失標的機制通常是行政性的，且多數具有最終性。

A submission arriving after the deadline is generally out: under FAR 52.215-1(c)(3), a proposal received at the designated Government office after the exact time specified will generally not be considered, subject to narrow exceptions. The same principle operates on electronic portals everywhere, where the clock is the portal's, not yours.

逾期送達的投標通常會被排除：依 FAR 52.215-1(c)(3)，在指定政府辦公室於明確規定時間後收到的提案，一般不會被列入考慮（僅在極狹窄之例外情形下另當別論）。電子平台亦同樣適用此原則——平台的時鐘為準，而非你的時鐘。

There may be no chance to fix an omission. FAR 52.215-1(f)(4) states the Government intends to evaluate proposals and award a contract without discussions with offerors, other than clarifications. And FAR 52.215-1(f)(2) preserves the right to reject any or all proposals where that is in the Government's interest.

遺漏可能無法補救。FAR 52.215-1(f)(4) 指出政府擬在不與投標人進行討論（僅允許澄清）的情況下評估提案並授予合約；而 FAR 52.215-1(f)(2) 保留政府在其利益所及時拒絕任何或全部提案的權利。

Missing a mandatory document, a signature, a declaration or a certification typically scores nothing on the affected item rather than triggering a phone call. Exceeding a page or word limit usually means the excess is not read, which removes your evidence rather than your claims. And an unanswered criterion is visible afterwards: under the UK Procurement Act 2023, suppliers that submitted an assessed tender receive an assessment summary under section 50 explaining how their tender was assessed against each award criterion — where the zero is written down in the buyer's own words.

遺失強制性文件、簽章、聲明或證明，通常導致受影響項目得分為零，而非觸發電話聯繫。超出頁數或字數限制通常表示超出的部分不會被閱讀，這會移除你的證據而非僅僅移除你的主張。而未回覆的評分準則事後亦會顯而易見：根據 UK Procurement Act 2023，提交經評估之標案的供應商會依第 50 條收到一份評估摘要，說明其標案如何依每個授標準則被評分——零分會以採購方自己的文字被寫下來。

None of these are sophisticated failures. They are administrative, and they are entirely preventable.

上述都不是複雜的失誤，而是行政性錯誤，且完全可以預防。

What to do about it

Build the matrix on the day the documents are released, before anyone writes prose. Have two people extract requirements independently from the full document set, including the draft contract and the annexes, then reconcile the two lists — the delta between them is a reliable measure of how easy this tender is to misread. Search for the obligation words in whatever language the tender is written in, but do not rely on keyword search alone: requirements hide in tables, drawings, appendices and the forms themselves.

在文件發布當日即建立矩陣，且在任何人開始撰寫文字之前完成。讓兩人獨立地從完整文件集（包括草案合約與附件）中擷取要求，然後對照並調節兩份清單——兩者之間的差異是一項可靠指標，可顯示此招標案有多容易被誤讀。以招標語言搜尋義務性詞彙，但不要僅仰賴關鍵字搜尋：要求往往藏於表格、圖面、附錄與表單本身。

Freeze the matrix as the outline. Every response section should exist because a requirement demanded it, and every requirement should point at a section. At each review, check the matrix before checking the writing: an argument that scores well in a section nobody asked for is wasted work.

將矩陣定案為大綱。每一個回應章節應當是因為某項要求而存在，每一項要求也應指向一個章節。在每次審查時，先核對矩陣再檢視文字：在無人要求的章節中得分良好的論述，屬於徒勞工作。

Where the instructions ask for a cross-reference matrix as part of the submission, treat it as a scored document and make it accurate, because an evaluator who follows one of its pointers and finds nothing will trust the rest of it less. Where it is not asked for, keep it internal but keep it current.

若指示要求將交叉參照矩陣作為提交的一部分，應將其視為計分文件並確保其準確性；因為若評估者依其某一指引開啟卻未見內容，將會降低對整份矩陣的信任。若未被要求提交，則將其作為內部文件使用，並保持最新狀態。

Finally, run the matrix once more against the final compiled document, not against the drafts, and submit with time in hand. A large upload failing at the deadline is a compliance failure like any other.

最後，將矩陣再一次與最終彙整後的文件比對（非草稿），並預留足夠時間提交。於截止時失敗的大型上傳，與其他合規失誤無異。

A note on the term

The compliance matrix is professional convention rather than a standardised artefact — its columns and its name vary between organisations and between buyers. The consequences it exists to prevent are not convention; they are written into the solicitation rules cited above.

「合規矩陣」屬於職業慣例，而非標準化的產物——其欄位與名稱會因組織或採購方而異。其存在所要防止的後果並非慣例可言；那些後果已被寫入上述所引用的招標規則中。

相關術語

• 色彩團隊審查（藍、粉、紅、綠、金、白）
• 勝出主題
• 投標／不投決策
• 獲標價格（PTW）

免費試用開始 — 7 天