SUPPORT / PROJECTS
Project support: separate a question, a defect and a change.
Different project requests require different evidence and decisions. Identify the affected deliverable and explain which kind of request you are making before proposing a fix.
Clarification or pending decision
Reference the requirement, review comment or deliverable in question. State what is unclear, the alternatives being considered and the decision needed. Identify any dependent work that cannot proceed until the question is resolved.
Possible defect
Describe the agreed or documented behavior and what happens instead. Include the affected version or environment, time observed and steps leading to the result. A report starts an investigation; it does not by itself establish the cause or whether corrective work is covered.
Content correction
Identify the exact page, field, file or output. Provide the current wording or value and the proposed replacement, with the source or approver responsible for its accuracy. Distinguish correcting an approved fact from requesting a new layout or additional content.
New requirement or expanded scope
Explain the desired behavior, who needs it and why. Identify changed inputs, permissions, integrations or outputs. A change may affect testing, schedule and ongoing responsibilities; obtain the required approval before assuming it is part of the existing work.
Keep updates attached to the same request
Use the engagement’s agreed contact route and reference earlier correspondence. If new evidence changes your understanding, say what changed. Avoid mixing unrelated issues into one request or describing an untested explanation as the confirmed cause. Coverage and response expectations remain agreement-specific.
Technology Solutions & Business Services