About Solution Reports

Last Updated: October 7, 2026
Contents

Solution Reports are PFN’s flagship publication. PFN aims for Solution Reports to have a consistent structure with consistent labeling and to include the key substantive features that will help make them next-level content. In addition, PFN believes that projects to develop Solution Reports should meet certain baseline requirements to assure that diverse viewpoints are considered, expressed, and acknowledged without bias. PFN expects the structure and baseline requirements will change as PFN gains more experience developing Solution Reports.

In this document, PFN summarizes the Report structure and key components of the baseline project requirements so that the Participants and others developing Solution Reports, and the people reading them, can see how they are made and what they are expected to address.

Capitalized terms that this document does not define have the meanings given in the PFN Glossary. See Related Content below.

What a Solution Report Does

Each Solution Report presents a policy solution developed by the Network Group that covers the Domain containing the solution. In some cases, more than one Network Group may contribute to a Solution Report, such as where the solution or parts of it fall within two or more Domains. The solution presented may be simple or complex, narrow or broad. A Network Group may develop several Solution Reports with different, even inconsistent solutions, even though they’re on the same policy topic.

Each Solution Report should present the framework and features of the solution as directly, consistently, coherently, and transparently as possible, including not only the aspects that are core to the solution, but also those that may be less important or optional. A Solution Report should present the vision, values, assumptions, and context around the solution; how the solution would work; what it would accomplish; the arguments for and against it; the alternative solutions; and the arguments for and against the alternatives. A Solution Report should be transparent about the options, pros and cons, tradeoffs, uncertain and unsettled factors, and the nuances and considerations that reveal its depth of thought. It should also discuss how its solution, arguments, and alternatives might be improved. And reflecting the views and input of genuine proponents of the primary and alternative solutions on these various items is essential.

PFN expects most Solution Reports to run roughly 20 to 50 pages, depending on the breadth and complexity of the solution.

Each project to develop a Solution Report should have one or two Solution Report Leaders, responsible for making the substantive and organizational decisions needed to make sure the Report effectively presents its policy solution, and for encouraging the constructive collaboration of all Network Group Participants, including those with different viewpoints. A Network Group Leader, or the PFN Leader, may serve as a Solution Report Leader.

When accessing viewpoints beyond those held by Network Group Participants is important to producing a PFN Solution Report, PFN may take steps to bring in people who genuinely hold the missing view, such as PFN Collaborators or outside proponents who will share their views and review how their views are stated by others. PFN may also undertake additional research to collect the written and verbal statements of viewpoint proponents that PFN cannot work with directly. In addition, PFN might encourage Participants to apply techniques and mindsets that might provide some assistance, such as steelmanning, devil’s advocate discussions, and red team review, though some of these techniques may not work well without including people who actually hold the views. PFN may also direct that the resulting Report explicitly describe alternatives, disagreements, choices, and uncertainties. See About Constructive Collaboration.

What a Solution Report Doesn’t Do

A Solution Report should not be a transcript or record of the Participants’ discussions; a consensus or compromise among Participants with different views; an implied endorsement of the solution and arguments by PFN, the Network Group, its Participants, or the Solution Report Leaders; or an advocacy piece. Also, a Solution Report should not focus on current policies and programs or on current problems, challenges, or shortcomings.

A Solution Report should not attribute individual perspectives or arguments to individual Participants. A Report will typically be the work of many Participants of a Network Group over months, so attribution would misdescribe who contributed what. In addition, PFN expects Participants to make contributions to views and arguments that they may not agree with, so contributing with or without attribution should not be understood as endorsing and favoring. Finally, attribution, even when it’s implicit, would also cut against the PFN Code of Conduct and the Chatham House Rule, which encourage Participants to think out loud and change their minds.

A Solution Report should not devote significant time or space to effective dates, transition issues, government relations strategy, or matters such as political feasibility, unless they are core to the solution, in which case they should be covered in a separate section or even a separate Report.

Baseline Requirements for Solution Report Projects

Every Solution Report project must meet the same baseline requirements, whatever the size of the Network Group and however varied the views within it. A Group with more Participants holding more different views does not do less of this work, but is able to do some of the steps more easily and will be able to undertake some valuable activities that go beyond the baseline requirements.

