The model preserves the prime's competitive advantage by making all deliverables appear authored and owned by the prime, not a subcontractor. That reduces the risk of evaluator concern or disqualification tied to subcontractor visibility. It also protects proposal integrity and the confidentiality of internal analyses and decision trails, which SLED evaluators and procurement rules treat as important.

Common failures include metadata leakage, formatting or voice inconsistencies, and accidental client email visibility. Each of these can reveal offshore involvement and trigger compliance reviews. Washington DES, California CDT, Texas DIR, and New York OGS have evaluation expectations or rules that make single, unified authorship and strict subcontractor invisibility important in practice.

1. Treat every deliverable as prime-branded. Use only prime templates, replicate the prime's tone and terminology, and follow formatting rules so the work reads as if the prime produced it.
2. Control attribution and metadata. Remove author fields, comments, tracked changes, device signatures, and any hidden fields before delivery. Export or save clean copies and validate them with prime tools when available.
3. Route all communication and uploads through the prime. Do not forward files to clients or upload to client portals. Deliver drafts only to the designated prime contacts.
4. Keep internal work internal. Draft matrices, analyses, and reviewer notes must never be included in final, evaluator-facing documents.

Scenario: A draft PDF retains author metadata showing an offshore username right before submission. Immediate steps: stop the upload, create a new clean copy, clear document properties and hidden fields, reexport to PDF using prime settings, and run any prime metadata scans. Then hand the clean file to the prime for final submission. That sequence follows standard metadata cleaning and attribution control steps used for SLED proposals.

Start by adopting the prime s templates and style rules as the working format. Match vocabulary, sentence rhythm, and structural habits from prior prime materials so writing feels native to the prime. At the document level, remove any author identifiers, accept or reject tracked changes, delete every comment, and inspect headers, footers, and embedded objects for hidden fields. Clear document properties such as author, company, device ID, and revision history, then save a fresh copy before export. When producing PDFs, check and clear PDF metadata and embedded comments, and ensure file names follow the prime s naming conventions. These specific steps reflect established guidance on attribution control and metadata cleaning used for SLED proposals.

Route every deliverable only through the prime s internal proposal contacts, never directly to client portals or evaluators. Use prime approved file sharing and scanning tools so the prime can validate metadata and formatting before submission. Do not include any statement, chart, resume, past performance entry, or org diagram that refers to offshore support. These limits reduce the chance that routine file handling will reveal a subcontractor role.

1. Copy content into the current prime template. 2. Accept all tracked changes and delete all comments, including resolved ones. 3. Open File, Info, and clear Author, Company, and other properties. 4. Inspect headers, footers, and any embedded Excel or image objects for hidden text or source metadata. 5. Save as a new clean DOCX file, then export to PDF. 6. Open the PDF properties, remove any author or application fields, and run the prime s metadata scanner if available. 7. Name the file per prime conventions and deliver it only to the prime s proposal manager for final packaging. Each step mirrors the recommended metadata cleaning and attribution controls used in SLED proposals.

• Use prime template and approved fonts and styles. - Accept tracked changes and delete all comments. - Clear document properties and hidden fields. - Export to PDF and scrub PDF metadata. - Follow prime file naming rules. - Send only to the prime s designated contact, using approved platforms. - Confirm the prime has scanned and approved the final file.

Use only the prime's approved template, not an offshore or ad hoc layout. Never introduce local formatting or stylistic cues. This rule is a first line of defense against detection and noncompliance.

Obtain the current approved template from the prime, and confirm the approved version number or date with the proposal manager. Create a new document from the prime template. Do not paste content into an offshore file and try to retrofit the template there.

Match fonts, colors, header and footer layout, logo placement, and approved section order exactly. Copy structural habits such as bullet styles and transition phrases when present. Replace any local styles with the prime's style definitions before editing content further.

Save a clean copy, export to PDF using the prime's recommended settings, then run any prime-supplied metadata scanner or validator before handing the file to the prime's proposal lead.

Accept or reject every tracked change, and delete all comments. Hidden markups can reveal authors and review history, so resolve them before further cleaning. A metadata cleaning checklist used for masked operations requires these steps as core controls.

Export to PDF after completing the Office cleanup. PDFs can inherit Office metadata if the source file still contains it. Use Acrobat Pro tools to remove metadata, hidden text, and embedded comments.

Strip EXIF and file-level metadata from photos. Use an image editor or a metadata stripper to remove camera make, model, GPS, and user labels. When possible, re-export images from the original source with metadata removed.

Remove version history and editor traces. For Google Docs, make a copy and then download the copy as the delivery format so prior version history is not transferred. Avoid client-facing sharing from offshore accounts.

The prime’s proposal manager, capture lead, or an assigned prime liaison handles all client-facing communication. All inbound requests, clarifications, and meeting invitations must be forwarded to those prime contacts immediately. This keeps the prime as the single visible author and accountability holder.

