How to Build a Grant Project Web Page: Six Steps That Match the Agency Guide
If your grant contract includes a project web page, that page is a deliverable with rules, not a marketing choice. Both guides read for this piece make the same three demands: the funder’s logos placed to a published standard, a disclaimer at the foot of the page, and a live link to the agency’s own site. Kuzeydoğu Anadolu Development Agency (KUDAKA), the regional public body running state-funded grant programs in Erzurum, Erzincan and Bayburt, goes further and requires the page to stay current for at least one year after the project ends, warning that the related budget line can be reclaimed if it is not updated.
Say you run a dairy cooperative in Erzincan, in eastern Turkey, and your 2026 contract lists a project web page as an activity. Six steps take you from the clause in your annex to an archived page an auditor can check. The binding document is always the guide attached to your own contract.
What do the guides actually require from the page?
BU BÖLÜMÜN ÖZETİ
- What İKA section 3.7 says
- What KUDAKA section 4.7 says
- What neither guide asks for
Less design than you expect and more bookkeeping. İpekyolu Development Agency (İKA), which covers Gaziantep, Adıyaman and Kilis, devotes its section 3.7 to web sites; KUDAKA covers the same ground in section 4.7. Between them they name logos, a disclaimer, outbound links, contact details and a minimum lifespan.
What İKA section 3.7 says
İKA states that if the project includes creating or developing a web site, the site must introduce the project and must mention the agency’s contribution. Placement of the agency and ministry logos and of the disclaimer may vary with the site’s design, but the guide says the bottom of the page is generally the more suitable place.
What KUDAKA section 4.7 says
KUDAKA calls the web page potentially the most important communication tool for some project objectives, then asks for restraint: pages should be as simple as possible and not overloaded. It recommends photographs showing the current state of the work, sized so they do not slow the site down.
What neither guide asks for
Neither asks for a separate domain, a content management system or a particular platform. A clearly structured page on your existing site satisfies both, provided the required elements are on it.
Steps 1 and 2: find the clause, then place the logos
Half a day, no spend. First you read the web page clause in your own annex rather than any agency’s public guide. Then you collect the logo files and place them in the order your guide sets, because the arrangement is specified and auditors look at it first.
Step 1: read your own annex, not a published guide
Open the visibility annex attached to your contract and find the web page section. Note every listed element and every duration. Two agencies in the same country ask for different things, so another region’s guide is a useful draft and a dangerous source.
Step 2: place the logos to the published standard
KUDAKA requires the agency logo, the Ministry of Industry and Technology logo and the beneficiary logo on the page, placed in line with the visibility standard, and says the rules written for bulletins and press releases apply to the web page too. The hierarchy itself is set out in grant logo usage rules.
Steps 3 and 4: the footer disclaimer and the links out
These two steps live in the same strip of the page and take an afternoon. The disclaimer is a fixed sentence you copy, never draft. The links are ordinary outbound links placed on the funder logos, which is the part teams most often forget because it looks decorative.
Step 3: copy your guide’s disclaimer word for word
Do not write this sentence and do not translate it loosely. İKA requires the disclaimer at the bottom of the page and uses it on every brochure, report, bulletin and news item as well. KUDAKA asks for two separate statements: a funding sentence naming the program year and the contract number, and a content-responsibility sentence.
Step 4: link the agency and ministry logos to their sites
İKA is specific here: the agency logo should carry a link to ika.org.tr and the ministry logo a link to sanayi.gov.tr. KUDAKA requires a link to kudaka.gov.tr. Keep them as standard links so they stay crawlable.
Step 5: keeping the page current for a year after the project ends
This is the obligation that outlives the project, and the only one with money attached. KUDAKA requires the project web page to stay published and current for at least one year after the project ends, and states that if the page is not periodically updated in that period, all or part of the relevant budget line may be reclaimed.
Current means updated, not merely online
A page that has not changed since the opening ceremony is online but not current. KUDAKA asks for progress material: photographs of activities and short interviews about what the project is doing. Four short updates a year is a defensible rhythm and takes an hour each.
Put the dates in a calendar on signing day
Domain renewal, hosting renewal and four update slots, all booked past the project end date. Nobody remembers an obligation in month fourteen. The full set of deadlines across materials and reporting sits in grant visibility obligation period.
Step 6: archiving the evidence an auditor will accept
Evidence is cheap while the page is live and expensive once it is gone. Screenshot the full page on the day it goes live, keep every update dated, and store the hosting and domain invoices beside them. An auditor checks whether the page existed with the right elements at the right time.
What goes in the folder
A dated full-page screenshot showing the logos, footer and links. A copy of the disclaimer text as published. Hosting and domain invoices. One screenshot per update, named by date. The folder structure for the printed materials is covered in grant visibility requirements turkey.
Archive the page itself, not just the design
Save the HTML or a PDF print, because a redesign eighteen months later can quietly remove a logo or a footer line. The live page proves today; the archive proves the whole obligation period.
Where do the two guides differ, and what do you do about it?
They differ in wording, and the difference matters because you copy the text rather than paraphrase it. İKA and KUDAKA use different verbs, name different institutions and set different scopes. Read the table as a report on two documents, not as a choice you get to make.
| Element | İKA, section 3.7 and 2.2 | KUDAKA, section 4.7 |
|---|---|---|
| Disclaimer scope | “This publication”, covering brochures, reports, bulletins, news and web sites | “The content of this website”, specific to the page |
| Wording of the denial | Does not reflect the views of the ministry and the agency | Does not contain the views of the agency and the ministry |
| Who may be named | The support beneficiary | The support beneficiary or the subcontractor |
| Funding statement | Project or activity name inside the disclaimer sentence | Separate sentence with program year, program name and contract number |
| Placement | Bottom of the page, described as generally more suitable | Logos per the visibility standard, no page position fixed |
| Outbound link | Links on the agency and ministry logos | Link to the agency’s official site |
| Lifespan | Not stated in section 3.7 | Current for at least one year after the project ends |
Even one guide can carry two versions
In İKA’s own document the disclaimer appears twice with different institutions named: one version refers to the Ministry of Industry and Technology and the agency, another to the agency and the Directorate General for Development Agencies, the ministry unit overseeing the agencies. That is a reason to verify rather than assume.
Ask your monitoring officer in writing
İKA already notes that the final form of logo use on promotional materials is settled in discussion with the monitoring expert. Send one e-mail naming the exact sentence you intend to publish and ask for confirmation. Keep the reply in the evidence folder; a written answer is worth more than a phone call.
What should you check before the page goes live?
Six lines, reviewed by whoever signs the final report rather than whoever built the page. Five of the six are footer items, which is why a page can look finished and still fail a check. Run the list again after any redesign.
The pre-launch checklist
If a line is unanswered, hold the launch until it is.
- The disclaimer is copied word for word from my own annex, punctuation included.
- Agency, ministry and beneficiary logos are placed to my guide’s standard.
- The agency and ministry logos carry links to their official sites.
- The funding statement names the program year and, if required, the contract number.
- Project name, address, telephone and e-mail appear on the page.
- A dated full-page screenshot is already in the evidence folder.
Who owns the page after handover
Name one person for the year after the project ends, and write that name in the closing report. An unowned page is the one that quietly expires in month thirteen.
Common mistake: lifting the footer text from another funded project’s web site because it looks official. That footer was written for a different agency, in a different program year, possibly with a subcontractor named. Copy from your own annex and have the sentence confirmed in writing.
Open your annex, find the web page clause, and draft the footer today rather than in the closing month. If you would rather hand the page, the updates and the archive to someone else, our visibility service builds them to your own guide, and the remote arrangement is explained in grant visibility service turkey.
Frequently Asked Questions
Quick Summary
- İKA section 3.7 and KUDAKA section 4.7 are the clauses that govern a project web page.
- Logos, a disclaimer and a link to the agency’s own site are required in both.
- The two guides word the disclaimer differently, so copy your own annex verbatim.
- KUDAKA asks for a funding sentence with the program year and contract number.
- The page must stay current for at least one year after the project ends under KUDAKA.
- A dated screenshot archive is the evidence that survives a redesign.
Short Glossary
- Disclaimer
- A disclaimer is the fixed sentence naming who funded the project and who alone answers for the content published about it.
- Monitoring officer
- A monitoring officer is the agency staff member assigned to your contract, who approves visibility materials and answers questions in writing.
- Visibility annex
- A visibility annex is the part of your contract that lists the materials, logos, wording and durations your project must follow.
Next Step
Draft the footer this week, send it to your monitoring officer for written confirmation, and book the four update slots for the year after project end. For the wider programme of channels the page sits inside, start with visibility services, then the site-level work in website visibility.
Updated: October 2026
Author: Guide Desk · AINEO-assisted desk · Editor: Ünsal Hanoğlu
Sık Sorulan Sorular
No. Copy the sentence printed in your own agency’s guide exactly as it appears, punctuation included. İKA and KUDAKA word it differently, naming different institutions and using different verbs, so a paraphrase can fail a check even when it is accurate. If the wording in your guide is unclear, ask your monitoring officer in writing before publishing.
İKA states that placement can vary with the site’s design but that the bottom of the page is generally more suitable, and its example shows a footer layout. KUDAKA does not fix a position, asking instead that the logos follow the visibility standard. In practice a footer block satisfies both and survives a redesign more easily than an in-page box.
Under İKA’s section 3.7, yes: the guide asks for links to the agency and ministry web addresses on those logos. KUDAKA requires a link to the agency’s official site. Use ordinary links without any attribute that blocks crawling, so the link is visible to an auditor and to search engines alike.
KUDAKA requires the project web page to remain published and current for at least one year after the project ends, and warns that all or part of the related budget line may be reclaimed if the page is not periodically updated during that period. İKA’s web site section does not state a duration, so check your own annex for the number that applies to you.
KUDAKA recommends photographs showing the current state of the project and asks for material such as activity photographs and short interviews, while warning that image sizes should not slow the site. İKA requires the project to be introduced and the agency’s contribution mentioned. Photographs also make the yearly updates easy to produce.
That depends on your approved work plan rather than on the visibility guide. KUDAKA’s wording implies a budget line for the web page, since it refers to reclaiming all or part of that line when the page is not kept current. Put the item in the plan before you spend, and confirm eligibility with your monitoring officer in writing.