CLERK2OFFICER · CAIIB ABFM · THE MANAGEMENT PROCESS

Organising

P3-A03 · 2,659 teaching words · 25 explained questions

Module A contentsPrevious chapterNext chapter

Module A review edition · 8 November 2026. Fictional cases; not affiliated with IIBF. Academic approval remains pending.

1. Turn a plan into coordinated work

Organising arranges activities, people, resources and authority so that an organisation can pursue its objectives. A plan can identify a desirable result, but implementation requires decisions about who does what, how work is grouped, where decisions are made and how departments cooperate. Organising is therefore more than drawing boxes on a chart. The structure should support the work, establish accountability and enable information to reach the people who need it. It also needs review when products, customers or operating conditions change.

Consider fictional Meridian Bank's Riverside branch. The manager plans to shorten the time taken to process small-business applications while maintaining proper checks. Applications pass through customer service, credit appraisal, documentation and disbursement. If each team works efficiently in isolation but no one owns the handoff, files can wait between stages. Organising the process means defining responsibilities and information flows as well as staffing individual tasks. The customer experiences the whole process, not only the part performed by the first employee.

An organisation is a group of people working through some structure toward shared purposes. Its formal structure describes authorised roles and relationships; informal relationships develop through everyday work and personal interaction. Both can affect how information moves. A formal reporting line is important for accountability, while an informal network can help an employee find a technical answer quickly. The manager should understand both without allowing informal shortcuts to replace required approvals or conceal who made a decision.

2. Understand why organising matters

Organising divides complex work into manageable activities and provides a way to coordinate those activities. It can reduce duplication, clarify decision rights and help people understand how their work contributes to an objective. A bank needs reliable coordination because customer service, risk assessment, technology, records and payment processing are interdependent. A missing document in one stage can delay several later stages. A structure is useful when it supports timely handoffs and appropriate challenge, not merely when every employee has a title.

Clear responsibility also makes control possible. If several units assume another unit will review an exception, the exception can remain unresolved. If two units independently contact the customer without coordination, information may conflict or work may be duplicated. An assigned owner does not need to perform every task personally, but someone must be accountable for ensuring that the issue reaches a decision. The structure should identify who acts, who approves, who supplies information and who is informed of the outcome.

Organising has costs and limitations. More specialisation can improve expertise but create additional handoffs. More managerial layers can support supervision but slow communication. Greater decentralisation can improve local responsiveness but create inconsistent decisions if authority and controls are unclear. There is no universally best chart. Management should choose arrangements appropriate to the organisation's purpose, size, risks and capabilities, then review their actual operation. An elegant chart does not prove that staff understand responsibilities or that the required work is being completed.

Organise a service handoffMap tasks and control purposes. Clarify decision rights and limits. Track exceptions across teams.Organise a service handoff1Identify the workMap tasks and control purposes.2Assign authorityClarify decision rights and limits.3Coordinate and reviewTrack exceptions across teams.
Organise a service handoff. Map tasks and control purposes. Clarify decision rights and limits. Track exceptions across teams.

3. Follow the organising process

Start with objectives and identify the activities needed to achieve them. For Riverside's application process, activities include receiving the request, checking completeness, analysing information, obtaining approval, documenting terms and arranging disbursement. Next group related work into roles or units, assign responsibility and establish authority. Then define reporting relationships, coordination mechanisms and required resources. Finally, communicate the arrangement and review whether it works. The process is iterative: a new product or a recurring control failure may require a change in roles or handoffs.

Activity analysis should distinguish work that creates the intended outcome from duplication or unnecessary movement. If three teams collect the same information because systems do not share it, the manager should investigate whether a single reliable record can serve the process. However, independent checks should not be removed merely because they appear repetitive. A verification by someone independent can serve a control purpose. The question is what each step achieves, what evidence it produces and whether its cost and timing are appropriate.

After roles are assigned, test a case from start to finish. A customer submits an incomplete application; the receiving team identifies the missing item, communicates it clearly and records the next action. When the item arrives, the file returns to the correct stage rather than starting over without explanation. An exception, such as conflicting information, has a named escalation route. This walkthrough reveals gaps that a high-level chart may hide, including ownership during handoffs and what happens when the usual employee is absent.

4. Apply principles without treating them as mechanical laws

