The panel’s job is to choose which good projects to decline.

Grant proposal writing for teams whose proposals are good and lose anyway
and who cannot work out which sentence did it.

Nobody on the panel is looking for a reason to fund you. They are assembling a shortlist and then writing down why everything else did not make it.

The four sentences a panel would otherwise write about you, answered before they write them. Standing built out of whatever can actually be pointed to. The risky phase moved early so the schedule can hold. And figures that say the same thing as the account beside them.

WHAT THE WORK IS 01 / 04

Four sentences account for most of the declines. Every one of them can be answered in advance.

  • 01 The four sentencesAnswered first.
  • 02 The first pageMaking the interest.
  • 03 The scheduleRisk moved early.
Declines answered in advance Interest made, not found Risk placed early Figures matching the account

The Writely difference

Almost every proposal that fails would have passed a panel reading it warmly. Very few survive one reading it for the reasons it will be declined.

Which is why the first thing this service does is not write the proposal. It is find the four sentences.

Answer the four sentences before they get written

The whole method, and it is worth being exact about the sentences because they are not imaginative. The outcomes are unclear. The team has not worked with this group before. The timeline does not hold. The numbers do not add up. Panels produce these same four lines in the same order, because they are how a rationalisation gets written when nobody wants to write a long one. So the proposal is built so that each of the four has already been answered in the panel’s own words, in the panel’s own section, before the panel reaches for the sentence. Where one of them cannot be answered, that is the finding, and it arrives weeks before a decision would have.

Make the interest, because the reader did not choose you

You know why the project matters. The reviewer is holding thirty proposals and a part-time slot, none of which they picked. Every one of those thirty argues that its subject is urgent, so the importance claims cancel each other out and none of them is read as a reason. What converts a reader in that position is a specific answer to three questions on the first page: what changes, for whom, and by when. That is not a summary of the proposal, it is the only part that will be read twice, and a proposal whose first page is context rather than those three answers is asking the reader to do work at exactly the point where they have least reason to.

Place the risky phase early rather than late

Every panel has read a thousand optimistic schedules, so yours arrives already discounted, and the discount is applied before anybody reaches the thinking. That makes the timeline worth more attention than its share of the document. The schedule that survives has two features and they are structural rather than cosmetic: the risky phase comes early, so that if the risk is real it surfaces inside a phase with room to respond rather than in the last one, where it ends the project instead of delaying it; and each phase carries slack, so the slip absorbed by one phase does not become a slip absorbed by all of them. A tight schedule is not read as ambitious. It is read as not having thought about it.

Make the figures say what the account says

Because the account and the itemised lines get assessed on their own, often by different people, sometimes on different days, and the person doing the figures does not go back and reconcile them. Which means a single figure that tells a different story from the account beside it is not tidied up; it is noticed, and the noticed figure is what gets believed. So the figures are written as an argument in their own right and then checked against the narrative line by line, asking of each one what the reader beside it would conclude. Two of the three places this goes wrong are ordinary: a total that does not match the sum of the lines, and a figure in the middle of the schedule that has no relationship to the phase it belongs to.

Find out what a panel is actually deciding

Eight things a grant proposal has to settle, and the one nobody checks is what your reader is writing at the end of it.

None of this is about writing more. It is about removing the four sentences a panel would otherwise have available to you.

Write for the rationalisation rather than the enthusiasm

Which is a strange instruction until you picture the last two hours of a panel’s work. Somebody is writing down why each proposal was declined, in a few lines, from a template of their own making, and they would rather finish early. Everything in a proposal is therefore read twice: once by somebody deciding, and once by somebody filling in a box afterwards. A proposal that has already supplied the language for the second reading has removed the easiest work available to the person filling it in. This is not a rhetorical point about tone. It is about which sentences end up in a box with your name on it.

Put what changes, for whom and by when on the first page

The three answers, in that order, within the first page, and they are the part of the document that gets read twice. Not a summary and not background: the specific change, the specific group it reaches, and the date it is expected by. Everything can then be judged against those three, which is what a panel does with a strong proposal and cannot do with a weak one. The reason this belongs at the front rather than the end is that a reader who has been given thirty proposals is not building a mental model of yours while they read, they are deciding how much of it to read, and these three answers are what the decision is made on.

Answer the four sentences in the panel’s language

