Partnership Management Information System
PMIS is the system of record behind funded programs. It publishes the opportunity, receives the proposal, runs the due diligence, holds the signed agreement, and follows the work all the way through to the outcomes that were promised.
Open right now
Read live from the public program register. A program leaves this list the moment its application window closes.
What PMIS coordinates
A partnership is not a document, a workflow or a budget on its own. PMIS holds all of it against the same record, so what was promised in a proposal is still visible when the last invoice is raised.
A program carries a category, a funding amount, a delivery window and its own public application window. Publishing one puts it in front of every registered partner organization for exactly as long as it is open.
PmisProgramOne profile per organization: legal identity, registration, entity type, governance structure, years in operation, compliance position, bank accounts and the people authorized to act on its behalf.
PmisPartnerAn application carries a requested amount and the proposal behind it: objectives, planned outcomes, proposed timeline, deliverable schedule, budget items, monitoring and evaluation, and sustainability.
PmisApplicationDue diligence across six standing sections, agreements produced from controlled templates, electronic signature, and endorsement recorded against the person who gave it.
Due diligence + generated documentsWeighted implementation tasks with deliverable requirements, due dates and evidence attachments; budget lines held against the funding envelope; invoices raised against real progress.
Tasks + budgets + invoicesRole-based permissions across both the admin console and the partner portal, so people see the part of the workflow they are responsible for, with an audit trail behind the actions that matter.
Roles + permissions + auditThe partnership journey
These are the states PMIS actually writes, and the record it keeps at each one. Nothing skips ahead: an application cannot reach approval without clearing assurance, and a partnership cannot start delivery without an agreement behind it.
01Opportunity
A program is created with its category, funding amount and delivery window, then published with its own public application window. From that moment it is visible to every registered partner organization, and only until the window closes.
program.status = published
Public visibility is what puts it in the catalog, and only for as long as the window is open.
02Proposal
A partner keeps one profile: legal identity, registration, governance structure, compliance position. Applying adds the requested amount and a structured proposal, so PMIS carries the organization forward instead of asking for it again.
application.status = submitted
Proposal sections captured at submission
03Assurance
Every partnership is seeded with the same standing checklist across six sections. Each item is answered with its own evidence and supporting documents, reviewed on its own record, and only then does an overall recommendation follow.
application.status = due_diligence
Every item carries its own evidence, comments and reviewer before an overall recommendation.
04Agreement
Agreements are produced from controlled templates rather than assembled by hand. A document travels draft, sent, signed and finalized; endorsers sign off by name with their remarks and the moment they gave it; final approval makes the partnership active.
document.status = finalized
Endorsement
Final approval is what turns the application into partnership.status = active.
05Delivery
An active partnership becomes weighted implementation tasks with deliverable requirements, due dates and evidence attachments. Completion is recorded as a percentage, budget lines sit against the funding envelope, and invoices follow real progress.
lifecycle_stage = implementation
Deliverable requirements, due dates and evidence attachments hang off each task; invoices are raised against the same partnership.
06Outcomes
Planned outcomes, the monitoring and evaluation plan and the sustainability strategy were written into the proposal on day one. They stay attached to the partnership, so what was delivered can be read against what was promised.
planned outcomes + M&E
The same record that carried the promise carries the result, so the two can be read together.
Built for partners
The partner portal is not a status page. It is where an organization does the work: the proposal, the evidence, the signature, the tasks, the invoices and the people allowed to touch each of them.
Apply to open programs
Submit a proposal against any program inside its application window, and see at a glance what you have already applied to.
Keep one organization profile
Legal identity, governance structure, compliance position and bank accounts, reused by every application instead of retyped.
Answer due diligence
Respond to the evidence items requested against your partnership and attach the supporting documents.
Sign agreements
Review generated documents and complete signing, including the electronic signing flow, from inside the portal.
Work implementation tasks
Deliverable requirements, due dates, attachments and completion percentage against each weighted task.
Raise invoices
Submit invoices against the partnership and follow their status through to payment.
Give your team access
Partner roles and users, so each colleague reaches only the part of the portal they need.
Ask for help in place
A help center inside the portal, with articles matched to the page you are on.
Governance and assurance
These are mechanisms in the platform, not claims about it: what has to be evidenced, what has to be signed, who is allowed to act, and what gets written down when they do.
Every partnership is seeded with the same standing checklist. Each item is answered with its own evidence, description and supporting documents, and reviewed on its own record.
Agreements are generated from controlled templates, then tracked through four states. A document does not become binding by being emailed around.
Signature state is tracked beside it as not required, requested or signed, so an unsigned agreement is visible as an unsigned agreement.
Partners complete signature from inside the portal, and the signed document is attached back to the partnership rather than living in someone's inbox.
Endorsement is recorded against named endorsers with their remarks and the moment they signed off. Only then can final approval make a partnership active.
Roles and permissions govern both the admin console and the partner portal, so each person reaches the part of the lifecycle they are accountable for.
Workflow actions are written to an audit log, and termination has its own request, review and decision path instead of a quiet deletion.
From proposal to outcome
A PMIS proposal is structured, not prose. Seven parts are captured at submission, and each one has somewhere to land once implementation starts.
What the partnership sets out to achieve.
The results the partnership commits to.
The delivery period being proposed.
What is handed over, and when.
How the requested funding is allocated.
How progress will be measured.
What continues after the funding ends.
The proposal commits to
Implementation records
Questions
Get started
Browse what is open today, or sign in to pick up an application, a document or a task already in flight.
