[UK] Smacky McTavish's Chief Of Security Application

Status
Not open for further replies.

GooseyMcDuck

Well-known Member
Aug 4, 2025
7
2
41
Steam ID: STEAM_0:0:216511021
Discord name: Goosey (fluff.goose)
For how long have you played on CG SCP: ~4 months
Age: 16
In what country are you located?: Scotland
Time zone: GMT (UTC+0)
Character name(s): Smacky McTavish
Civilian name: Shanky McTavish
What server are you applying for? (SCP-RP UK or SCP-RP USA): SCP-RP UK
Do you have a mic?: Yes
-
List all whitelisted, MTF, or CI roles that you hold or have held: Security Sergeant & Security Captain
-
Have you received any kicks/bans/warnings? and why?: Yes, banned once for prop abuse (cramming) as I put together pots and pans which I didn’t know would cause lag. I have a couple fail-RP and a few other warnings which were mostly if not all outside of me playing as GenSec Captain/Sergeant. These are all from September, August, July, or April in 2025. Otherwise, I have been behaving quite well whenever I am on.
-
Why are you applying for the Chief of Security?
I am applying for the Chief of Security as I would love to move up in the chain of command, do more and be granted the opportunity of being a great leader. I have been a Captain for 4 months and I have learned the skills required to be a responsible leader.

Furthermore, I have got ideas that I wish to implement in the department to try and improve it further. As a Captain, I wanted to help out by creating small documents like tutorials on hacking or a guide to new Captains; these I feel, if considered, would further better the roleplay experience of those within GenSec as it would let them assist with specific scenarios or feel more welcome to leadership, preparing them for future opportunities within the site.

Continuing on, I would like GenSec to be organized and more well trained and organised as I have seen people on catwalks by themself or rushing out into D-Block and immediately getting gunned down. Despite my own issues within combat, I fully believe a more coordinated department would be an excellent goal to reach and will guarantee more success in combat situations.

Finally, having competent leadership and good mentors in the department would help immensely as it would make the department as a whole more welcoming and respected. I had many people, who I deeply respect, that mentored me as I was a cadet moving up to where I am now as a Captain, which is something I’d like for others to experience. I enjoy roleplay and I feel like having relations with other departments would broaden this further for GenSec.
-
What makes you suitable for Chief of Security?: I believe I would be suitable for Chief of Security as I am a respected and mostly-liked member within GenSec. I have been considered to have decent leadership skills, a diplomatic friendly attitude, I like to help teach those around me, and I have a keen eye for the future prospects of the General Security Department.

As mentioned previously, as I highlighted my stance on having GenSec being a coordinated, more tactical but hospitable department, as well as encouraging mentorship of new players, I would be able to consider feedback from others, apply leadership, manage departmental relations, and manage the department ensuring Captains and Sergeants are performing to a high standard.

I believe that, in coordination with the other Chief of Security, the department can be more prosperous, and be more enjoyable as a whole in roleplay scenarios.
-
What are the responsibilities of the Chief of Security in RP?:
  • Organizing weekly meetings with Security Captains, explaining what went well and what wasn’t, and taking in feedback.
  • Coordinate with Site Administration to make changes and refine the department
  • Accepting or denying Captain applications
  • Managing departmental relations, also taking in feedback from others on how to improve
  • Mentoring new Captains and Sergeants
  • Approving new Sergeants for interviewing
  • Managing the department as a whole; ensuring that members perform their duties well
  • Create new projects, sub-divisions, and policies.
-
Please give some lore about your Chief of Security character and what storylines they would be involved in: Smacky McTavish was a former Royal Mail delivery worker in Glasgow. He was previously a drunk, who ironically, drank buckfast after his rounds of delivering mail. One day, he blacked out, waking up in a strange facility titled ‘Site-65’, quickly becoming hired as a Cadet within the General Security Department.

He was called into the Chiefs office about a week after submitting his application. During his interview becoming Captain, he was given questions regarding points of interests, what to do in specific situations, etc. Once he passed, he would lead GenSec in performing sweeps, riot and heavy weapons training, as well as scouting out new sergeants and mentoring sergeants. He would be kidnapped by DEA who queried him about his origin, why there is no documentation for him, and whether he was potentially from the British Occult Service, but would leave the ordeal unscathed.

During which, he would assist departments, like the DEA in printing documents. In contrast to this, he would be needlessly dragged to witness the execution of a dear friend and mentor of his who was shot by personnel in Floor 3 for Treason after he murdered a response unit over the theft of a sniper rifle. He vowed to make GenSec better than this - better than some scuffle over what is just simply a tool.

Months after he became a Captain, after his psychological evaluation as a s ergeant, unfortunate encounters with ISD Ethics, deaths of colleagues and friends, he chooses to fill in his application to Site Administration to become the Chief of Security.
 

SCP-Forum-thing.png



The following message is composed via consensus of the site administration team of site-65.

Hello @GooseyMcDuck ,

Thank you for showing an interest in expanding your duties within the Foundation. After careful consideration, we have come to a verdict regarding this personnel role reassignment request. This request is to be elevated to the next stage. We will be in contact shortly.


Good luck.

Secure. Contain. Protect.



CONFIDENTIAL
This document may not be shared with or used by personnel below the designated clearance level.​


 
Status
Not open for further replies.