Treat the description as an operating agreement

A job description can be grammatically clear and operationally weak. Phrases such as “support administration” or “manage all program requirements” leave unanswered questions about scope, authority and priorities. Different people may read the same sentence and expect different work.

Arcus recommends treating the document as an agreement about the role’s contribution within the administration. It should connect purpose, accountabilities, decisions, working relationships, capability and conditions. The document should also be consistent with the organization chart, approved policies and actual resources.

This is more than a recruitment exercise. The same role definition informs orientation, supervision, development, compensation analysis and performance review. If these activities use different assumptions about the job, confusion can persist even after a successful hire.

A description does not create capacity. Where the work is unmanageable or authority is unresolved, rewriting the document should expose the decision needed rather than make the problem appear settled.

Understand the work before drafting

Review the service or organizational purpose of the role. Speak with the accountable manager, current employee where appropriate and colleagues who rely on its work. Examine recurring outputs, decisions, deadlines, service commitments and responsibilities that have accumulated informally.

Distinguish the current job from the desired future job. If leadership wants the position to spend more time on planning and less on routine processing, identify who will take over the processing and what support is required. The description should reflect an approved operating choice, not an aspiration that nobody has resourced.

Separate the role from the particular strengths or habits of its incumbent. An employee may provide exceptional expertise beyond what the position requires. Conversely, a task may be essential even if the current employee has not been able to perform it consistently.

Use external examples as prompts, not as finished answers. A description from another Nation or organization may assume a different team, budget, service model or delegation structure. Copying it can import responsibilities and qualifications that do not fit local needs.

Record unresolved questions during the analysis. If two managers disagree about who owns a result, obtain a decision before embedding conflicting expectations in the final document.

Write accountabilities that identify a contribution

Begin with a short purpose statement describing why the role exists and the result it supports. Then organize major accountabilities into coherent areas. Avoid an unranked inventory of every task the employee might perform.

Use precise verbs that reflect the intended level of responsibility. Preparing an analysis, recommending a decision, approving expenditure and implementing an approved action are different accountabilities. A vague verb such as “manage” may hide these distinctions.

Consider a hypothetical statement: “Responsible for program reporting.” A clearer version could be: “Prepare the program’s monthly activity and expenditure report, reconcile information with Finance, explain material variances and submit it to the program director for review by the agreed deadline.” This describes an output and an interface without implying authority to approve the report externally.

A second example is “Handle community concerns.” A more useful statement might specify receiving and documenting service concerns, coordinating responses within approved policy and escalating matters outside delegated authority. The Nation should define the actual escalation route and confidentiality requirements.

Keep the document readable. Detailed step-by-step instructions belong in procedures that can be updated as systems change. The job description should remain clear about the result and accountability even when the method evolves.

Clarify decisions and working relationships

State the primary reporting relationship and any functional guidance the role receives. Where several programs depend on the employee, identify who resolves competing priorities. Multiple stakeholders should not become multiple uncoordinated supervisors.

Describe important decision boundaries: what the role can decide, what it recommends and what requires approval. Refer to the appropriate delegation policy for detailed thresholds so that the description does not become inconsistent when those thresholds change.

Identify key interfaces with other roles. For a program manager, this might include Finance’s responsibility for accounting controls, HR’s support for employment processes and leadership’s authority over strategic priorities. Clarify who prepares, reviews, decides and communicates at the main handoffs.

Do not assign accountability for results that depend entirely on decisions or resources the role cannot influence. Where responsibility is shared, explain the contribution expected from this position and the escalation process when dependencies are not met.

Check necessary separation of duties. A description should not accidentally combine preparation, approval and independent review in a way that undermines the Nation’s controls. Small organizations may need practical alternative review arrangements, approved through the appropriate process.

Choose qualifications that match the work

Identify the knowledge, skills, experience and credentials needed for essential responsibilities. Separate requirements needed on entry from capabilities that can reasonably be developed with support. State when equivalent combinations of education and experience can be considered under the Nation’s policies.

A credential should have a clear relationship to the job. Some work requires specific professional qualifications; other work may be performed effectively through relevant experience and demonstrated capability. Inflating requirements can narrow the candidate pool without improving the match.

Describe relationship and communication capabilities in observable terms. For example, the role may need to explain options clearly, work respectfully with community members and follow the Nation’s protocols. Avoid vague personality labels that are difficult to assess consistently.

Include relevant working conditions, travel, hours, availability and the nature of the work. Distinguish essential results from one assumed method of achieving them, and use the Nation’s appropriate process for accessibility and accommodation questions. Avoid adding unnecessary personal characteristics to the role profile.

Review the combination of requirements and compensation. A broad technical and management mandate paired with a narrow administrative pay assumption may signal a design or classification problem. The description provides evidence for that review; it does not determine the answer by itself.

Decide whether to clarify, redesign or separate the role

Clarification may be sufficient when the work is coherent and adequately resourced but expectations are poorly documented. The main effort is confirming accountabilities, interfaces and decision rights.

Redesign is more appropriate when the role contains conflicting priorities, excessive breadth or tasks that belong elsewhere. It may involve changing handoffs, simplifying processes or reallocating responsibilities. Assess the effects on other positions before finalizing the description.

Separating a role may be justified where distinct functions require different expertise, independent review or more capacity than one position can supply. It creates additional cost and coordination requirements, so the case should be based on demand and operating needs rather than the number of headings in the document.

A phased approach can address urgent clarity while a larger design decision is prepared. State what is interim, who owns the unresolved issue and when it will be reviewed. Do not present a temporary workaround as a settled permanent mandate.

Budget the review and the resulting changes

Document development uses employee, manager and HR time. Implementation may also require training, revised procedures, compensation review or additional staffing. Keep the cost of writing the description separate from the cost of making the proposed role work.

For a hypothetical eight-role review, assume each role needs two employee hours, three manager hours and three HR or analyst hours. That is 64 hours. Add a twelve-hour cross-role validation workshop and preparation allocation, producing 76 hours before approval and implementation.

If external facilitation costs an illustrative $6,000, show that cash expense separately from existing staff capacity. If the review identifies a need for a new position or a compensation adjustment, present the continuing cost as a separate decision. The $6,000 writing and facilitation budget does not finance those commitments.

Prioritize descriptions with significant consequences: difficult recruitment, changed responsibilities, unclear authority or repeated handoff failures. A staged review can be more practical than rewriting every role simultaneously while operational questions remain unresolved.

Maintain a review trigger for material changes to services, systems or delegations. A short update at the right time can prevent a larger gap between documented and actual work.

Validate the description through a practical scenario

Before approval, walk through a realistic decision or service request. Ask who receives it, who gathers information, who decides, who communicates and who checks completion. If the proposed description leaves a gap or duplicate responsibility, revise the design.

Review the draft with the employee and relevant managers, then obtain approval through the Nation’s established process. Explain material changes and address any employment or compensation implications through the appropriate professional and policy channels.

Use the approved description during orientation and regular performance discussions. Track whether recurring misunderstandings, inappropriate escalations or recruitment mismatches diminish. If problems continue, consider whether the issue is workload, supervision or resources rather than wording.

A better job description earns its value when people can use it to coordinate work and make decisions. Its success is measured in clearer accountability and a more workable role, not in the length of the document.

Evidence and source notes

1. FNHPA, Job Description and Compensation Development study, findings, page 8.
2. Government of Canada Job Bank, Hire employees, job-analysis and description guidance. Reviewed through indexed official text because direct retrieval failed.

Research reviewed October 18, 2026. Role statements and resource estimates are hypothetical examples. The six tests are original Arcus management analysis and should be applied within the Nation’s authority and policies.