Which means using their words rather than your own, because a panel looking for an answer to the timeline question will not recognise one written as a statement about the team’s confidence. So each of the four gets its own place, phrased as the panel would phrase the concern and answered as fact, and the strongest version of this puts the panel’s objection on the page and then disposes of it in the same breath. A proposal that leaves an objection unanswered is not neutral about it; it has handed the reader a sentence they can now use, and readers use sentences far more readily than they produce them.

Say who would vouch for you, by name

Because a track record here cannot be checked by a panel reading a letterhead they have never seen, and the question underneath every one of these applications is whether the work will actually happen. The honest substitutes are specific and usually available: a named partner who would confirm the arrangement, a community the organisation has already worked in, someone whose previous work in the same setting is described rather than titled, and a track record stated as what happened rather than as a claim about capability. None of those is as good as an institutional name a reader recognises, which is why this is where a proposal from a small organisation is quietly at a disadvantage, and why saying so plainly is better than hoping it is not noticed.

Order the phases so the risk surfaces while there is still time

The practical form of putting the risky work early, and it is the single change that most affects whether a schedule reads as thought about. If the part most likely to fail is the first thing to be delivered, then finding out takes little and the rest of the project can adapt. If it is the last thing, then finding out is fatal and the panel’s third sentence has already been written. Where the risk genuinely cannot be moved, the proposal says so, names what happens if it materialises, and shows where the slack sits, which is the honest version and is read as such.

Treat the figures as read by somebody in a hurry

Not read carefully, read quickly, and not by the person who read the prose. Which means each line should be identifiable on its own without a heading explaining it, the totals should be visible without arithmetic being performed in the reader’s head, and nothing should depend on a footnote. Where a figure cannot be made obvious without explanation, the explanation usually belongs beside it rather than in a note at the end, because a note at the end is a document the hurried reader has already decided not to open. This is unglamorous and it decides a real number of proposals.

Describe the work instead of naming the job titles

Locally specific and it applies to the whole team section rather than to one line of it. A funder reading from outside the country cannot check a title, and the same title carries different work depending on the region, the sector and how far the reader is from it, so a team described by role is often read as vague where it was meant to read as senior. What travels is the work: what this person has actually done, in what setting, and what they would be doing on this project. It also protects the proposal, because a panel can check a description against something they know and cannot check a title against anything at all.

What this service cannot do

Five limits. A grant proposal does not promise outcomes the work cannot deliver, because a funder who funded a project once remembers it. It does not pad the team with names to make it look stronger, since a panel checks a track record rather than counting people. It does not write a referee’s report and it does not invent a history that is not there. It does not submit where the project contradicts the programme’s published criteria, because that is a decision about whether to apply rather than a matter of wording. And it does not write an academic research proposal, which is a different document and has a page of its own.

Before anything is drafted, write down the four sentences a panel would use against you. Then answer each of them in their words. Everything else on this page follows from doing that first.

A better brief

Send the programme’s own criteria, and the parts of the record you were not sure counted.

The brief that stalls this is the one that describes how important the work is, because every applicant says that and it cancels out before the panel reaches the second page. Send instead: the published criteria and the guidance notes, the panel’s stated priorities in their wording, the parts of the record that are thin, and the parts you were hoping would not be asked about. Also send the dates properly, since a tight schedule is read as a thoughtless one and the fix is usually a reordering rather than more time.

  • The published criteria and guidance notes.
  • The panel’s stated priorities, in their words.
  • What you have done before, and where.
  • Who would vouch for the team.
  • The parts of the record that are thin.
  • The deadline, and how firm it is.
Share your brief
DECLINE SHEET Before drafting

The four sentences, answered.

Outcomes clear
Standing shown
Schedule holds
Figures add up
First page specific
Risk moved early

How the work is done

From the four sentences a panel would write, to a schedule and a set of figures that both hold up.

Four sentences, first page, schedule, figures. The first step removes the objections; the last one stops the account being quietly discounted by a number.

01 / THE FOUR SENTENCES

Find them, then answer each one in the panel’s wording

First, and it decides the shape of everything after it. The sentences are not creative: the outcomes are unclear, the team has not worked with this group, the schedule does not hold, the figures do not add up. Each gets written down, and then each is answered where a panel would look for the answer, using the panel’s own phrasing rather than a reframing of it. Where one cannot be answered honestly, that is the most useful finding this service produces, and it arrives early enough to do something about: change the plan, change the team, change the request, or do not apply.

02 / THE FIRST PAGE

What changes, for whom, by when, and nothing else

