Keep a supported account
Organise the facts, evidence and language you reuse, and keep an agreed source that can be checked and updated.
Grant Readiness Starter Kit →Grant Resource Studio™
How it works
Understand the source review, team judgement, structured knowledge and human-approved updates behind a build.
The foundation comes first
Review the knowledge before drafting
A useful source can contain an outdated figure or describe a programme that has changed. The work begins by deciding what is current, resolving contradictions with the team and capturing delivery practice that has not been written down.
GRS structures the agreed material around recurring funding questions, with enough evidence for someone to check it. Context architecture is the supporting discipline: deciding what the assistant needs, where it comes from, which source governs and how changes are agreed.
The practice, the build and the asset
Three names, with different jobs
- Practice
Grant Resource Studio™
The specialist practice that publishes free resources and delivers commissioned support.
- Build
Grant Readiness Engine™
The six-stage process for developing a commissioned knowledge base with your team.
- Asset
Funding Knowledge Base
The reviewed organisational knowledge your team owns, uses and keeps current.
The Engine describes how a build is delivered. The Ecosystem below describes practices you can use independently or together in day-to-day funding work.
The guided build
The six-stage Grant Readiness Engine™
Discovery
Agree what you need to use the knowledge for, the source material, reviewers and intended workspace. Identify important gaps and a workable scope.
Review
Assess existing applications, reports and evidence. Your team helps distinguish current information from older accounts and explains what needs checking.
Extract
Develop reusable content from sources and conversations. Review the first drafts together so useful material and missing evidence become visible early.
Structure
Organise the agreed account, Case for Support and application reference information. Check that recurring questions lead to relevant, supported material.
Build
Create the knowledge base in the agreed workspace and configure the drafting workflow. Your team confirms how it will find, use and maintain the content.
Apply & Improve
Test a real or example application, correct problems and practise using the asset. Handover includes an agreed routine for reviewing future changes.
The practices in use
The Grant Readiness Ecosystem
A Funding Knowledge Base still goes out of date if nothing notices when a fact has moved.
The Working Context System acts as a reliable second brain, helping make that knowledge self-maintainable through human review and approved updates. When configured with the relevant sources, it can surface drift, gaps and new information as you work, so a person can check the change and write it into the knowledge.
Organised knowledge, working context and structured review reinforce each other. You can enter through any practice, around a useful Starter Kit document or a fuller FKB. A commissioned build is not a prerequisite.
Carry agreed working context
Keep relevant instructions, decisions and source pointers available across sessions, helping bring possible changes back for review.
Working Context System →Check the draft
Check against published funder requirements and evidence. Missing facts or inconsistencies can point to a knowledge update for a person to approve.
Application Review Kit →Review findings → check the source → approve a change → update the knowledge.
How the parts work together
The right knowledge,
carried into the work.
Agreed knowledge and working context can support recurring workflows and one-off requests, with human review and approved updates.
Agreed information
Your funding knowledge
A full Funding Knowledge Base or smaller document holding agreed facts, evidence and reusable material.
Start with a knowledge document →Continuity between sessions
Working context
Current instructions, relevant decisions and pointers to the sources to read.
Working Context System →Inform the task
Within the access you agree
Your AI assistant
Uses relevant sources with the task’s current guidance, project details or reporting figures.
Support different kinds of work
Recurring workflows
Work you return to
- Grant applications
- Funder reporting
- Donor communications
Agreed inputs, outputs and review points.
One-off requests
Work that arises
- A partnership brief
- A wider funding conversation
- A question about your evidence or work
Check the evidence and requirements for each request.
Outputs go to a person
Human judgement and structured checks
People review and decide
Check facts, evidence and requirements before using or sending the output. Use the Application Review Kit for grant drafts; check other outputs against their own purpose.
Only approved changes return to the right record. Check the source and agree the update to knowledge or working context.
Operational records remain in their existing systems and are supplied where needed.
Checked funding knowledge and agreed working context inform an AI assistant alongside current task inputs. They support recurring applications, reports and donor communications, as well as one-off partnership briefs and funding conversations. A person checks the output before use. Only source-checked and approved changes return to the appropriate knowledge or context record. Operational records remain in their existing systems. This is a working arrangement that complements the three-practice Ecosystem and is distinct from the six-stage build process.
What a full knowledge base can support → · How changes are reviewed and approved →
Keep a person in charge of changes
- Identify relevant evidence or a confirmed change.
- Propose a specific update to the record that owns it.
- Have a person check the source, wording and implications.
- After approval, edit the source directly or authorise a configured assistant to apply that agreed edit.
If a source is missing or read-only, the assistant must say so and leave the change for someone who can make it. Your team remains responsible for checking the work.
The published Context pack carries agreed working context across sessions. This page makes no claim that it automatically maintains a Starter Kit knowledge document.
See the approach in practice
Compare the fixed demo answers, read the originating case study, or watch the two-minute explainer on YouTube.