Division of work assigns activities in a way that can develop expertise and improve consistency. Coordination reconnects the specialised parts so that the whole process delivers its objective. Specialisation without coordination can produce a file that moves slowly through excellent individual departments. Conversely, one person doing everything may be impractical or create control conflicts. The appropriate design depends on volume, skills, risk and the need for independent checking. The aim is a workable balance rather than the maximum possible number of specialised desks.

Unity of command generally means an employee should understand the primary reporting and authority relationship for assigned work. A clear chain of command helps route decisions and accountability. In practice, projects and specialist functions can create more than one source of direction. Where that happens, the bank needs explicit priorities and escalation. An employee receiving conflicting instructions from a branch manager and a project lead should not be left to guess which objective overrides a required control or who can resolve the conflict.

Span of control concerns the number of direct reports supervised by a manager. A wider span can reduce layers but may be difficult where work is complex, staff are inexperienced or close coaching is needed. A narrower span can support attention but add cost and delay. No single number is appropriate for every branch or function. Assess the nature of the work, staff capability, geographic distribution, systems and required supervision before deciding whether a particular span is manageable.

Follow the process

No autoplay. Read each step, or use Play, Pause and Next. Reduced-motion settings remove transitions.

Identify the work

Map tasks and control purposes.

Assign authority

Clarify decision rights and limits.

Coordinate and review

Track exceptions across teams.

All steps are available above.

5. Distinguish authority, responsibility and accountability

Authority is the legitimate power to make a decision or direct action within a defined scope. Responsibility is the duty to perform an assigned activity. Accountability means being answerable for the outcome or discharge of a role. Terms can be defined differently by institutions, so explain the relationship in a case. Assigning a task without the authority, information or resources needed to perform it creates a predictable failure. Granting authority without an appropriate boundary and review can create a different risk.

For example, a credit officer may be responsible for preparing an appraisal, while an authorised sanctioning official decides within a delegated limit. The officer should not promise approval to the customer before the decision is made. The sanctioning official relies on the appraisal but remains accountable for applying the relevant authority and conditions. Operations staff may then check that documentation and pre-disbursement conditions are satisfied. Each role has a distinct contribution; a handoff does not eliminate the need to record what was done and by whom.

Accountability should not be confused with blame for every event outside a person's control. A manager can be accountable for identifying a system failure, escalating it and implementing an approved response without personally controlling the external outage. Fair assessment considers authority, information and circumstances. Equally, a manager cannot avoid responsibility for an unresolved issue simply by forwarding it repeatedly. The practical question is whether the person took the actions required by the role and made remaining constraints visible to someone able to decide.

6. Delegate with boundaries and follow-up

Delegation assigns responsibility and appropriate authority for a defined activity to another person. It can develop staff, improve responsiveness and free managers to focus on decisions that need their attention. Effective delegation states the expected outcome, decision limits, resources, reporting and escalation. The manager should check understanding and provide support proportionate to the employee's experience and the risk. Delegation is not the same as abandoning the task; the delegating manager retains the accountability established by the organisation's rules.

At Riverside, the manager might delegate preparation of a weekly service report to a trained officer. The officer can gather and analyse data but cannot alter the bank's reporting definitions or suppress material exceptions. The manager agrees a deadline and review process and provides access to the source records. If the officer discovers that waiting-time data are incomplete, the agreed escalation route allows the issue to be reported rather than hidden. The assignment is useful because authority and boundaries are clear.

Delegation can fail through excessive control as well as insufficient oversight. A manager who asks for every minor decision may remove the benefit and discourage initiative. A manager who delegates a sensitive approval beyond policy authority creates an unacceptable control gap. Select tasks appropriate to the employee's capability and the organisation's rules, monitor results and adjust support. Good delegation develops judgement while preserving clear responsibility for decisions that the manager is not authorised to transfer.

Apply the idea

A loan file is delayed between customer service and credit review. What should be clarified?
Choose an action to see feedback.
Read the suggested decision without JavaScript

Handoff owner, required information and escalation. Coordination can reduce avoidable delay while retaining checks that serve an identified control purpose.

7. Compare centralisation and decentralisation

Centralisation places specified decisions at a higher or central level; decentralisation distributes appropriate authority to lower levels or units. Central control can support consistency, specialist expertise and oversight. Local authority can improve responsiveness and use knowledge of customers or operating conditions. Both have costs. A central team may become a bottleneck if every minor matter requires approval; a decentralised system can produce inconsistent or unauthorised decisions if limits, training and review are weak.