Then the page that decides whether the rest gets read, written to be read twice rather than once. Three answers in that order, specific enough to be disagreed with, and no background before them. Everything after this page is judged against those three, so they are chosen rather than drafted: if they cannot be made specific, that is usually a sign the project itself has not decided what success looks like, which is worth discovering before a panel does it for you. The rest of the proposal then earns its length rather than assuming it.

03 / THE SCHEDULE

Move the risk early and build the slack in where it is needed

Third, because a schedule that does not hold is the fastest decline available and the one most proposals supply by accident. The work is not adding time; it is reordering, so that the phase most likely to fail is the first one delivered and therefore the least expensive to discover, and then giving each later phase enough room that a slip in one does not become a slip in all of them. Where the risk cannot be moved it gets named plainly, with what happens if it materialises and where the slack sits, because a panel can assess a stated risk and cannot assess one they have to guess at.

04 / THE FIGURES

Make them say the same thing as the account

Finally, and against a reader who has not read the prose. Each line is made identifiable on its own, totals are visible without the reader doing the sum, and nothing important hides in a footnote. Then the harder check, which is line by line against the narrative: what would the person reading this figure conclude, and does the section above it say the same thing. Most disagreements between a narrative and its figures are not errors but two different stories about the same project, and the figure is the one that is believed.

What actually gets handed over

Five documents. The decline sheet is the one that decides whether the rest of the work is worth doing.

A grant proposal is a single document and the work behind it is not. Three of these five are written before anything is drafted, and one of them is written for a decision that may go against you.

The decline sheet

The four sentences a panel would write about this project, in the order they usually write them, with the answer to each and the place in the proposal where that answer lives. This is the document the whole engagement is built around, because everything else in it is a way of making one of those four sentences untrue. It also records where an objection could not be answered, which is the most valuable thing the process produces and the reason a proposal can be stopped before a deadline rather than after a decision. Where one of the four is answered by an obvious change to the plan, this is where that change gets made.

The first page

What changes, for whom, by when, in three answers specific enough to be disagreed with, and nothing in front of them. The page is written to be read twice rather than skimmed, since it is the only part of a long document a hurried reader gives a second look. It also records the reasoning for the choices, because the specific version and the general version differ by about four sentences and the difference decides whether a panel can picture the end of the project. Where the three cannot be made specific, the note says so rather than supplying a version that reads well.

The standing note

Everything that can be pointed to in place of an institutional name the reader has never heard: prior work in the same setting, named partners who would confirm the arrangement, individuals whose record is described rather than titled, and the standing of the organisation in its own community stated as fact rather than claimed. This is the section that carries the most weight for a small organisation and gets the least attention, usually because it is assumed to be about credentials and there are none. The note makes the inventory explicit, which is usually longer than the applicant expected and usually includes three things they had not counted.

The schedule with its slack

The full timeline with the risky phase moved to the front, slack marked on each phase, and a plain statement of what happens if the risk does materialise. Not a summary of the schedule in the proposal but the reasoning behind its shape, so that a panel reading the third section can see why the phases are in that order and that it was not arbitrary. It also records where the dates are fixed by something outside the team, which is usually the honest reason a schedule is tight, and stating it plainly reads very differently from a schedule that is simply tight.

The figures note

The itemised lines checked line by line against the account beside them, with every point of disagreement recorded and resolved rather than smoothed over. It covers the three ordinary failures: a total that does not match the sum of what is above it, a figure in the middle of the schedule with no relationship to the phase it belongs to, and a line whose purpose only becomes clear from a footnote nobody will open. It is the least interesting document here and the one that most often stops a strong proposal being quietly set aside.

Three of these five are written before a line of the proposal. That is not a preliminary; it is the part that decides whether the proposal deserves its length.

What a grant proposal has to settle

Six things, and the one nobody settles is what your reader will write when they put you down.

Each can be settled before drafting, and the first one settles what the proposal is for.

  • The four sentences, answered.
  • What changes, for whom, by when.
  • Standing that can be pointed to.
  • A schedule with the risk moved early.
  • Figures matching the account.
  • Alignment with the published criteria.
THE PROPOSAL Six things

Six things it must settle.

Sentences answered
First page specific
Standing shown
Risk moved early
Figures aligned
Criteria matched

Explore the pages around this one

The neighbouring documents, and the two proposal pages that already exist here.

A grant proposal is written for a panel against published criteria, which makes it closer to the research and reporting pages than to the ones written for a reader who is already reading. These are the pages covering the rest of that territory, including the academic research proposal page, which is the one most often confused with this one and which this page does not overlap.

