Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RAD FAQ: New reporting scenarios (stage 1) #3756

Closed
2 tasks done
Tracked by #138
bmathesonFEC opened this issue May 14, 2020 · 8 comments
Closed
2 tasks done
Tracked by #138

RAD FAQ: New reporting scenarios (stage 1) #3756

bmathesonFEC opened this issue May 14, 2020 · 8 comments

Comments

@bmathesonFEC
Copy link
Contributor

bmathesonFEC commented May 14, 2020

Summary

Some reporting advice in the RAD FAQ is not represented elsewhere on fec.gov. New reporting examples is a solution, but for the sake of expediency and getting the transition page down, I suggest making a lighter version of reporting examples for this content (named Reporting Scenarios) as an MVP. Add tickets to upgrade the reporting scenarios to reporting examples in future work.

Example Scenario
Reporting Requirements Y Y
Screenshot Y N
Real world details (date, amount, name, etc) Y N
FECFile Y Y
PDF link Y Y
YouTube link Y Y

(A reporting scenarios will have most of the same information as a reporting example, without the transaction details and screenshot).

Here are the issues I identified as needing to be added as a reporting scenario:

  • Reporting a refund made (PAC, Party)
  • Receipts from a federal candidate committee (Party)
  • Proceeds from the sale of assets (PAC, Party, Candidate)

Related issues

Completion criteria

  • Create draft of reporting scenarios listed above.
  • Submit to RAD managers for review.

Future work

Create a ticket to upgrade reporting Scenarios to Reporting Examples.

@bmathesonFEC
Copy link
Contributor Author

Started with the simple step of moving "refund contributions" from the disbursement reporting example section to the "receipts" section in the PAC, SSF, and Party guides. The example was written for refunds received for contributions made by the committee. That satisfies one of the requests generated by the RAD FAQ review but it does mean we don't have an example for refunds issued by the committee. I'm adding that reporting scenario for each of the committee types.

@bmathesonFEC
Copy link
Contributor Author

Started drafting reporting scenarios for each of the scenarios in this ticket. Nothing ready for review yet, work will likely push into the weekend, but the RAD manager review period will likely be relatively short.

@bmathesonFEC
Copy link
Contributor Author

At the end of 12.4 four reporting scenarios have drafts:

  • refunds issued (PAC, SSF, Party)
  • contributions received from federal candidates (party)

Still in progress:

  • sale of assets (pac, ssf, party, candidate)

I am removing publication as a completion criteria from the scope of these tickets. I will add it to a new ticket for 12.5 for publication and adding the links to the committee guide filing reports page for each filer type. (#3801)

@bmathesonFEC
Copy link
Contributor Author

Several reporting examples are with RAD managers for review, but the sale of assets examples are still in draft progress. I discovered that the nature of the party example would be slightly different than the PAC and Candidate examples so that slowed down the process.

@bmathesonFEC
Copy link
Contributor Author

All of the new reporting scenarios are now with RAD manager for review.

@bmathesonFEC
Copy link
Contributor Author

Made edits based on RAD manager review, the content is back with them for a second review, will closed when feedback is received.

@bmathesonFEC
Copy link
Contributor Author

Finalized edits from RAD managers, sent to content team for a second pair of eyes review.

@bmathesonFEC
Copy link
Contributor Author

Incorporated edits from content team ready for publication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants