K
keturah.agent
All build guides
L1-A02

NOC Submission Validator

Authority Compliance · Submission Readiness

Build “NOC Submission Validator” in Microsoft Copilot Studio (Cowork)

Seven steps from a blank agent to a published Copilot. Copy the prompt, starters, and manifest below as you go.

  1. 1

    Open Copilot Studio

    Sign in to Microsoft Copilot Studio (copilotstudio.microsoft.com) with your work account. Choose the environment where the agent should live, then select Create → New agent.

  2. 2

    Name & describe the agent

    Set the name to "NOC Submission Validator" and paste this description: "Checks authority NOC packages for completeness before submission." This is what teammates see when they pick the agent in Microsoft 365 Copilot.

  3. 3

    Paste the instructions (system prompt)

    Open the Instructions field and paste the generated system prompt from the panel below. It defines the agent's role, capabilities, and guardrails. Tune the wording to your team's tone if needed.

  4. 4

    Add conversation starters

    Under Conversation starters, add the suggested prompts below. These give users a one-click way to understand what the agent can do.

  5. 5

    Connect knowledge & actions

    Add the data sources this agent reads from (SharePoint document libraries, Dataverse tables, or a REST/HTTP action to your own API). Map them to its skills: document checklist validation; pre-submission readiness gate; authority requirement matching; rejection-risk scoring. Keep connectors scoped to least-privilege.

  6. 6

    Test in the Cowork pane

    Use the Test pane to run the conversation starters and a few real questions. Confirm the agent asks for missing inputs, prioritises correctly, and cites its source. Refine the instructions until the behaviour is right.

  7. 7

    Publish to Microsoft 365 Copilot

    Select Publish, then choose the channels (Microsoft 365 Copilot, Teams). Submit for admin approval if your tenant requires it. Once approved, the agent appears in Copilot for the people you shared it with.

Step 3 — System prompt (instructions)

instructions.txt
You are the NOC Submission Validator, a Authority Compliance assistant.

Purpose: Validates the completeness of authority No-Objection-Certificate submission packages before they are sent, matching document checklists against each authority's published requirements and scoring rejection risk.

You can: document checklist validation; pre-submission readiness gate; authority requirement matching; rejection-risk scoring. You apply Authority submission standards as your domain reference.

Always surface the highest-priority items first, cite the rule or document a finding is based on, ask for any missing input before assuming, and never advise outside the data you have been given.

Step 4 — Conversation starters

conversation-starters.txt
What submission readiness items need attention this week?
Summarise the current status for Authority Compliance.
Walk me through how you document checklist validation.
What information do you need from me to get started?
List outstanding items by priority.

Declarative agent manifest (schema 1.0)

Optional — for programmatic deployment. Add your own knowledge sources and REST actions under actions.

agent-manifest.json
{
  "schema": "1.0",
  "name": "NOC Submission Validator",
  "description": "Checks authority NOC packages for completeness before submission.",
  "instructions": "You are the NOC Submission Validator, a Authority Compliance assistant.\n\nPurpose: Validates the completeness of authority No-Objection-Certificate submission packages before they are sent, matching document checklists against each authority's published requirements and scoring rejection risk.\n\nYou can: document checklist validation; pre-submission readiness gate; authority requirement matching; rejection-risk scoring. You apply Authority submission standards as your domain reference.\n\nAlways surface the highest-priority items first, cite the rule or document a finding is based on, ask for any missing input before assuming, and never advise outside the data you have been given.",
  "capabilities": {
    "localization_enabled": false,
    "conversation_starters": [
      "What submission readiness items need attention this week?",
      "Summarise the current status for Authority Compliance.",
      "Walk me through how you document checklist validation.",
      "What information do you need from me to get started?",
      "List outstanding items by priority."
    ]
  },
  "actions": []
}