Consider a bank's credit policy and individual customer service. The bank may set common underwriting standards centrally while allowing branches to make certain decisions within defined authority. This is a mixture rather than a choice between complete centralisation and complete local autonomy. The design should identify which decisions require specialist review, what information branches must provide and when exceptions are escalated. Local knowledge is valuable, but it does not permit a branch to ignore a bank-wide requirement or a legal obligation.

The right balance can change with technology, scale and risk. A new central system may allow faster access to reliable information, while an unfamiliar product may initially need specialist oversight. Management should examine actual outcomes: decision time, quality, consistency, customer impact and control exceptions. A structure that is fast only because it bypasses review is not necessarily effective. Equally, a control process that delays every routine decision without improving risk management deserves investigation and possible redesign within applicable authority.

8. Compare organisational structures

A functional structure groups work by expertise, such as operations, credit, technology and finance. It can develop specialist capability and consistent standards, but coordination across functions needs deliberate attention. A divisional structure groups activities around products, customers or regions, potentially improving focus on a particular market while duplicating some capabilities. A matrix combines dimensions, such as a functional reporting line and a project responsibility. Each structure creates trade-offs in decision speed, expertise, cost and accountability.

In a functional arrangement, Riverside's application may pass through several specialist teams. The bank should define handoffs and a process owner so that customer problems do not disappear between departments. In a divisional arrangement, a small-business unit may have closer customer focus but still need independent risk controls and common infrastructure. In a matrix project, employees may receive direction from both a functional manager and a project manager. The organisation must resolve priorities and explain which authority applies to personnel matters, project work and control decisions.

Structures are not permanent simply because they have existed for years. Growth, technology, regulation and customer needs can make an existing design less suitable. Before reorganising, identify the problem and evidence. A new chart will not fix a broken system, unclear policy or insufficient training by itself. Test whether the proposed change improves decisions, coordination and controls, and consider transition costs. Reorganisation should have an objective and review criteria rather than become a recurring exercise in changing titles.

Authority and responsibilityAssigned work needs evidence. A recommendation is not approval. Record the handoff and exceptions.Authority and responsibility1Prepare the caseAssigned work needs evidence.2Approve within authorityA recommendation is not approval.3Verify conditionsRecord the handoff and exceptions.
Authority and responsibility. Assigned work needs evidence. A recommendation is not approval. Record the handoff and exceptions.

9. Use charts, manuals and communication together

An organisation chart depicts selected formal relationships, positions and reporting lines. It can help a new employee understand where a role sits and where an issue may be escalated. A chart is a simplified representation: it may not show every process, informal relationship or temporary project. It should be current and consistent with actual authority. A person shown as responsible on paper but unable to obtain information or make the required decision may not be able to perform the role effectively.

An organisation manual can describe functions, responsibilities, delegated powers and procedures in more detail. It should identify the document owner, version and route for updates. Employees need to find and understand the relevant guidance, and managers need to ensure that changes reach affected staff. A manual is not evidence that the process operates as written. Training, observation, control testing and feedback help establish whether employees can apply it and whether it remains suitable when products or systems change.

Communication connects the formal design to daily work. A change in responsibility should be explained to both the receiving and sending teams, with a clear effective date and handoff. Otherwise each may assume the other remains responsible. For a customer complaint, staff should know who owns the case, what information must be recorded and when to escalate. A concise role description and a working feedback channel can be more useful than a complex chart that looks complete but leaves operational questions unresolved.

10. Recognise culture, change and conflict

Organisational culture includes shared norms and behaviours that influence how people work, especially when a written procedure does not answer every question. A bank may state that employees should report errors, but staff will observe how managers actually respond. If reporting is punished while hidden problems are ignored, the effective culture can discourage early warning. Structure and culture interact: a formal escalation route needs trust, clear authority and a response that addresses the underlying issue rather than merely the messenger.

Change can create uncertainty about roles, status, workload and skills. Explain the objective, involve affected employees where appropriate, provide training and clarify what happens to existing responsibilities. Resistance is information to investigate; it may reflect a genuine design weakness, missing resources or concern about customer impact. Not every proposed change can satisfy every preference, but management should communicate decisions honestly and provide a route for unresolved risks. A change is not complete when the new chart is published; it is complete only when the work can operate effectively.

Conflict can arise from scarce resources, unclear responsibilities, competing goals or interpersonal differences. Constructive disagreement can improve decisions when people share evidence and focus on the problem. Unresolved conflict can delay service or encourage departments to protect their own metrics at the expense of the customer. The manager should identify the cause, hear relevant perspectives, clarify authority and agree actions. Serious conduct or policy issues require the appropriate formal channel; a desire for harmony should not suppress a necessary escalation.