Do not email or message any client addresses directly. Do not accept calendar invites that list offshore participants in visible attendee lists. Do not log into or upload files to client portals. These behaviors create visible traces that can reveal offshore involvement.

1. Pause and confirm. If a client-sent message reaches an offshore inbox, stop and notify the prime contact. Do not respond from the offshore account. 2) Clarify through the prime. Ask the prime contact whether they want a draft response, a technical note, or a redlined document. Provide only internal deliverables unless the prime explicitly instructs otherwise. 3) Prepare an internal deliverable. Create a prime-branded draft, or a concise technical brief, with all metadata cleaned and all internal notes removed. Label drafts as internal-only in your records. 4) Submit to the prime. Deliver the file and a short summary or talking points to the prime contact. Do not forward or copy the client. 5) Log the handoff. Record the request, the file(s) delivered to the prime, and the timestamp in your internal tracker to support audits and follow up.

Do not upload or sign into client portals. The prime completes all submissions and uploads. Ensure file names, PDF properties, and metadata conform to prime standards before delivering to the prime so the prime can submit without modification.

Confirm recipient is a prime contact. - Remove all author metadata and comments. - Use prime-branded templates and wording. - Supply a short summary or script for the prime to use. - Record the handoff in the tracker. Each item supports attribution control and compliance.

• Look for contractions and pronouns. A formal voice avoids contractions and favors third person, while a conversational voice uses we, you, and contractions.
• Check sentence length and punctuation. Formal prose leans toward longer sentences and more complex punctuation, conversational prose uses short sentences and straightforward punctuation.
• Note hedging and modal verbs. Formal voice often uses precise qualifiers (shall, must), conversational voice uses softer modality (can, might).

• Apply the same tone across all evaluator-facing sections, including executive summaries, compliance matrices, and resumes. SLED evaluators expect consistent voice throughout a proposal, so tone shifts increase visibility risk.
• When a document mixes audiences, set a primary tone and make only controlled adjustments for audience-specific content. Use the prime’s past deliverables as the benchmark for what counts as “on tone”.

Small, repeatable edits keep work efficient and safe.

• Replace or retain contractions to match formality. Example: change "we're" to "we are" for formal tone.
• Swap pronouns for the prime’s preference. Example: change "the team" to "the prime" or "we" depending on the prime’s habit.
• Adjust modality and verbs. Use "must" or "shall" to raise formality, use "can" or "will" to lower it.
• Trim or lengthen sentences to match average sentence length from the prime’s samples.
• Mirror paragraph openings and closings. If the prime favors direct calls to action, keep those; if they prefer descriptive signposts, adopt that pattern.

• Compare the draft to two recent prime-authored documents for contractions, pronoun use, and average sentence length. Use those documents as the reference benchmark.
• Run a short read-aloud test. If cadence diverges from the prime’s samples, make small sentence-level edits.
• Verify that headings, bullets, and callouts match the prime’s usual phrasing and formality.

• Pull two recent prime proposals, note three repeated tone markers, and list them at the top of your draft.
• Apply the micro-edit moves in one primary section, then have an internal reviewer compare it to the prime samples.
• Run metadata and attribution checks after tone edits to ensure no draft markers reveal offshore involvement.

Use only prime-approved platforms, do not create or send external file-sharing links, and never upload directly to client portals; these requirements reflect the Masked Relationship Model expectations for attribution control and file handling. For any approved platform, confirm the prime specifies the exact permission settings, such as view-only access, disabled download if required, link expiration, and blocked re-sharing.

1. Prepare a clean copy according to the prime’s metadata checklist, then export or save a new file to remove hidden fields and history. 2. Upload the clean copy only to the prime’s designated workspace or transfer mechanism. 3. Apply the prime’s permission template: restrict editing to named prime reviewers, set link expiry if applicable, and turn off external sharing. 4. Notify the prime through the agreed internal channel that the file is ready, include the exact file name and version, and do not send the link to any client address. These steps align with guidance that cloud platforms can reveal edit histories and incorrect upload permissions create visibility risk.

• A list of approved platforms and required permission templates. - A standard file naming convention to use before upload. - A validation check or tool the prime will run to confirm no residual metadata or version history. - A single authorized recipient at the prime for all uploads or links, with documented confirmation of receipt.

• Confirm platform is prime-approved. - Confirm clean copy and metadata validation. - Apply prime permission template and expiration. - Use prime naming and versioning, confirm recipient identity. - Do not upload to client portals or forward external links.

1. Prepare a working copy, then create a clean copy for delivery. Work from a draft, do the cleaning steps on a separate saved file, and keep the draft under internal control.

2. Accept or reject all tracked changes, and delete comments. Ensure no markup or resolved comments remain in the file, because comments often contain author names or notes reviewers could trace back to offshore contributors.

3. Remove document properties and personal information in Office files. Use File > Info > Check for Issues > Inspect Document, run the inspection, and remove all document properties and personal information found. Also check Properties > Advanced Properties and clear Author, Company, and other fields.

