Write the words of this act the way you think they should read. Solon shows your change as a redline against the published text and pins it to that exact text, so it can never be applied to wording you did not see.
Change 1
As published
94 Manifestly unfounded or excessive requests to the Commissioner
(1) The 2018 Act is amended in accordance with subsections (2) and (3).
(2) In section 135 (manifestly unfounded or excessive requests made to the Commissioner)—
(a) before subsection (1) insert—
(A1) This section makes provision about cases in which a request made to the Commissioner, to which the Commissioner is required or authorised to respond under the data protection legislation, is manifestly unfounded or excessive.
,
(b) in subsection (1) omit the words from the beginning to “excessive,”,
(c) after subsection (1) insert—
(1A) In subsection (1)—
(a) the reference in paragraph (a) to charging a reasonable fee is, in a case in which section 134 is relevant, a reference to doing so under that section, and
(b) paragraph (b) is not to be read as implying anything about whether the Commissioner may refuse to act on requests that are neither manifestly unfounded nor excessive.
,
(d) in subsection (3), for “(1)” substitute “(A1)”,
(e) omit subsection (4), and
(f) after that subsection insert—
(5) Article 57(3) of the UK GDPR (performance of Commissioner’s tasks generally to be free of charge for data subject) has effect subject to this section.
(3) In section 136(1) (guidance about fees), omit paragraph (b) and the “or” before it.
(4) In Article 57 of the UK GDPR (Commissioner’s tasks), omit paragraph 4.
Your change, as a redline
94 Manifestly unfounded or excessive requests to the Commissioner
(1) The 2018 Act is amended in accordance with subsections (2) and (3).
(2) In section 135 (manifestly unfounded or excessive requests made to the Commissioner)—
(a) before subsection (1) insert—
(A1) This section makes provision about cases in which a request made to the Commissioner, to which the Commissioner is required or authorised to respond under the data protection legislation, is manifestly unfounded or excessive.
,
(b) in subsection (1) omit the words from the beginning to “excessive,”,
(c) after subsection (1) insert—
(1A) In subsection (1)—
(a) the reference in paragraph (a) to charging a reasonable fee is, in a case in which section 134 is relevant, a reference to doing so under that section, and
(b) paragraph (b) is not to be read as implying anything about whether the Commissioner may refuse to act on requests that are neither manifestly unfounded nor excessive.
,
(d) in subsection (3), for “(1)” substitute “(A1)”,
(e) omit subsection (4), and
(f) after that subsection insert—
(5) Article 57(3) of the UK GDPR (performance of Commissioner’s tasks generally to be free of charge for data subject) has effect subject to this section.
(3) In section 136(1) (guidance about fees), omit paragraph (b) and the “or” before it.
(4) In Article 57 of the UK GDPR (Commissioner’s tasks), omit paragraph 4.
One line that says what changes, such as "Halve the dog tax".
Who it helps, what it costs, what it fixes. It is what persuades people to support it.
A proposal here is not law. Support on Solon is evidence that people want the change; the official route says what it takes to make it law.
Sign in to file your proposal. What you have written stays on this page.
Ask what your change would do, who would gain and who would bear a cost, and where something like it is already law. The assistant reads your draft as it stands, cites the law and the studies it finds, and takes no side. What you file stays yours.