11. Review the Riverside design

Riverside's revised application process should show the sequence, handoffs, decision rights and exception route. A customer-service employee checks completeness, an authorised credit function assesses the request, an appropriate official decides, and operations confirms conditions before disbursement. This is a fictional teaching design, not a universal bank procedure. The manager should test a normal case, an incomplete file and a case involving absence or conflicting instructions. The walkthrough reveals whether the chart and manual correspond to the work people actually perform.

For examination questions, distinguish assigning a task from granting authority, delegation from abandonment, and accountability from unlimited personal control over external events. Compare structures by their effect on coordination and independence. When a file stalls between functions, adding another specialist may not solve the problem; clear ownership and handoff information may be more relevant. When a local team makes inconsistent decisions, consider training, boundaries and review rather than assuming that every decision must be centralised permanently.

Finally, treat organising as a continuing management activity. Monitor decision time, quality, exceptions and employee feedback; review whether the structure supports the objective; and adjust within approved authority. A well-designed organisation makes it easier for capable people to cooperate and for problems to become visible early. It does not eliminate the need for planning, staffing, directing or controlling. Those functions remain connected, and their effectiveness depends on clear roles, usable information and a culture in which staff can raise a concern before it becomes a larger failure.

25 original questions

Choose one best answer. Explanations address the answer and distractors; no negative marking.

Browser-local saving is optional.

1. Organising primarily concerns what?
Answer and detailed reasoning

Correct: C. Arranging work, resources, authority and coordination

Organising connects tasks and relationships to objectives. A chart is one representation, while targets and profit calculations do not by themselves establish decision rights, handoffs or accountability for the work.

2. A process stalls between specialised teams. What should be examined?
Answer and detailed reasoning

Correct: C. Handoff ownership and required information

Specialist work must be coordinated end to end. Separate metrics can hide waiting between teams, and removing independent checks or changing chart appearance does not establish who resolves the handoff.

3. Formal and informal organisations differ how?
Answer and detailed reasoning

Correct: A. Formal roles are authorised; informal relationships arise through interaction

Both can influence work, but formal authority establishes official responsibilities. Informal assistance can be useful without granting unauthorised approval, and a chart cannot display every relationship or communication path.

4. Why assign an owner to an exception?
Answer and detailed reasoning

Correct: A. To ensure it reaches a decision and follow-up

Ownership establishes accountability for progress, not solitary execution or perfect outcomes. Escalation remains necessary when authority or information is insufficient, and the decision should be recorded and reviewed.

5. Division of work needs what complementary activity?
Answer and detailed reasoning

Correct: C. Coordination of specialised tasks

Specialisation can develop expertise but creates dependencies. Coordination connects stages to the shared result; neither an absence of objectives nor assumptions that every handoff disappears will deliver the complete service.

6. Removing a repeated independent verification solely because it takes time may overlook what?
Answer and detailed reasoning

Correct: A. Its control purpose

A check can provide independent challenge even if another team handled similar information. Review its purpose and evidence before redesign; speed alone does not establish that the control is unnecessary or removable.

7. Unity of command generally supports what?
Answer and detailed reasoning

Correct: C. A clear primary reporting and authority relationship

Clarity helps employees understand who directs their work and resolves conflicts. Projects can involve multiple relationships, but priorities and escalation must be explicit; unity does not prohibit cooperation.

8. A matrix structure can create which practical challenge?
Answer and detailed reasoning

Correct: C. Conflicting functional and project priorities

Multiple dimensions can provide expertise and project focus but require clear authority and escalation. Accountability remains necessary, and a matrix does not automatically ensure that instructions will never conflict.

9. Span of control refers to what?
Answer and detailed reasoning

Correct: B. The number of direct reports supervised by a manager

Span concerns the supervision relationship. Its suitability depends on work complexity, capability and systems; customer population, document length and capital ratios do not define the number of direct reports.

10. A wider span is always best because it reduces layers?
Answer and detailed reasoning

Correct: C. No, complexity and coaching needs also matter

Fewer layers may improve speed, but a manager can become overstretched. Work risk, experience and geographic spread affect suitable supervision; the span can be counted but has no universal optimum.

11. Authority is best described as what?
Answer and detailed reasoning

Correct: A. Legitimate power to decide or direct within scope