Here are the major baseline requirements for a Solution Report project, up to the point of the final reviews and approval for publication:

  • A solution inventory. Before drafting begins, the project lists every live solution on the topic, stated as its proponents state it, with the organizations and people who hold each one. Solutions are not collapsed into two sides, and the No-Change Solution is always included.
  • Pre-commitment. Before the research begins, the project records how it will compare the solutions, including which criteria matter most, and what evidence would change its assessment of each solution. The comparison standards may change as the project develops.
  • Short solution statements. For each solution in the inventory, a short statement covering the solution, its arguments, and its track record (if any) is prepared based on what it’s own proponents have written or expressed (not on how others have characterized it). The short statement should also include the primary counterarguments based on what proponents of the counterarguments have written or expressed.
  • A check by a proponent. The Report’s short statement of each solution is checked by someone who is a proponent of that solution and did not write the statement, whether that person is a PFN Participant or from outside PFN. This may be done through indepth research of written and verbal statements of solution proponents.
  • Primary Alternative Solutions. Identify the Primary Alternative Solutions that will be addressed in the Report. The No-Change Solution is always one of the Primary Alternative Solutions.
  • Additional research. Undertake additional research for the Report’s solution and for each Primary Alternative Solution, including as appropriate discussions with outside experts.
  • Full solution statements. Draft a full statement for each Primary Alternative Solution, including arguments, counterarguments, evidence, priorities, pros and cons, tradeoffs, and the like. After the Primary Alternative Solutions, draft a full statement of the Report’s solution.
  • Test the Solutions. Compare the Report’s solution and each Primary Alternative Solution against the pre-committed criteria the project recorded before the research began, with every criterion addressed for every solution and the evidence cited in each case. Also, test the Report’s solution and the Primary Alternative Solutions against several key “stress tests”: (a) under the premortem test, assume the solution was adopted and failed badly five years later and then write the postmortem; (b) under the key assumptions check, identify what assumptions have to be true for the solution to work and ask of each assumption what supports it, what would falsify it, and what changes if it is wrong; (c) under an explanation check, describe step by step how the solution would produce its intended result (a chain that goes vague makes the Report less certain); and (d) under a “consider the opposite” test, ask of each study the project relies on what the project would have concluded had the result come out the other way.
  • Draft final Report. Convert the full statements and additional information gathered about the Report’s solution and each Primary Alternative Solution into a draft final Solution Report.
  • Counterarguments. Each significant counterargument to the Report’s solution or a Primary Alternative Solution is answered in the Report, or the Report says why it is not.
  • Verification. Verify every Factual Claim and citation in the draft final Report. And review all analyses and interpretations to assess their thinking and expressions.
  • Right of reply. Before finalizing the Solution Report, each organization or person whose solution the Report describes is given the relevant passage and invited to correct how their Position is characterized.

Many of these baseline requirements reflect PFN’s constructive collaboration techniques for Solution Report projects. See About Constructive Collaboration.

If a Network Group has more Participants with different views, then it may be possible to accomplish some of the baseline requirements for Solution Report projects more easily. And more importantly the project may be able to dig into some matters in more depth. For example, a Network Group’s Participants can say what proponents of a position would concede, where proponents would take different views, which arguments move and don’t move proponents, and how proponents would react to the Report’s solution.

Review and Publication

Before publication of any Solution Report, qualified reviewers must verify its Factual Claims, including cited sources, and its Analysis and Interpretation statements. See About PFN Content and Statement Types. When possible, a near-final version should also be reviewed by someone who disagrees with it.

Also, the Network Group Leader and the PFN Leader must review and approve each Solution Report before publication. If the Network Group Leader does not believe that a Report should be published, PFN does not publish it unless the PFN Leader believes that it should be published.

Their review and approval assessments should be based on adherence to these baseline requirements, on the Report structure guidelines set forth in the next section of this document, and on other PFN policies and guidelines. The questions are these: Does each solution rely on statements by its own proponents? Was the statement of each solution checked by a proponent who did not write it? Are significant counterarguments answered, or is the silence explained? Has the right of reply been extended? Has every Factual Claim and citation been verified? And has any other requirement gone unmet? In some instances, the failure to meet a requirement may not result in the denial of approval, provided the failure is disclosed in the Report.

