Skip to main content
GullySystem
Technology

Workflow and Approvals for Software development companies

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

Approvals cover change requests over agreed effort, rate card discounts, repository access for new joiners and laptop purchases alike. Every request waits with a named approver. Nothing moves silently.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
Software development companies

How the business operates.

Your product is delivery. Revenue depends on each person’s invoiced hours and the additional work requested by the client that remains unbilled.

Project and SOW register

Record each client, the contract type, the rate card, the milestones and the team, so every project shows what was sold before any hour is logged against it.

Timesheets against the plan

Log hours by person, project and task, with billable and non-billable kept apart and the burn shown against the estimate as the project runs.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Client and statement of work register. Hold every client, contact and signed statement of work. Billing model, rate card, hour cap, renewal date and payment terms are fields on the record, so the contract can be searched and reported.
  • Proposals and estimates. Build an estimate by role, grade and week from your own rate card. Keep each revision and the assumptions behind it, and convert the accepted one into a project.
  • Project plan and milestones. Lay out sprints, releases and client acceptance dates for each project. Milestones carry the amount payable on sign-off, so a slipped date shows its effect on billing.
  • Timesheets against the plan. Engineers log hours by project and task. Leads then approve them each week, and a project’s approved hours are compared with the planned hours for the same period.

Operational bottlenecks to check

Scope changes are never billed

A client asks for one more screen in a call, and the team builds it. The invoice does not change.

Hours and invoices disagree

The tracker says one total, the timesheet another, and the invoice a third. Somebody reconciles them by hand.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Proposal and estimate

    A prospect asks for a build. The team prepares an estimate by role and week, and the proposal goes out under one number. The accepted version is kept with its assumptions. Nothing is retyped.

  2. 2. Statement of work signed

    The signed contract is attached to a new project. Its billing model, rate card, hour caps, payment terms and named roles are entered as fields, not left inside the file. They can be reported.

  3. 3. Team allocated

    Engineers are assigned by the delivery head, a tester and a designer by percentage and dates. Clashes with other projects show before the allocation is saved.

  4. 4. Sprints and timesheets

    Sprints and milestones sit on the project calendar. Engineers log hours against the project and task each day, and the project lead approves them weekly.

  5. 5. Changes recorded and approved

    A request from the client becomes a change entry with an estimate. It is approved by the account owner and the client contact, then added to the project’s scope and budget. The client sees it.

  6. 6. Invoice and review

    Approved hours or accepted milestones become the invoice. At close, planned against actual hours and cost are compared and the project is archived with its documents. History stays searchable.

Industry reports to connect with

  • Hours planned against hours logged, by project and by sprint
  • Free engineers with skills and free-from dates
  • Change requests raised, approved and billed, by client
  • Invoices raised and unpaid, by client and age

Questions before implementation.

When should software development companies consider workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Related functions for software development companies.

    Talk to us

    Discuss workflow and approvals for your business.

    Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

    What happens after you share your requirements

    1. We review your brief and the systems you already use.
    2. We clarify the workflow, missing information and the work to consider first.
    3. The proposed scope sets out the deliverables, responsibilities and dependencies.
    4. Review the scope and commercial terms before deciding whether to proceed.

    Start with your requirements

    Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

    Share your requirements