Two proposal pages already exist here and neither overlaps this one. A research proposal asks a supervisor or a committee to approve a study. A general proposal asks a client to commission work. A grant proposal asks a funder for support against published criteria, judged by a panel that did not choose the project.

Where this is actually described

All eight are new to this set, and one of them is the document your panel is reading.

Twelve candidates were tried across two rounds and eleven answered; eight are used here and all eight are new. They cover the structure a panel actually reads, the question of evidence behind it, what is supposed to happen afterwards, the process of choosing between good options, the mechanics of a schedule that holds, and the object itself in its research and general forms. One entry was answered and then dropped because it already appears elsewhere in this set. These external resources are informative references, not Writely service pages.

THE STRUCTURE A PANEL ACTUALLY READS

Wikipedia: Logic Model

The single most useful structural reference on this page, because most proposals describe activities and almost none of them explains the chain that connects those activities to a change. Its account of inputs, activities, outputs and outcomes, of the link between each and the next, and of why a programme with perfectly good activities and a broken chain between them is still not going to work is the shape of the first-page answers this page is about. It is also the fastest diagnostic available: a project that cannot fill in the middle of that chain has usually not decided what success looks like, which is worth finding out before a panel discovers it.

Open resource
WHY THE EVIDENCE QUESTION DECIDES IT

Wikipedia: Needs Assessment

The reference behind the question a panel asks first and states least often: why this, why here, why now, and how do you know. Its treatment of finding out what a group actually needs rather than what it has been assumed to need, of the difference between a stated problem and a shown one, and of what happens when a proposal asserts a need without having checked it is exactly the gap that produces the first of the four sentences. It is also where an applicant from a community the funder has never worked in gains or loses most, since a funder cannot assume the problem is understood.

Open resource
WHAT THE PANEL IS ACTUALLY BUYING

Wikipedia: Monitoring and Evaluation

The section most often written last and read most closely, because a funder is not buying the activity and is buying the evidence that the activity changed something. Its account of tracking progress against stated objectives, of measuring outcomes rather than outputs, and of the discipline of writing down what was going to happen before it happened is the argument for the first page on this page. It also makes the boundaries here concrete: a proposal promising more than its own monitoring can check is promising something nobody will be able to verify, including the funder.

Open resource
THE SPINE OF THIS PAGE

Wikipedia: Competitive Bidding

The process a grant panel actually runs, described without the sentiment that usually attaches to it. Its account of choosing between multiple submissions for a limited allocation, of evaluating against criteria rather than against preference, and of what an assessor is required to record and justify is the reason this page argues that the writing should be aimed at the decline rationale rather than at enthusiasm. A panel is not trying to find a project to love, it is trying to produce a defensible shortlist, and a submission that has already answered the four obvious objections makes that job considerably easier.

Open resource
WHY A TIGHT SCHEDULE GETS DISCOUNTED

Wikipedia: Critical Path Method

The technical reference behind the third of the four sentences, and the one that explains why the answer is reordering rather than more time. Its treatment of the longest dependent chain of tasks in a project, of how delay on that chain moves everything after it, and of why a schedule with no slack anywhere is a schedule where one late delivery moves the end date is exactly what a panel is checking for when they read a timeline. It is also the argument for putting the risky phase first: on a chain, finding out early takes little and finding out late takes a great deal.

Open resource
THE OBJECT, IN ITS RESEARCH FORM

Wikipedia: Research Grant

The closest neighbour to what this page describes, and reading it explains why the research proposal page is not a substitute. Its account of funding awarded to support investigation, of the norms governing who may apply and what they may claim, and of how a research application is assessed on the rigour of its method makes the distinction obvious: there the burden of proof is whether the study is sound, and here it is whether the study is better than the other sound ones on the same pile. Where both forms appear in one application, they are written to different panels and neither substitutes for the other.

Open resource
THE OBJECT IN GENERAL

Wikipedia: Grant

The general reference, and the one that clarifies what a funder is actually purchasing when the sum is not large. Its account of support given without a repayment obligation being the main condition, of the difference between that and a payment for a deliverable, and of why the two attract different applications and different readers is worth understanding before drafting. It also explains the panel’s position better than any etiquette guide does: the reader is not a client with a problem and cannot be persuaded that a problem exists, only shown that this is the best available answer to one they already recognise.

Open resource
WHY THE CLAIMS GET CHECKED

Wikipedia: Evidence-Based Practice