Solution Reports are credited as authored under PFN oversight by the Network Group Participants who made meaningful contributions to the ideas, thinking and other intellectual aspects of the Reports. A Report’s Leaders are typically credited as authors, subject to each person’s attribution election, and recognition may extend to other Participants who made significant contributions.

In PFN, authorship credit is distinct from copyright ownership, as copyright does not protect the ideas, thinking, and other intellectual contributions to the Reports. Instead, copyright ownership is tied to the human-generation of the words, visuals, and other means of expressing (and organizing) the intellectual contributions. Typically, PFN’s copyright in a Solution Report comes mainly through the PFN Writer, where the Writer assigns the copyright in the writing to PFN.

Completed Solution Reports are publicly available under the PFN Content License, which lets anyone republish or adapt them with credit. PFN asks that Reports be republished in full rather than in part, because a single solution presented alone misrepresents what PFN does.

See the PFN Glossary, the PFN Content License, and the Participant Agreement.

Solution Report Structure

This section describes how the Report should be organized and what the Report itself says about this work, including how the different views were developed, which solutions are untried, and where the evidence behind the solutions is unequal.

Each Solution Report should have several sections: an executive summary, the solution, the analysis, and the limits, plus additional items if useful. It should also include generic front matter and back matter.

Front Matter

  • Title. The title should describe the solution, not the problem. It should reflect a view, rather than being neutral. For example, “Indexing the Retirement Age to Cohort Life Expectancy” is preferable to “The Future of Social Security.”
  • Subtitle. A subtitle, optional, should provide a bit more audience-relevant information about what the Report does.
  • Byline. The byline should include the Solution Report author or authors and other key contributors, including the responsible Network Group. PFN authorship follows intellectual contribution, not drafting, subject to a Participant’s attribution election.
  • Publication date.
  • Acknowledgements and Version History pointer. A sentence or two directing readers to the Acknowledgements section for more on contributors, disclosures, content type, the PFN Content License and CC BY terms, and a suggested citation, and to the Version History section.

Executive Summary

The executive summary should be written for a reader, particularly a policymaker, who is likely to read nothing else. It should be no more than one page, should be written in plain language toward the end of the project by the best writer available, and is likely to be revised many times before it is finalized.

The summary should present the Report’s solution in three or four plain sentences that avoid empty rhetoric and any impression that the Report is an advocacy piece. It should describe what the solution would accomplish, the two or three strongest arguments for it, the two or three strongest arguments against it and how the Report answers them, including where it does not, the Primary Alternative Solutions, and a pointer to key related content. It should not make any point that is not in the full Report.

The Report’s Solution

This section should present the Report’s solution, its framework, and its main features. It should not focus on current policies and programs or on the problems and challenges driving the need for solutions. It should set out the solution’s vision, values, and goals, and the priorities among them where they conflict. It should provide detail about the solution’s assumptions and context, how it would work, what it would accomplish, and who and what would be affected and how. It should describe the solution’s main limitations, including the goals and changes it would not accomplish. Where the authors faced choices and uncertainties, this section should explain how the Report addresses them, what choices it made, and why, including where it did not resolve them. The Report should present the thinking behind these decisions transparently.

Analysis

This section should present the arguments for the Report’s solution, whether or not they are easy to defend. It should explicitly and separately describe the supporting assumptions, context, facts, evidence, analysis and interpretations, and values, including the strength or weakness of each.

Participants with different views may believe that some arguments are stronger and others weaker, or that certain modifications would make the solution and its arguments stronger. Those perspectives should be included.

This section should also describe the primary assumptions, facts, evidence, analyses and interpretations, and values that run counter to the solution, what changes should be considered to make the solution more acceptable to Participants who disagree with it, and the arguments for those changes.

This section should also present the Primary Alternative Solutions, with the arguments for and against them, how they would differ, and what they would accomplish. The No-Change Solution should be one of the Primary Alternative Solutions in every Report, analyzed in full, with its own case and its own costs, rather than serving as the baseline for the others.

Each Report should also include the following. Each of them is short, and each answers a question a reader can otherwise only guess at.

  • Whether each solution has been tried. For the Report’s solution and each Primary Alternative Solution, whether some version of it has been put into effect, where, and what happened, or a statement that it is untried.
  • A statement of evidence weight. Where the evidence behind the solutions is unequal, say so plainly, separately from the fair statement of each. Presenting positions fairly does not mean presenting them as equally supported.
  • Responses to counterarguments. The significant counterarguments the project collected, each with the Report’s response, or a statement of why the Report does not answer it.
  • How the different views were developed. About half a page: what sources each position rests on, including the Report’s solution; who stated each position; and who checked that statement, including whether that person was a PFN Participant or from outside PFN.
  • Where the solution could have gone another way. The design and framing choices that could reasonably have gone differently, with the reasoning.

