Method / Custom software
Custom software brief
Try the interactive exercise ↓Custom software brief preparation is a process for defining one job, its participants, exchanged information and a checkable result. The brief connects the customer’s first action to a completion condition that the team can inspect. Roles and permissions identify who reads a record, who changes the record and who decides an exception. One ordinary booking change exposes affected records and the difference between a request and a confirmation. Seven worksheet fields preserve the workflow, people, current records, handoff, change, completion and open questions. A completed brief supports a scope discussion but does not prove that custom development is necessary or that a product implements the requested behavior.
Which workflow should a custom software brief describe?
A custom software brief should describe one recurring job with an identifiable start and completion point. The job can be a service booking, enquiry, order or document review. A bounded job gives the team a specific process to examine before choosing screens or integrations.
Choose a job that a member of staff can follow from the customer’s first action to an observable result. A service booking provides a practical hypothetical example. The customer requests a time, a coordinator checks availability and the customer receives a confirmed next step. The example defines an intended process, not a feature already delivered by a product.
Describe the start of the service booking in one sentence. Describe the completion of the service booking in a second sentence. The description exposes disagreement when one person calls a request complete at submission and another requires a confirmed appointment.
The booking boundary controls the scope of the brief. A smaller boundary makes the proposed change easier to inspect. A boundary covering every department hides the specific decision that needs improvement.
What should a software brief say about user permissions?
A software brief should name each role, the information the role needs and the actions the role may perform. Permission to read an outcome does not automatically include permission to change its source record. A role list starts an access discussion but does not replace an access-control design.
The Open Worldwide Application Security Project (OWASP) recommends minimum necessary privileges in its Authorization Cheat Sheet. OWASP also recommends checking permission on every request. OWASP’s authorization guidance supports an explicit permissions discussion, not a claim that a drafted role list proves security.
For example, a hypothetical booking process has three roles. The customer sees a confirmed appointment. The coordinator changes appointment availability. The manager decides whether a stated exception is acceptable. The proposed separation requires agreement with the actual business rules.
| Proposed role | Information needed | Decision to specify |
|---|---|---|
| Customer | The customer’s appointment and current status | Whether the requested time is acceptable |
| Coordinator | Requests, availability and assigned work | Which available time to confirm |
| Manager | The reason for an exception and affected booking | Whether the exception is permitted |
The permission boundary needs a negative example too. A customer viewing an appointment does not acquire permission to edit another customer’s booking. Writing the forbidden action gives the implementation team something concrete to test.
Where should a software brief identify a handoff?
A software brief should identify the point where another person or system needs the current record to continue a job. The handoff description names the next owner, the required information and the place holding the authoritative record. Missing information and unclear responsibility are separate causes of a blocked handoff.
For example, a customer changes a requested appointment time by message. The coordinator updates a spreadsheet while another staff member still reads the original message. The handoff has two competing versions of the time. Adding a notification alone does not decide which version controls the booking.
Record the handoff as one observable gap. The next staff member cannot see the changed time. The customer cannot confirm the agreed state. The team cannot identify the authoritative record. Each gap points to a different requirement.
A data handoff transfers information. An information exchange also transfers responsibility when someone must decide the next action. Naming both the record and the next owner reduces ambiguity without assuming that a new integration is necessary.
How should a software brief describe a booking change?
A software brief should describe one ordinary change and every role or record affected by the change. A moved booking, corrected customer detail or revised request exposes work that the original happy path misses. The change example should identify a human decision when automatic handling is not agreed.
The hypothetical service booking moves from one requested time to another. The changed time affects the availability record, assigned staff and customer confirmation. A changed request does not become a confirmed booking until the specified decision is made.
Use three steps to describe the booking change. First, identify the edited information. Second, identify the records and roles that need the edit. Third, identify the decision that makes the change effective.
- Record the requested time change in the booking example.
- Record the affected availability and confirmation records in the booking example.
- Record the responsible decision-maker in the booking example.
The third step prevents a generic automation requirement from hiding a business decision. For example, a coordinator can request a change while a manager retains authority over an exception. The brief must state the intended rule before the team designs the exception path.
The initial change example does not document every possible edge case. The example gives the team a bounded way to discover exceptions. More examples belong in the scope discussion when different changes require different decisions.
How should a software brief define completion?
A software brief should define completion as a visible result for a named role after a specific action. A feature label such as notifications does not identify the required result. Completion conditions also need an explicit outcome for incomplete information or a pending decision.
A hypothetical acceptance condition states that the customer’s booking view shows the agreed new time after an authorized coordinator confirms a change. The condition identifies the actor, action and visible outcome. The condition does not assert that a particular product already implements the behavior.
A pending change needs a different condition. For example, the customer view identifies a request as pending while the responsible person has not confirmed the time. Displaying the request as confirmed would contradict the stated decision rule.
Separate the proposed acceptance condition from its observed test result. The brief records what needs to happen. A later demonstration records whether the agreed behavior occurs. A written requirement is not evidence that the software passes the requirement.
A useful completion record includes one normal outcome and one unresolved outcome. The pair makes the transition from requested to confirmed visible. The actual business rules and agreed scope still determine the final acceptance conditions.
Try the idea
What information defines a workflow handoff?
A workflow handoff needs a task, a sender, a receiver, a record and proof of completion. The five fields expose missing ownership or evidence. For example, a project enquiry moves from the sales team to the project owner after the project owner records an accepted next step.
Your brief
Your entries stay in this page and clear when you leave. No information is sent to Beyzick. A preparation worksheet, not a quotation or scope approval. Avoid personal or customer information.
What should a custom software brief worksheet contain?
A custom software brief worksheet should contain seven fields covering the workflow, people, current records, handoff, change, completion and open questions. The fields connect the intended job to a result the team can inspect. An unanswered field stays visible instead of becoming an assumed feature.
The hypothetical service booking provides a concrete example for all seven fields. The example preserves the difference between a request and a confirmation. The unresolved cancellation rule remains an open question rather than an invented policy.
| Brief field | What to record | Hypothetical booking example |
|---|---|---|
| Workflow | One job with a start and completion point | A requested appointment becomes a confirmed appointment |
| People | Roles, information needs and decisions | Customer, coordinator and manager have distinct decisions |
| Current records | Where information is held today | A message and a spreadsheet contain different times |
| Handoff | Information and responsibility passed onward | Assigned staff need the confirmed time and current record |
| Change | One edit and its affected records | A time change affects availability and confirmation |
| Completion | A visible result for a named role | The customer sees the agreed time after confirmation |
| Open questions | A decision requiring an owner | The manager needs to define the cancellation rule |
A worksheet makes uncertainty inspectable. An open question identifies missing information without filling the gap with an unsupported answer. For example, a brief can name the person responsible for the cancellation rule while leaving the actual rule undecided.
Keep a working part of the process visible. A confirmation step that already works does not need replacement merely because the brief includes new software. The intended improvement should address the named gap without quietly expanding to the entire operation.
Which technology solutions fit a custom software brief?
Technology solutions for a custom software brief include a focused website improvement, an integration, a product or a wider operational application. The appropriate scope depends on the documented workflow and the gap preventing completion. A completed worksheet does not establish that custom development is the right purchase.
Beyzick provides websites, product design and development, and connected workflow services in its public service description. Beyzick uses the reader’s actual problem and existing setup to frame a scope discussion. Beyzick’s technology solutions provide the service context for that discussion.
For example, a missing explanation on a booking page can call for a focused content change. A repeated transfer between agreed records can call for investigation of an integration. Neither example establishes the solution before the workflow and constraints are understood.
A useful first discussion includes the current tool, the repeated difficulty and the outcome someone needs to inspect. A required integration, deadline or editing responsibility belongs in the discussion too. Price, delivery and support require an agreed scope rather than assumptions drawn from a worksheet.
Does a custom software brief need a complete screen list?
A custom software brief does not need a complete screen list to describe one workflow. Screen decisions become more specific after roles, records and completion conditions are understood.
Does a software brief prove that custom development is necessary?
A software brief does not prove that custom development is necessary. A working existing tool, a clearer rule or a focused change can address the identified gap.
Can a software brief include unanswered questions?
A software brief can include unanswered questions with named decision owners. An unresolved cancellation rule remains an open question until the responsible person defines the rule.
Does a role list establish secure access?
A role list does not establish secure access. The implementation needs agreed permissions and checks that enforce those permissions.