Views:

In this article: Requirements for all Microsoft QTM Voucher Programs | Guidelines for preparing a SOW and POE | Document preparation and Voucher Redemption | Partner and Customer contacts and signature requirements 

 

Requirements for all Microsoft Quick to Market (QTM) Voucher Programs 

  • Submission and approval of a Statement of Work (SOW) prepared on a Microsoft template before any voucher funded work can be delivered. 

  • A Proof of Execution (POE) document confirming the completion and delivery of approved SOW activities is required before a voucher expires. 

  • See the program-specific Terms and Conditions along with links to each relevant program SOW and POE templates in this article: FY26 Quick to Market Program Information. 


Guidelines for preparing a Statement of Work and Proof of Execution 

Following are instructions that align with QTM program requirements to prepare Statement of Work and Proof of Execution documents. Applying this guidance can help ensure a single and efficient signing experience for customers, and streamlined, efficient processing of documents.
 

Document preparation and Voucher Redemption

  • Ensure your customer has provided you with a copy of their Voucher email.

  • Use the correct templates for Statement of Work (SOW) and Proof of Execution (POE) documentation.

  • Do not modify program templates. 

  • If a template download contains multiple versions, use the version that corresponds to the Program Year indicated on the customer Voucher email.

  • Voucher expiration date is the deadline by which the customer project should be completed, and signed POE submitted.

  • Do not submit your POE until your SOW has been approved. POE must match approved SOW.

  • Refer to a program’s SOW template and Terms and Conditions for eligible workloads.

  • Upload completed SOW and POE templates to the QTM Voucher Redemptions page when submitting Voucher Redemption Requests.

     

Partner and Customer contacts and signature requirements

  • Provide complete information requested, including primary Customer Tenant ID on which work will be performed.

  • Contact details provided must match document signatory. It is not necessary for the same person to sign the SOW and POE documents.

  • Ensure customers are aware of signing deadlines and are available for signature to meet program deadlines.

  • SOW and POE documents must be signed and dated by partner and customer. 
    Note: Digital documentation is preferred. Scanned/uploaded documentation is not recommended due to readability issues and may be returned for revision.

     

    • If using digital signatures, an audit trail must be provided and included with the signed SOW or POE. Electronic signatures without an audit trail will not be accepted. 

    • Copy/paste physical signatures will not be accepted.

       

SOW preparation guidance best practices

  • Complete document in English. Add machine translation for Scope of Work details, if needed.

  • For each eligible workload to be deployed or activity to be performed, provide a high-level bullet list of primary activities related to each item selected.  A shorter, generalized list of deliverables is preferable to an exhaustive list.

  • Pre-signature review available: Quickly learn if your SOW is ready for signatures and official submission by using AI-assisted QTM Document Review in the FPC Portal currently available for the following programs:  ME3/ME5 Migration + Deployment (MWDO) and M65 Copilot Deployment Voucher. 

  • Follow the example format below when completing your SOW. 
    Best practice tip: Only include high-level details and deliverables.

 

 

 

 

 

 

 

 

 

Keywords: Scope of Work, Proof of Execution, SOW, POE, Service Agreement Verification Forms