The Network Group developing a Solution Report may choose to present the strongest counterarguments to the Report’s solution before the case for it, rather than after. A reader who meets the counterarguments first is less likely to have the terms of the question set by the case.

Here are some additional guidelines that relate to the Analysis section:

  • Strive to state and cite explicitly the facts, evidence, analyses, and interpretations that cut against the solution. Every characterization of an opposing or different view should be one its proponents would recognize as their own.
  • Present the counterarguments, alternatives, and their supporting arguments based on strong versions of those views, with cited sources as appropriate. Do not present generic or weak versions of alternatives and objections.
  • Present at least one counterargument and one alternative that the Report does not fully answer. If every counterargument is neutralized in the Report, particularly if they are neutralized by weak points, the Report should say why.
  • Do not let the counterarguments be conspicuously thinner than the case for the solution. The counterarguments and alternatives should be sourced and developed with the same care. If a Report’s counterarguments are weak, the Report should say why.
  • Strive to identify at least one meaningful improvement from a different view that was either included in the solution, considered and rejected, or should be considered in the future. Describe the thinking behind it.
  • Avoid explaining different views by reference to the interests, incentives, or motives of the people who hold them. Focus on the view and its ideas and arguments, not the people, even if an opponent’s motive is real.
  • Try to acknowledge when a counterargument or alternative view rests on different assumptions or different values, rather than on a factual error or a difference in analysis and interpretation.
  • Cite sources by people with different and even conflicting views.
  • A Report should not describe itself as balanced, rigorous, comprehensive, or fair.
  • Make sure the Report is reviewed by at least one person whose views differ from the views described in it.

Limits

This section should describe the limitations that apply to a Report and its solution. Does it depend on assumptions that should be stated explicitly, and how would the solution and its likely effects change if those assumptions are wrong? What if the supporting evidence is uncertain or unsettled? What does the Report fail to address?

This section should also cover two things about how the Report was made. First, viewpoint coverage: which positions had no proponent to check the Report’s statement of them, and what that probably costs the Report. Second, any change during the project to the criteria for comparing the solutions, or to what the project said would change its assessment, with the original, the change, and the reason.

This section should also address what evidence, development, or other circumstance might lead the proponents of the Report’s solution to abandon or substantially revise their views. This should say a lot about the thoughtfulness and seriousness of the work. A Report shouldn’t say “new evidence”; it should say something like “publication of a study finding no effect on labor supply.” If people with different views would be moved by different changes, the Report should say so. And as noted above, if a different view is more about values than evidence, the Report should acknowledge that nothing empirical or analytical would make a difference. A Report should honestly and transparently set out the real thinking around the solution.

Additional Items

A Solution Report may include additional information that will improve the Report for policy experts and policymakers. Examples include legal and constitutional considerations, effective dates and transition rules, and political feasibility and strategy. Some of these should be included with caution, since a Report should focus on its long-term policy vision and solution and not be sidetracked because a solution might have short-term complexities and difficulties.

Back Matter

A Report should satisfy PFN’s general content policies on Endnotes, Acknowledgements, including the PFN Content License terms and a suggested citation, and Version History. In particular, the Acknowledgements should address the use of generative AI in the development and writing of the Solution Report. See About PFN Content and Statement Types and About Using Generative AI.

PFN Content. About Constructive Collaboration · About Domain Overviews · About Network Groups · About PFN Content and Statement Types · About Using Generative AI · PFN Content License ·PFN Glossary.

Acknowledgements

Contributors. Harry Conaway (PFN Leader) is the author and writer of this content and is solely responsible for its substance.

Disclosures. Claude (Opus 5.5, Anthropic) was used to assist in editing this content. All substantive and writing decisions were made by the author and writer noted in the Contributors section above.

PFN Content Type. This content is classified as PFN about and governing content, and thus is not subject to PFN’s Content and Statement Types policy for substantive policy content.

Version History

Current Version. To be added