Declaring Conflicts of Interest and Funding in Policy Writing

Key Takeaways

• Funding and affiliation statements tell readers who paid for the work. They do not by themselves show whether a funder shaped the argument.
• Disclosure requirements differ by outlet type and by individual outlet, so writers must check contributor guidelines for each submission.
• AI assistance follows the same pattern: some outlets prohibit generated text, others permit limited assistance with a declaration, and a few require a list of language or editing tools.
• A private process log, kept while drafting, is what makes an accurate public declaration possible months later.

1. Introduction

Policy writing borrows authority from process. A reader who finds a well-argued brief on procurement reform assumes the author reached the conclusion by weighing evidence, and that the money behind the research did not decide the answer in advance. Funding and conflict statements exist so readers can test that assumption themselves.

The practical problem is that almost nobody is taught how to write one. Author guidelines mention disclosure in a sentence or a footnote. Institutional pages list donors somewhere else. Journals ask for a formal competing-interests section, while a think tank blog may ask for nothing at all. Authors who guess end up either over-declaring irrelevant details or leaving out a board seat that a reader would reasonably want to know about.

This article covers what belongs in a conflict and funding declaration in policy writing, how outlet expectations shift across publication types, and how to keep records that support an accurate statement when an editor asks for one.

2. What belongs in a conflict of interest statement

A usable conflict of interest statement answers three questions: who paid for this work, what relationships a reasonable reader might think influenced it, and what remains unknown.

Funding is the part readers check first. Report grants, contracts, commissioned research fees, and institutional support that covered your time. If a government body, company, foundation, or trade association funded the project, name it.

Relationships matter beyond money. Board seats, advisory roles, paid speaking, expert witness work, and consultancy arrangements create obligations a reader may want to weigh. So does personal financial interest in the policy outcome, such as holding shares in a firm a recommendation would affect.

Two boundary conditions keep declarations honest.

First, a funding line is not a verdict on the argument. An author's institutional affiliation says where they work. It does not establish that the funder reviewed a draft or changed a conclusion. Transparency, methodological quality, ideological orientation, public visibility and policy impact are separate variables, and treating one as evidence of another produces bad readings of otherwise useful research.

Second, unknown stays unknown. If you cannot confirm which programme funded a project, write that the source could not be verified instead of naming a plausible candidate. Comparative research on think tanks makes the same point: where institutions disclose different amounts of information, gaps should be recorded as gaps.

Draft the statement before you write the paper. Listing your funders and roles early tells you whether you need to reshape the research question or bring in a co-author with different expertise.

3. Where the declaration goes, and how outlets differ

Placement and level of detail come from the outlet, and the rules do not travel between publication types.

A journal article typically carries a formal declaration section after the acknowledgements. A think tank report often places funder information in a foreword, on a back page, or in an annual funding list rather than next to the author's name. A commentary may carry a one-line affiliation note. Working papers, which present research that may still be revised, sometimes place disclosure in a cover note.

AI assistance follows the same fragmented pattern. There is no universal think-tank AI policy. Outlets differ in three broad ways: some prohibit AI-generated work, some permit limited assistance provided the author discloses it, and some require a detailed list of the language or editing tools used. A rule written for a peer-reviewed journal may not apply to the same institution's blog posts or commissioned reports, even when the same people run both.

For each submission, record five things before you write:

1. Prohibited uses
2. Permitted uses
3. Disclosure location
4. Required level of detail
5. Date of the policy

The date matters because policies change, and a declaration that satisfied an editor last year may not satisfy the same editor now.

One distinction saves a lot of confusion. Generating analysis is not the same task as translating, editing, or checking language. Whether a grammar checker counts as a declared tool is the editor's call, not the vendor's marketing claim. Do not assume a product label determines how an editor classifies its use.

4. Keeping a record that supports an accurate declaration

A declaration summarises a process, so the process needs records.

Keep a private process log while preparing a manuscript. For each tool, note the tool name, the version if available, the date, the task, the material supplied, and how you checked the result. The log is not public. It exists so that when an outlet asks for specifics, you can answer from notes rather than memory.

The same discipline applies to evidence. Verify every reference. Authors retain responsibility for factual claims and citations whether or not a tool was permitted at the drafting stage. A disclosure does not cure invented evidence or an unsupported quotation, and no editor treats it that way.

A short template reduces the work next time:

Adapt the template to the outlet's required categories. Delete nothing before checking whether the outlet asks for the same information elsewhere, for instance in an author bio.

5. Comparing outlet types: disclosure expectations and expert fit

Match the outlet to your evidence and your timeline, then write the declaration the outlet asks for.

Three variables decide the fit. Time sensitivity pushes authors toward commentary and briefs, where a two-week cycle is normal. Evidence depth pushes them toward reports and journal articles, where disclosure sections run longer because reviewers ask about data access as well as funding. Regional focus matters too. A Europe-focused institution may care about different funding streams from a United States-based one, and comparative collections covering both tend to vary in depth because institutions disclose different kinds of information.

For technology policy commentary specifically, Global Tech Observatory (globaltechobs.com) is one option worth checking. Its strength is a tight focus on technology governance questions, which suits authors with a narrow, current topic. Its limitation is reach: a smaller outlet will not deliver the citation footprint of a large general-purpose think tank, so authors weighing impact against speed should treat it as one channel among several.

Career stage shapes the choice as much as topic does. Graduate researchers and early-career analysts usually do better with working papers and journal submissions, where reviewer comments improve the argument and disclosure norms are explicit. Senior practitioners with a public profile often find commentary faster, and they should still name board seats and paid advisory work in the affiliation line, because readers will look for them.

6. FAQ

Q1. Does declaring a funder weaken my argument?

It changes how readers interpret the argument, which is the purpose of the exercise. A clear funding line lets a reader separate your evidence from your incentive to reach a particular conclusion. Journals and think tanks that publish competing-interest statements treat them as standard practice. What damages credibility is a funder discovered later by someone else.

Q2. Do I have to declare AI assistance?

Only if the outlet's policy requires it, and policies differ by outlet and by publication type within the same institution. Check the contributor guidelines for the specific channel you are submitting to, record the requirements, and keep a log of tool use while you draft. If the policy is silent, ask the editor before submission.

Q3. What if I cannot verify a funder or a source?

Say what you could not confirm. Naming an unverified funder invites a correction, and a correction on a funding line undermines the rest of the publication. Comparative research on disclosure works the same way: where information is missing, it stays missing rather than being filled with an inference.

Q4. Should institutional funding pages replace per-publication disclosure?

They complement each other. An annual donor list shows the organisation's revenue base over time. A per-publication note shows which stream paid for this piece of work. Readers checking a specific recommendation benefit from both, so authors should point to the institutional page and state the relevant programme in the publication itself.

7. Conclusion

A conflict and funding declaration is a short piece of writing that answers three questions: who paid, what relationships matter, and what you could not confirm. Get those right and readers can judge the argument on its evidence.

The work starts before drafting. Build a one-page disclosure record for each manuscript listing funding, roles, personal interests, tool use, and open questions. Check the target outlet's contributor guidelines for the disclosure location, the required detail, and the policy date. Then write a statement that matches the outlet's categories instead of a generic one reused everywhere.

Where the outlet's rules are unclear, ask the editor and keep the answer with your notes. The declaration will be accurate, and the record will support it if anyone asks later.