4. Inspect hidden content and embedded objects. Check headers, footers, watermarks, custom XML parts, embedded spreadsheets or slides, hidden text, and linked files. Hidden fields and embedded objects can contain author or device metadata.

6. Final save and validate. Save the cleaned file as a new filename that follows the prime naming convention. Run any prime-provided metadata scanner or a trusted metadata inspection tool to confirm the file is clean before handing it to the prime for submission.

Prime templates, style names, and visual samples are the reference. Match fonts, font sizes, heading hierarchy, bullet and numbering styles, table styles, margins, header and footer layout, color swatches, and logo placement. The Masked Relationship Model requires using only the prime branded templates and avoiding offshore templates or stylistic cues. Formatting differences such as fonts, spacing, headers, or colors are common detection points.

1. Start from the prime template. Open the prime file and create a new document from that template. Never paste full content into a generic local template. 2. Normalize imported text. When bringing content from other files, use paste special or paste as plain text. Then reapply the prime styles. 3. Clear direct formatting. In Microsoft Word, select the affected text and press Ctrl+Space to remove character-level formatting, and Ctrl+Q to remove paragraph-level overrides. Use the Styles pane to assign the correct Heading and Body styles. 4. Standardize fonts and sizes globally. Use the Replace Font or Design > Fonts tools to ensure only approved fonts appear.

• Document was created from the prime template. - Styles panel shows only prime-approved style names in use. - No manual font overrides remain (Ctrl+Space/Ctrl+Q applied). - Bullet and numbering appearance matches sample. - Tables use prime table styles and captions match format. - Headers, footers, page numbers, and logos match the prime sample. - File saved with prime filename convention and exported via prime method. - Final visual check against a prime sample completed, and prime reviewer approved.

• Build a short style-mapping guide that lists prime style names and the exact font/size for each. Keep it beside your workstation. - Create a one-click macro or a small script that applies the prime’s core styles to a selected document, then run it before handing the file to the prime. - Keep a “visual benchmark” PDF of the prime deliverable for quick side-by-side checks.

• Accept or reject all tracked changes, then save a new copy. The checklist used for masked delivery lists accepting or rejecting tracked changes as a required step.
• Delete every comment, including resolved or hidden comments. Even resolved comments can contain names or notes that reveal contributors, so remove them before export.
• Clear document properties and metadata fields. Remove author, company, last saved by, creation and modification timestamps, and any device or application identifiers before creating the PDF.
• Inspect headers, footers, embedded objects, and any attached files. Hidden fields and embedded content often carry metadata that survives conversion.
• Export or save as a fresh PDF and then resave as a clean copy. Creating a new file helps drop residual internal data that can remain in iterative saves.
• Validate with the prime's metadata scan or quality checklist. Many primes run an automated scan or a manual check to ensure no attribution traces remain.

Scenario: You finish a section in an editable document and must deliver a submission-ready PDF. Steps to apply: accept all changes, delete all comments, run a metadata clear on document properties, save a new file, export to PDF, then run the prime's verification tool or open the PDF properties to confirm author and company fields are blank. The course checklist identifies PDF metadata and hidden comments as specific submission-stage risks that require these steps.

• Confirm file name conforms to prime naming conventions and contains no offshore identifiers.
• Do not upload materials to client portals from offshore accounts or devices. Incorrect upload permissions can reveal version history or user accounts.
• Keep an internal audit note with the clean-copy filename, who ran the verification, and the verification method used. This supports traceability inside the prime relationship.

• Clean metadata is a required control, not an optional tidy up. The Masked Relationship Model treats metadata leakage as one of the most common visibility failures, so treat these steps as mandatory before any deliverable leaves offshore control.
• If unsure, escalate to the prime's proposal manager for a final scan. That protects both the prime and the offshore team.

Before handing a PDF to the prime, answer these three quick questions: Have all edits and comments been removed? Are author and company fields blank? Has the prime's metadata verification been completed and recorded?

Primes own emails, meetings, and clarifying questions. Action for RSPs: treat all questions as routed through the prime, and supply ready-to-send text snippets, Q and A bullets, and suggested talking points that match the prime tone. Keep each item short and labeled for the prime to paste.

Primes enforce voice, terminology, and formatting. Action for RSPs: use the prime master template, mirror sample language from past proposals, and produce copy that needs minimal editing to match sentence rhythm and vocabulary.

Primes will paste, reformat, or rewrite content to create a single authorial voice. Action for RSPs: avoid section-level stylistic flourishes, use neutral transitions, and keep sentences modular so reviewers can combine text easily.

Do deliver prime-branded text, not 'offshore-style' copy. Do remove all metadata, comments, and tracked changes before handoff. Do follow the prime's file naming and template rules exactly. Do include a one-line change log with each deliverable. Dont contact clients or appear in portal activity. Dont use offshore templates or visible formatting cues.