Cost rises with the negotiation needed to clarify or adjust the role's duty split, and with any additional review required if the case needs reframing toward a different classification. Ask for an estimate that reflects this specific uncertainty rather than a flat rate for a standard systems analyst filing.
Price the classification review specifically
A role where the employer can quickly confirm a clear analyst-weighted duty split costs less to prepare than one requiring back-and-forth to adjust responsibilities or consider a different approach. Ask what the estimate assumes about the outcome of the duty review and what changes if the role turns out to be primarily programming work. Confirm current government fees separately from this classification and preparation work.
Two categories of expense are routinely left out of an estimate. The first is the employer's own effort: a manager's time producing an honest breakdown, an internal review of the wording, and the wait for an authorised signature in an organisation where that authority sits outside the hiring team. None of it is invoiced and all of it consumes the calendar.
The second is the cost of proceeding on a description that does not hold, since a reconsidered position is not the same as a fresh start — the account already given is part of the history. Hypothetical example: an architect's employer treats the duty breakdown as an administrative task, delegates it to someone who has never seen the team work, and pays twice: once for the review of a description that did not survive, and again for the version that should have been produced first.