The discipline behind why a panel checks rather than agrees, and the reason a well-meant claim does not carry the weight it used to. Its account of decisions resting on the best available research rather than on preference or habit, of how weak evidence gets exposed in practice rather than in theory, and of why an intervention that sounds reasonable and has not been shown to work is treated as an open question is precisely the reader a grant proposal is up against. It is also a useful discipline for the writer, since it asks the same question of a proposal that a panel would.

Open resource

Your letterhead is not being read by anybody who knows it

Nigeria at the centre. Where standing has to be built rather than assumed.

Writely is rooted in Nigeria and works remotely with applicants and organisations across every sector. Wherever you are applying, the name on your letterhead carries no weight until something in the proposal makes it carry some.

Remote grant proposal writing for any market

Grant proposal writing across Nigeria

Explore grant proposal writing for applicants and organisations in Nigerian cities, communities and states. One thing here is different enough to change how a proposal is written, and it is not a small one. A funder assessing an application from this market will usually have no prior knowledge of the organisation applying, and cannot check a track record from a letterhead, so the whole section that elsewhere is a formality has to be built from things that carry weight on their own: prior work in the same community, a named partner who would confirm the arrangement, a person whose record is described rather than titled, and standing asserted as fact about a place rather than as a claim about capability. The second local difference is that job titles do not travel, so a team described by role reads as vague to an external panel where it was meant to read as senior, and the work has to be described instead. The third is that funders in this space often fund across regions and sectors, so a proposal that assumes its reader already understands the local context is a proposal that has to describe that context as part of the case rather than as background.

Lagos Abuja Port Harcourt Kano Ibadan Enugu Benin City Uyo Kaduna Calabar Jos Abeokuta Awka Akure Warri Owerri Zaria Sokoto Bauchi Maiduguri

Nigeria states and the Federal Capital Territory

Writely’s support is available remotely across Nigeria, including:

  • Abia
  • Adamawa
  • Akwa Ibom
  • Anambra
  • Bauchi
  • Bayelsa
  • Benue
  • Borno
  • Cross River
  • Delta
  • Ebonyi
  • Edo
  • Ekiti
  • Enugu
  • Gombe
  • Imo
  • Jigawa
  • Kaduna
  • Kano
  • Katsina
  • Kebbi
  • Kogi
  • Kwara
  • Lagos
  • Nasarawa
  • Niger
  • Ogun
  • Ondo
  • Osun
  • Oyo
  • Plateau
  • Rivers
  • Sokoto
  • Taraba
  • Yobe
  • Zamfara
  • Federal Capital Territory

Remote support across Africa

Country-level discovery

Writely works with applicants and organisations across Africa, including in:

Nigeria Algeria Angola Benin Botswana Burkina Faso Burundi Cabo Verde Cameroon Central African Republic Chad Comoros Côte d’Ivory Democratic Republic of the Congo Djibouti Egypt Equatorial Guinea Eritrea Eswatini Ethiopia Gabon Gambia Ghana Guinea Guinea-Bissau Kenya Lesotho Liberia Libya Madagascar Malawi Mali Mauritania Mauritius Morocco Mozambique Namibia Niger Rwanda São Tomé and Príncipe Senegal Seychelles Sierra Leone Somalia South Africa South Sudan Sudan Tanzania Togo Tunisia Uganda Western Sahara Zambia Zimbabwe

Questions, answered

Send the criteria.

If your question is not covered here, send the essentials in a chat. The guidance notes tell us more than the idea does.

