Institution context build

The decision on your calendar.

Policies, executive knowledge and vendor records sit in separate files. Your institution needs ownership, versions and permitted uses before making them conversational.

Bring the sources you are allowed to share.

• A bounded source collection
• Named source owners and sharing permissions
• The workflow and knowledge questions
• Required access, retention and exit conditions

The file your institution keeps.

• A source ownership and version register
• Knowledge gaps and reviewer assignments
• A context structure your institution keeps
• Permitted-use and access requirements
• An implementation and exit plan

Four working steps.

1. Agree the questionOne workflow, permitted inputs, accountable owner and the decision due.
2. Prepare the sourcesKeep versions, missing records and assumptions visible.
3. Review the evidenceRetain failed cases. Your team reviews the proposed answer and open questions.
4. Leave the fileA one-page recommendation, supporting records and named next actions.

Your team owns review and acceptance.

This is a proposed follow-on engagement. Handling, delivery environment, acceptance and timing must be agreed before work. A hosted workspace is not included by default.

Timing depends on agreed inputs and customer review. Corrections within the agreed scope are recorded in the file; a new use or workflow requires a new scope.

Inspect the method.

Read the source-handling routes. Browser methods work on supplied inputs or inspectable examples.

Scope and fee.

Scope and fee fixed in writing after one working session. The written scope names the sources, customer review responsibilities, deliverables and corrections included.