Authority comes from an authorised role or delegation with boundaries. Responsibility concerns assigned work, and neither preference nor a job title gives control over every external event or unlimited decision power.

12. Responsibility differs from authority because it concerns what?
Answer and detailed reasoning

Correct: B. The duty to perform assigned work

A person can have a duty without unlimited decision rights. Appropriate authority and resources must support the task, but responsibility does not itself authorise every approval or guarantee a perfect outcome.

13. A credit analyst preparing an appraisal may promise sanction automatically?
Answer and detailed reasoning

Correct: A. No, sanction requires the relevant authority and decision

Preparing evidence and approving credit are distinct roles. Customer importance or personal preference does not transfer sanctioning authority; the actual approval and conditions must be recorded before commitments are communicated.

14. Delegation should specify what?
Answer and detailed reasoning

Correct: B. Outcome, authority, limits, reporting and escalation

Clear boundaries make delegated work executable and reviewable. Delegation does not transfer powers the manager lacks or eliminate accountability, and trust does not replace the controls required for the task.

15. A manager delegates a report but prohibits alteration of definitions. Why?
Answer and detailed reasoning

Correct: C. To preserve consistency and control within the delegated task

Delegation can include data collection and analysis while retaining policy boundaries. Clear limits do not prohibit useful work or imply secrecy; they define what changes require separate authority.

16. A manager approves every minor action despite capable staff. What risk arises?
Answer and detailed reasoning

Correct: C. Excessive control can slow work and limit development

Over-control can create bottlenecks and discourage judgement. Accountability remains, and staff do not gain powers automatically; the solution is proportionate delegation within required controls rather than eliminating safeguards.

17. Centralisation can support what?
Answer and detailed reasoning

Correct: D. Consistency and specialist oversight for defined decisions

Central expertise can improve consistency, but high volumes may slow decisions and local knowledge remains valuable. Centralisation is a design choice with trade-offs, not a guarantee of speed or complete information.

18. Decentralisation requires what?
Answer and detailed reasoning

Correct: A. Clear authority, capability and review

Local decisions can improve responsiveness when boundaries and skills are appropriate. Local knowledge does not override policy or law, and monitoring is necessary to identify inconsistent or unauthorised actions.

19. A bank sets central credit policy but gives branches limited decision rights. This is what?
Answer and detailed reasoning

Correct: A. A combination of centralisation and decentralisation

Different decisions can be allocated at different levels. Central standards and bounded local authority can coexist; the arrangement still requires clear responsibilities, training and oversight rather than an all-or-nothing label.

20. A functional structure groups work primarily by what?
Answer and detailed reasoning

Correct: B. Specialist activities or expertise

Functions such as credit, operations and finance group expertise. This can improve specialisation but needs coordination; arbitrary labels or customer names alone do not describe the functional design.

21. A divisional structure can improve what while creating another trade-off?
Answer and detailed reasoning

Correct: D. Focus on a product, region or customer, with possible duplication

Divisions can align attention with a market but may duplicate capabilities or need common oversight. They do not guarantee zero cost or remove the need for control independence and cross-unit coordination.

22. An organisation chart proves what about actual performance?
Answer and detailed reasoning

Correct: B. Little without checking how roles operate

A chart is a simplified formal representation. Evidence from work, communication and controls is needed; staff can misunderstand duties, handoffs can fail and informal relationships can influence information flow.

23. A manual is most useful when it has what?
Answer and detailed reasoning

Correct: B. Clear responsibilities, ownership, versioning and accessible guidance

A maintained manual supports consistent understanding. It does not prove execution or replace training; outdated or incomplete guidance can mislead staff even when a document formally exists.

24. Constructive conflict management begins with what?
Answer and detailed reasoning

Correct: D. Understanding the issue and perspectives, then clarifying authority and action

Disagreement can reveal a process problem or competing priorities. Evidence and defined decisions help resolution; serious conduct issues require proper channels, and a wish for harmony cannot override mandatory requirements.

25. A reorganisation is complete when what has occurred?
Answer and detailed reasoning

Correct: B. Roles and processes operate effectively and are reviewed

A chart communicates a design but does not establish implementation. Training, handoffs, authority and evidence of working outcomes matter; silence or title changes do not prove the service is functioning.

Ready: 25 questions.

Sources and version notes

Review edition, 8 November 2026. Original explanations and fictional cases; independent academic approval remains pending. External links require internet.

Module A contentsPrevious chapterNext chapter