Ask your question
What is grant proposal writing?
Writing the application that asks a funder for support against published criteria, judged by a panel that did not choose the project. The distinctive part is that the reader is not trying to be persuaded the project is good, since everything on the pile is good, but is choosing between good options and then writing down why the others were passed over. So the work is aimed at those four sentences a panel reaches for when it declines something: the outcomes are unclear, the team has not worked with this group, the schedule does not hold, and the figures do not add up.
How long should a grant proposal be?
Whatever the guidance notes ask for, and not more. Length is one of the few things in this field where the instinct to be thorough is actively harmful, because every extra page is another page a panel has to read before reaching the part they will judge you on. What belongs in the length is the evidence, the method and the reasoning, and what does not is a restatement of the case in three different registers. Where the guidance gives a limit, treat it as a limit, and put the three answers about what changes, for whom and by when on the first page rather than in a section called aims.
What are the four sentences that decide most grant proposals?
The outcomes are unclear. The team has not worked with this group before. The schedule does not hold. The numbers do not add up. They are not imaginative and they are not the only reasons projects are declined, but they account for a large share of them because they are how a short rationale gets written when nobody wants to write a long one. The useful consequence is that each of them can be answered in advance, in the panel’s own phrasing rather than a reframing of it. A proposal that leaves one unanswered has not been neutral about it, it has handed the reader a sentence they can now use.
How do I make a small team look credible?
You do not make it look anything, and the attempt is usually what gives it away. What you do is state what is actually there in terms a reader can check: prior work in the same setting, a named partner who would confirm the arrangement, an individual whose record is described rather than titled, and standing asserted as fact about a community rather than claimed about an organisation. A panel checks a track record rather than counting people, so adding names loses credibility rather than buying it. Where the team really is new to the work, saying so plainly and showing how they would be supported is read far better than a roster of names with nothing behind them.
Should I include work I have not started yet?
Yes, since a proposal is by definition a description of something not yet done, and pretending otherwise produces the opposite of what you want. What matters is the distinction between a plan and a promise. A plan says what will be done, by when, with the phase that might not work identified and a response named. A promise says it will happen regardless, and the difference between the two is where a panel’s scepticism comes from. So describe the work honestly as future work, show that you know which part is riskiest, and make sure your own monitoring could check whether you delivered it.
How much detail should the figures have?
Enough that each line is identifiable on its own, that a total is visible without the reader doing the sum, and that nothing important depends on a footnote. Detail below that level invites a reader to work out whether the numbers hold, and detail above it is read as padding. The part that matters more than the level is the agreement with the account: the figures are usually assessed on their own, away from the prose, often by a different person, and a single figure that tells a different story from the paragraph above it does not get reconciled, it gets noticed.
What if the deadline is very short?
Say so at the start, because a short deadline changes what the proposal can honestly claim and pretending otherwise produces a plan nobody can deliver. It is usually better to submit a narrower proposal that fits the criteria than a broad one that does not, since a panel short on time will read the first page and the schedule and little else. Where the timing is genuinely impossible, that is a decision about applying rather than about writing, and the useful work is identifying which parts cannot be written honestly at all. Ask before the deadline is announced internally rather than after.
Can you help if my organisation has no grant history?
Yes, and it is a common situation rather than a disqualifying one. What an organisation without funding history has is prior work, standing in its own community, partners who would vouch for it and people with records a panel can be told about, and those are the things the standing note is built from. What it does not have is an institutional name that carries weight on its own, and no wording substitutes for that, which is worth knowing before applying. Sometimes it changes the answer entirely: a smaller request, a programme that funds first-time applicants, or a partner applying on whose record the proposal can lean.
Do you write the referee's report too?
No, and the reason is worth stating plainly. A referee’s report is somebody else’s assessment of somebody else’s work, and it has to be theirs. What this service does is make sure the material a referee needs is in front of them, which usually means the standing note, the record of prior work and the specific description of the project, since a referee can only speak to what they have been given. It also means telling you where a referee is likely to hesitate, so you can supply the evidence rather than hope. Where a referee has not agreed to write, that is a matter to settle first.
How specific should the outcomes be?
Specific enough to be disagreed with. An outcome stated as improved capacity or greater awareness cannot be checked by anybody, least of all by the funder who funded it and will be asked about it later, and a panel reading it knows it cannot be checked either. What works is a named group, a named change and a date, and the discipline of asking whether your own monitoring could verify it if challenged. Two warnings apply. Promising more than the work can deliver is the fastest way to be funded once and never again, and an outcome list that is simply long dilutes the one or two that matter.
What if my project does not fit the programme criteria?
Then that is a decision about whether to apply rather than a writing problem, and it is better made before the deadline than after a decision. A proposal written to fit criteria it does not meet is usually detectable, because the mismatch shows up in the first page and then has to be explained for the rest of the document. Sometimes the fit is genuinely there and simply has not been described in the programme’s language, which is a wording problem this service can help with. Sometimes the project has to be reframed around a different part of its own work, and sometimes it is simply the wrong programme. All three are worth knowing which one you are in.
Where is Writely available, and how do I start?
Writely is based in Nigeria and works remotely with applicants and organisations across Nigeria and the rest of Africa. Use the Chat with us button to send the published criteria, the guidance notes, the panel’s stated priorities in their own wording, and the parts of your record you were not sure counted. That is enough to write the decline sheet, which is the first thing this service produces and the part that decides whether the rest is worth doing.

Your next move

Send the criteria and the guidance notes. We’ll find the four sentences a panel would write about you.

Whether you need the first page to carry the interest, the risk moved to the front of the schedule, or the figures to agree with the account beside them, begin a clear conversation with Writely.

Request services